aws-provider no support for ap-northeast-3 region that became generally available on 1/03/21

[bchaja]

aws-provider ver 3.30 doesnt support ap-northeast-3 and error out with 'Invalid AWS Region ap-northeast-3'. The ap-north-east become open to all as of 1st/03 https://aws.amazon.com/blogs/aws/aws-asia-pacific-osaka-region-now-open-to-all-with-three-azs-more-services/

[bflad]

Hi @bchaja 👋 Thank you for submitting this.

The automatic region name validation that occurs during the Terraform AWS Provider configuration is based off the upstream AWS Go SDK endpoints model. When those are updated, which is most likely later today given previous AWS Go SDK timing with these types of announcements, the dependency update is made in this codebase, and released then the error will no longer occur.

You can workaround this error in the meantime with a provider configuration using the skip_region_validation argument, e.g.

provider "aws" {
  # ... potentially other configuration ...
  region                 = "ap-northeast-3"
  skip_region_validation = true
}

[snayler0]

FYI I have opened an issue with the aws-sdk-go team for this - aws/aws-sdk-go#3805

Unfortunately for me - skip_region_validation is not an appropriate workaround due to some questionable... but necessary processes to update our code - So i'll have to let my tests continue failing while we wait :)

Hopefully the change comes through soon though! Is it correct to assume that when the change is in the aws-sdk-go repo, it'll automatically mean a new provider version is built and made available here? (eg: ~v3.30.1?)

[bflad]

Automatic validation of the ap-northeast-3 region has been merged and will release with version 3.31.0 of the Terraform AWS Provider, likely later today. As mentioned above, the skip_region_validation flag can be used to prevent the validation error on earlier versions:

provider "aws" {
  # ... potentially other configuration ...
  region                 = "ap-northeast-3"
  skip_region_validation = true
}

[ghost]

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

[ghost]

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!