terraform-provider-aws icon indicating copy to clipboard operation
terraform-provider-aws copied to clipboard

Terraform Aws new region "me-central-1". error :' Invalid Region"

Open atanudas100 opened this issue 2 years ago • 10 comments

Description

If I use latest terraform version "4.50".. then the code accept the region "me-central-1" but it showing "Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: f4c793eb-0e82-4ce2-aa4e-359d959a9779, api error InvalidClientTokenId: The security token included in the request is invalid"

Using any other version < v4.50 , it is showing "Invalid region me-central-1"

References

No response

Would you like to implement a fix?

None

atanudas100 avatar Jan 16 '23 04:01 atanudas100

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

github-actions[bot] avatar Jan 16 '23 04:01 github-actions[bot]

Hi. Problem is really serious, we can not use terraform for new regions

xeonic-ant avatar Mar 16 '23 13:03 xeonic-ant

We also have this issue and it is blocking us from using Terraform in new regions.

joeybenamy avatar Mar 17 '23 20:03 joeybenamy

Me too, I cannot use terraform to deploy an EKS Cluster in me-central-1. Is it because of this region release recently?

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

zning1994 avatar Apr 23 '23 13:04 zning1994

I am also experiencing this issue when using an AWS S3 bucket in me-central-1 as the state backend for my module. My module is only creating global resources like IAM roles.

jwenz723 avatar May 03 '23 21:05 jwenz723

My problem was due to the terraform cli version not being up to date. I updated to version 1.4.6 and now my issue with accessing a terraform s3 state bucket in me-central-1 is resolved.

jwenz723 avatar May 03 '23 22:05 jwenz723

Tried with terraform cli version 1.5.5 and still having same issue.

Onelvis avatar Aug 11 '23 17:08 Onelvis

I have try with terraform 1.5.5 no luck, I tried with sts_region and endpoint block pointing to the sts URL, and no luck..

adamdaniel2993 avatar Aug 11 '23 17:08 adamdaniel2993

Hello! Is there any update on this?

cisco-ashekham avatar Feb 15 '24 15:02 cisco-ashekham

You can set your terragrunt.hcl file to "ignore" a region. This may work for you. With Terragrunt, you can use this in your locals section:

  # The following locals are used for constructing multi region provider configurations for the underlying module.
  multi_region_vars = read_terragrunt_config(find_in_parent_folders("multi_region_common.hcl"))
  regions_to_ignore = "me_central_1"
  all_aws_regions   = [for region in local.multi_region_vars.locals.all_aws_regions : region if region != local.regions_to_ignore]  
  #all_aws_regions   = local.multi_region_vars.locals.all_aws_regions
  opt_in_regions    = local.multi_region_vars.locals.opt_in_regions

Had to do this when we bumped from AWS provider ~> 3.0 to >= 4.26.0 Which was needed when we bumped terraform-aws-service-catalog to v0.104.16 (which needed AWS 4.x)

justin-octo avatar Feb 23 '24 20:02 justin-octo

Fixed via https://github.com/hashicorp/terraform-provider-aws/pull/26590 in Terraform AWS Provider v4.29.0.

ewbankkit avatar Jun 18 '24 16:06 ewbankkit

[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

github-actions[bot] avatar Jun 18 '24 16:06 github-actions[bot]

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.

github-actions[bot] avatar Jul 22 '24 02:07 github-actions[bot]