Invalid AWS Region: me-central-1

[nicon89]

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 other comments that do not add relevant new information or questions, 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

Terraform CLI and Terraform AWS Provider Version

$ terraform -v
Terraform v1.2.8
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v4.28.0

Affected Resource(s)

provider "aws"

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

terraform {
  required_version = "~> 1.2.8"
  required_providers {
    aws = {
      version = "~> 4.28.0"
    }
  }
}

provider "aws" {
  region = var.region
  default_tags {
    tags = {
      terraform = "true"
      env       = "common"
    }
  }
}

resource "aws_s3_bucket" "_" {
  bucket_prefix = "terraform-state"
}

Debug Output

https://gist.github.com/nicon89/df6a7c4f0e4d71fbc7fce3ce2a29863f

Panic Output

Expected Behavior

s3 bucket should be created in me-central-1 region.

Actual Behavior

Error:

│ Error: Invalid AWS Region: me-central-1
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on main.tf line 10, in provider "aws":
│   10: provider "aws" {

Steps to Reproduce

1. terraform apply

Important Factoids

References

• #0000

[ewbankkit]

@nicon89 Thanks for raising this issue 👏.
Until support for the new me-central-1 AWS Region is added to the Terraform AWS Provider you should be able to use the skip_region_validation configuration setting to bypass this error.

Blog post.

[nicon89]

@ewbankkit thanks, that did the job.

[github-actions]

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.