Service specific endpoints compatible resolver #396
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 is an alternative to #52 allowing aws service endpoints to be configured as per the service-specific endpoints feature defined environment variables which are not otherwise supported in the aws sdk for go v1.
Description of changes:
An endpoint resolver is configured which delegates to the default resolver unless there is relevant configuration in the environment.
When environment configuration is found for service endpoints it is used unless disabled via
AWS_IGNORE_CONFIGURED_ENDPOINT_URLS=true
. The configuration can set all service endpoints (AWS_ENDPOINT_URL
) or can configure endpoints for specific services.This endpoint resolver would no longer be required after updating to the aws sdk for go v2.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.