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

Support Automatic Region Validation for me-south-1 (Middle East (Bahrain)) #9545

Closed
bflad opened this issue Jul 30, 2019 · 3 comments
Closed
Labels
enhancement Requests to existing resources that expand the functionality or scope. provider Pertains to the provider itself, rather than any interaction with AWS.
Milestone

Comments

@bflad
Copy link
Contributor

bflad commented Jul 30, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

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

Potential Terraform Configuration

provider "aws" {
  region = "me-south-1"
}

References

@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. provider Pertains to the provider itself, rather than any interaction with AWS. labels Jul 30, 2019
@bflad bflad added this to the v2.22.0 milestone Jul 30, 2019
@bflad bflad changed the title Support Automatic Region Validation for me-south-1 (Middle East (Behrain)) Support Automatic Region Validation for me-south-1 (Middle East (Bahrain)) Jul 30, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jul 30, 2019
@bflad bflad removed the needs-triage Waiting for first response or review from a maintainer. label Jul 30, 2019
@bflad
Copy link
Contributor Author

bflad commented Jul 30, 2019

Support for automatic validation of this new region has been merged and will release with version 2.22.0 of the Terraform AWS Provider, later this week.

On a build of the provider with the update:

provider "aws" {
  region = "me-south-1"
}

data "aws_region" "current" {}

output "region" {
  value = data.aws_region.current.name
}

Outputs:

$ terraform apply
data.aws_region.current: Refreshing state...

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

region = me-south-1

Please note that this new region requires the same manual process to enable it as ap-east-1 Asia Pacific (Hong Kong) did. This process is outlined in the announcement for that region. Once enabled in the console, it takes a few minutes for everything to work properly.

If the region is not enabled properly, or the enablement process is still in progress, you can receive errors like these:

$ terraform apply

Error: error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid.
	status code: 403, request id: 142f947b-b2c3-11e9-9959-c11ab17bcc63

  on main.tf line 1, in provider "aws":
   1: provider "aws" {

To use this new region before Terraform AWS Provider version 2.22.0, you must disable the provider's automatic region validation via:

provider "aws" {
  # ... potentially other configuration ...

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

@ghost
Copy link

ghost commented Aug 1, 2019

This has been released in version 2.22.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 for triage. Thanks!

@ghost
Copy link

ghost commented Nov 2, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Nov 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. provider Pertains to the provider itself, rather than any interaction with AWS.
Projects
None yet
Development

No branches or pull requests

1 participant