[DRIVERS-2696] Add a programmatic option to control AWS region settings Created: 17/Aug/23 Updated: 21/Dec/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Neal Beeken | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | alex+, james+ | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Quarter: | FY25Q2 | ||||||||
| Description |
SummaryAWS SDKs offer slightly different ways to configure region settings. Some use environment variables, others only allow programmatically setting options. The variations in configurations is problematic when the user is not in direct control of the SDK and the driver's internal use may prevent them from properly configuring the SDKs behavior. MotivationWho is the affected end user?
How does this affect the end user?In the case of How likely is it that this problem or use case will occur?If an SDK does not obtain settings from the environment this will occur always when using AWS auth. If the problem does occur, what are the consequences and how severe are they?Increased latency when using AWS authentication. Is this issue urgent?TBD Is this ticket required by a downstream team?No Is this ticket only for tests?No Acceptance Criteria
|
| Comments |
| Comment by Tom Selander [ 22/Aug/23 ] |
|
Drivers Triage: It is unclear the exact path forward for what we'll do, but we should update the auth spec and document our decision. Backlogging this until Q4 |