fix: always provide region to AWS SDK clients#3630
Merged
Conversation
50b5fd0 to
bcbbf4e
Compare
AWS SDK v3 clients require the region to be set, even for global services like STS and IAM. This change implements the following logic: - On Lambda/ECS platform start up, try to find if the default region is set at config/profile level (or via AWS_REGION env var) - If a default region is not set, use the region in which the test is going to run - Pass that value to all SDK client constructors, such as STS or IAM clients
bcbbf4e to
51cc45a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
AWS SDK v3 clients require the region to be set, even for global services like STS and IAM.
This change implements the following logic:
Fixes #3629
Pre-merge checklist
This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.