Skip to content
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

backend/s3: Support New me-south-1 Region Automatic Validation #22254

Closed
bflad opened this issue Jul 30, 2019 · 2 comments · Fixed by #22253
Closed

backend/s3: Support New me-south-1 Region Automatic Validation #22254

bflad opened this issue Jul 30, 2019 · 2 comments · Fixed by #22253

Comments

@bflad
Copy link
Contributor

bflad commented Jul 30, 2019

Current Terraform Version

Terraform v0.12.5

Use-cases

https://aws.amazon.com/about-aws/whats-new/2019/07/announcing-the-new-aws-middle-east--bahrain--region-/

Amazon Web Services (AWS) is announcing the immediate availability of the Middle East (Bahrain) Region, which is the first AWS Region in the Middle East and consists of three Availability Zones.

The region shorthand name is me-south-1. Allow S3 Backend storage in the new region without special backend configuration.

Available Workaround

terraform {
  # ... potentially other configuration ...

  backend "s3" {
    # ... other configuration ...

    region                 = "me-south-1"
    skip_region_validation = true
  }
}

Proposal

Update AWS Go SDK dependency to v1.21.7, which contains new region endpoint information.

References

@bflad
Copy link
Contributor Author

bflad commented Jul 30, 2019

This has been merged and will release with Terraform 0.12.6.

@ghost
Copy link

ghost commented Aug 30, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant