Inner STSClient doesn't longer use the provided region

[Grmiade]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

Since the version 3.502.0, the inner STSClient doesn't longer use the provided region in the DynamoDBClient instance when we use assume role with web identity.

SDK version number

@aws-sdk/client-dynamodb@3.502.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v20.9.0

Reproduction Steps

• Configure envs like AWS_REGION (eu-west-3 by example), AWS_ROLE_ARN, AWS_STS_REGIONAL_ENDPOINTS and AWS_WEB_IDENTITY_TOKEN_FILE to use assume role with web identity.
• Create a DynamoDBClient instance like new DynamoDBClient()
• Perform any command.

Observed Behavior

The STSClient will use the us-east-1 region by default.

Expected Behavior

The STSClient should use the region specified in AWS_REGION by default (like it was before the version 3.502.0).

Possible Solution

Downgrade to 3.501.0.
Or specify explicitly the region with new DynamoDBClient({ credentials: fromNodeProviderChain({ clientConfig: { region: process.env.AWS_REGION } }) }).

Additional Information/Context

Still doesn't work with 3.514.0

[kuhe]

Thanks for reporting this. I've confirmed this bug was a result of my misunderstanding of the defaulting behavior of the global fallback us-east-1.

A fix was merged in #5800 with new tests.

The fix should be released in the next version expected later today as v3.515.0.

[Grmiade]

Thanks @kuhe for the reactivity 👍

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.