-
Type: New Feature
-
Resolution: Done
-
Priority: Unknown
-
None
-
Component/s: Authentication
Summary
Currently drivers are querying an AWS link-local endpoint each time a connection handshake results in authentication. This may result in hitting a rate limit. Drivers should cache fetched AWS credentials if the expiration time is known, and only re-fetch the credentials when they are about to expire.
Motivation
Who is the affected end user?
Users authenticating with MONGODB-AWS using automatic credential lookup.
How does this affect the end user?
Hitting rate limits may result in temporary unavailability.
How likely is it that this problem or use case will occur?
Likely for EKS and ECS users with many simultaneous connections.
If the problem does occur, what are the consequences and how severe are they?
Authentication failures requiring backoff and retry attempts.
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
No
- is related to
-
DRIVERS-2011 On-demand callback for AWS credentials
- Closed
- split to
-
CDRIVER-4439 Cache AWS Credentials Where Possible
- Closed
-
CSHARP-4273 Cache AWS Credentials Where Possible
- Closed
-
CXX-2554 Cache AWS Credentials Where Possible
- Closed
-
GODRIVER-2504 Cache AWS Credentials Where Possible
- Closed
-
JAVA-4690 Cache AWS Credentials Where Possible
- Closed
-
MOTOR-1002 Cache AWS Credentials Where Possible
- Closed
-
NODE-4478 Cache AWS Credentials Where Possible
- Closed
-
PYTHON-3313 Cache AWS Credentials Where Possible
- Closed
-
RUBY-3066 Cache AWS Credentials Where Possible
- Closed
-
RUST-1420 Cache AWS Credentials Where Possible
- Closed
-
PHPC-2158 Cache AWS Credentials Where Possible
- Closed
- mentioned in
-
Page Loading...