Detect https_proxy environment variable and allow SDK to discover credentials #12
Conversation
This file contains 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
eliminate requirement to explicitly pass in AWS credentials and instead let the SDK discover them via it's built-in mechanisms.
|
Added! Thanks for this! (: |
Closed
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.
I'm running behind a corporate proxy and calls to AWS require explicitly setting the
httpOptions.agentproperty. This requires taking on a dependency to https-proxy-agent. Ideally the SDK would have this functionality built-inThe second change eliminates the requirement to specify the
accessKeyIdandsecretAccessKey. The SDK will automatically discover credentials via the shared credentials file (~/.aws/credentials) or environment variables. These techniques are recommended over the accessKeyId and secretAccessKey properties, but they are still supported.