update aws credentials build #659
Open
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
Author
|
sorry , i updated and In my environment the test passed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR enhances the AWS configuration logic by introducing support for the AWS default credential provider chain.
When accessKey and secretKey are empty, allowing it to automatically load credentials from multiple AWS-supported sources such as:
Environment variables
This change improves flexibility and simplifies configuration in environments where credentials are already managed by AWS.
Changes
Updated getAwsConfig to use the AWS default credential chain when accessKey or secretKey is not provided.
Retains existing behavior (manual static credentials) when both keys are explicitly specified.