aws/session: Add support for client TLS certs on HTTP client #3654
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.
Adds support for the SDK to automatically modify the HTTP client to include TLS configuration of custom Client TLS certificate. This configuration can be provide via the environment variable or directly in code via the
session.Options
struct.These options are compatible with the AWS_CA_BUNDLE configuration.
Environment variable configuration
Both
AWS_SDK_GO_CLIENT_TLS_CERT
, andAWS_SDK_GO_CLIENT_TLS_KEY
must be provided together, and must point to valid PEM encoded file containing the certificate, and key respectively.In code configuration via session.Options
Alternative configuration is to specify the
ClientTLSCert
andClientTLSKey
fields on thesession.Options
struction. These areio.Reader
s that provide the PEM encoded content for the certificate and key files.