fix(config-resolver): allow asterisk region with warning #1760
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kuhe
force-pushed
the
fix/region-check
branch
from
3bf6fe8 to
6ea3043
Compare
kuhe
force-pushed
the
fix/region-check
branch
from
6ea3043 to
3cc9bdd
Compare
trivikr
approved these changes
Nov 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
n/a
Allow single asterisk to be set as the region, but warn that this is not the correct way to configure sigv4a. This makes the region validation less sharp-edged for people who have configured
*unnecessarily while using sigv4a.Documentation at the AWS SDK will be updated (aws/aws-sdk-js-v3#7472) to refer users to the
sigv4aSigningRegionSetandauthSchemePreferenceconfiguration fields instead.