-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Handling endpoint differences for S3 in the AWS SDK for Go v1 and v2 #33028
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
proposal
Proposes new design or functionality.
service/s3
Issues and PRs that pertain to the s3 service.
Comments
gdavison
added
the
enhancement
Requests to existing resources that expand the functionality or scope.
label
Aug 15, 2023
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This was referenced Sep 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
proposal
Proposes new design or functionality.
service/s3
Issues and PRs that pertain to the s3 service.
Description
The S3 resources in the AWS Provider are currently implemented using the AWS SDK for Go v1. The team will be updating the SDK for S3 (and other service) to the AWS SDK for Go v2. In v1, the S3 client uses a global endpoint (
s3.amazonaws.com
) inus-east-1
and regional endpoints (s3.<region>.amazonaws.com
) for all others.However, in v2, the S3 client uses regional endpoints for all regions. In practice, this change is unlikely to impact users, but some AWS account setups may restrict how endpoints are used, so it is potentially a breaking change.
v1 supports using regional endpoints for all regions using the environment variable
AWS_S3_US_EAST_1_REGIONAL_ENDPOINT
, the shared config parameters3_us_east_1_regional_endpoint
, or the Go config parameterS3UsEast1RegionalEndpoint
. The valid values arelegacy
(i.e. global endpoint forus-east-1
) orregional
.v2 supports uses regional endpoints for all regions, as well as supporting a pseudo-region
aws-global
which uses the global endpoint.Proposal
regional
, which will then use regional endpoints in all regionsus-east-1
and continue supporting the configuration parametersAffected Resource(s) and/or Data Source(s)
All S3 resources
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: