-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Authentication
-
None
-
Needed
-
Summary
AWS recommends using an SDK to "take care of some of the heavy lifting necessary in successfully making API calls, including authentication, retry behavior, and more".
_We should consider adopting SDKs for drivers where one exists for the programming language, especially in light of new features like DRIVERS-1746(https://jira.mongodb.org/browse/DRIVERS-1746).
A recommended pattern would be to not further enhance the driver implementation, and take an optional dependency on the AWS SDK. If the SDK is available, use it, otherwise fallback to the existing driver implementation.
Motivation
Who is the affected end user?
Drivers would have less implementation work and users would get a standard behavior for their programming language.
How does this affect the end user?
They will be able to use the full extend of the SDK capability, but may require some changes if the SDK behavior does not match the behavior of the driver previously.
- is related to
-
DRIVERS-1405 For MONGODB-AWS, follow AWS-SDK conventions for resolving credentials
- Backlog
- related to
-
DRIVERS-2945 Support for AWS EKS Pod Identity
- Backlog
- split to
-
CDRIVER-4516 Consider Using AWS SDK for Auth
- Backlog
-
CXX-2609 Consider Using AWS SDK for Auth
- Backlog
-
GODRIVER-2625 Consider Using AWS SDK for Auth
- Backlog
-
RUBY-3169 Consider Using AWS SDK for Auth
- Backlog
-
RUST-1529 Consider Using AWS SDK for Auth
- Blocked
-
CSHARP-4390 Consider Using AWS SDK for Auth
- Closed
-
JAVA-4796 Consider Using AWS SDK for Auth
- Closed
-
MOTOR-1061 Consider Using AWS SDK for Auth
- Closed
-
NODE-4781 Consider Using AWS SDK for Auth
- Closed
-
PHPLIB-1032 Consider Using AWS SDK for Auth
- Closed
-
PYTHON-3496 Consider Using AWS SDK for Auth
- Closed