Summary

AWS 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.

Motivation

Who is the affected end user?

• AWS Auth users that allow the driver to obtain temporary credentials

How does this affect the end user?

In the case of NODE-5477 users are experiencing increased latency when the driver routes it's STS request to the default global region (us-east-1) rather than to their current local region.

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

• Add an optional AWS_REGION property to authMechanismProperties
• Require drivers to set this property in their SDK configurations whenever possible to override environment variables