-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Use S3 regional endpoint in us-east-1
for directory buckets
#34893
Conversation
Community NoteVoting for Prioritization
For Submitters
|
…t-1` does not match client region `aws-global` and UseArnRegion is `false`' when using S3 access point.
…-1` does not match client region `aws-global` and UseArnRegion is `false`' when using S3 access point.
…-1` does not match client region `aws-global` and UseArnRegion is `false`' when using S3 access point.
…-east-1` does not match client region `aws-global` and UseArnRegion is `false`' when using S3 access point.
us-east-1
for directory bucketsus-east-1
for directory buckets
This functionality has been released in v5.31.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Force use of the S3 regional endpoint in
us-east-1
for directory buckets.Relations
Closes #34869.
Closes #34621.
Output from Acceptance Testing
us-west-2
us-east-1
global endpointus-east-1
regional endpoint