-
Type: New Feature
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Authentication
-
None
Summary
Users cannot provide custom AWS configuration. Namely, this affects the Node Driver in that it does not support AWS IAM Role Assumption. As a result, users need to implement custom expiry and reconnection logic when their STS session expires.
Motivation
Who is the affected end user?
Who are the stakeholders?
How does this affect the end user?
users need to implement custom expiry and reconnection logic when their STS session expires.
How likely is it that this problem or use case will occur?
Likely. In the Node Driver, users often ask for different AWS configurations.
If the problem does occur, what are the consequences and how severe are they?
Annoyance for user.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
No.
Acceptance Criteria
Allow users to provide their own configuration function.
- is depended on by
-
JAVA-5618 Allow use of a specific profile when connecting to AWS
- Blocked
- is related to
-
NODE-6094 Request + PR: ability to get Mongo to handle AWS IAM Role assumption
- Closed
- related to
-
JAVA-5618 Allow use of a specific profile when connecting to AWS
- Blocked
- split to
-
NODE-6141 Allow users to provide custom AWS configuration
- Backlog