• Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.7.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Needed
    • Hide

      Needs to document that AWS KMS provider credentials in mongosh now do not need to be provided in an environment in which credentials can be picked up by the AWS SDK (i.e. the same set of circumstances in which the MONGODB-AWS auth mechanism does not require explicit credentials). In this case, the user can pass

      {
        kmsProviders: { aws: {} }
      }
      

      to the Mongo constructor to enable AWS KMS usage.

      Show
      Needs to document that AWS KMS provider credentials in mongosh now do not need to be provided in an environment in which credentials can be picked up by the AWS SDK (i.e. the same set of circumstances in which the MONGODB-AWS auth mechanism does not require explicit credentials). In this case, the user can pass { kmsProviders: { aws: {} } } to the Mongo constructor to enable AWS KMS usage.
    • Iteration Turtle, Iteration Unicornfish

          Assignee:
          anna.henningsen@mongodb.com Anna Henningsen
          Reporter:
          anna.henningsen@mongodb.com Anna Henningsen
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved:

              Error rendering 'slack.nextup.jira:slack-integration-plus'. Please contact your Jira administrators.