Invalid AWS Region #8040

scalp42 · 2019-03-21T18:35:54Z

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

Terraform Version

Terraform v0.11.13
+ provider.aws v2.2.0

Terraform Configuration Files

provider "aws" {
  region = "us-west-2"
  alias = "bridge"
  version = "~> 2.2.0"
}

data "aws_caller_identity" "bridge" {
  provider = "aws.bridge"
}

data "aws_iam_policy_document" "s3_changeme_terraform" {
  statement {
    #sid = "1"

    actions = [
      "s3:GetBucketLocation",
      "s3:GetBucketVersioning",
      "s3:GetObject",
      "s3:GetObjectVersion",
      "s3:ListBucket",
    ]

    effect = "Allow"

    resources = [
      "arn:aws:s3:::changeme-terraform",
    ]

    principals {
      type = "AWS"
      identifiers = [
        "arn:aws:iam::${data.aws_caller_identity.bridge.account_id}:root",
      ]
    }
  }
}

Debug Output

Plan: https://gist.github.com/scalp42/c847168667233b4bf5b89e79dbaa7c0c

Apply: https://gist.github.com/scalp42/cd7644708890dfed55080c6d870a8b1f

Expected Behavior

it should not ask for the region
it should pick up the region from the provider

Actual Behavior

will ask for AWS region
will not create any resource mentioning an invalid AWS region

Steps to Reproduce

terraform plan -out terraform
terraform plan apply terraform

References

This issue relates to the region being asked: hashicorp/terraform#20599

The text was updated successfully, but these errors were encountered:

scalp42 · 2019-03-21T18:38:34Z

It works if I force the region through env variable:

AWS_REGION=us-west-2 terraform xxx

But I don't think it's expected behavior as the region is specified in the provider.

squidfunk · 2019-06-06T17:21:06Z

Still happening for me on terraform-0.12.1 and terraform-provider-aws-2.13.0

BovineEnthusiast · 2019-06-18T06:28:54Z

In the off chance this helps someone who has the same issue but for a different reason, I accidentally had underscores instead of dashes.

techiechap · 2019-07-08T19:18:42Z

In the off chance this helps someone who has the same issue but for a different reason, I accidentally had underscores instead of dashes.

Same issue, i had used underscore instead of -, thanks

DrStrangepork · 2019-07-12T15:28:45Z

In the off chance this helps someone who has the same issue but for a different reason, I accidentally had underscores instead of dashes.

Underscores and dashes in what? AWS_REGION is the correct format with underscores.

BovineEnthusiast · 2019-08-05T05:31:43Z

In the off chance this helps someone who has the same issue but for a different reason, I accidentally had underscores instead of dashes.

Underscores and dashes in what? AWS_REGION is the correct format with underscores.

If I recall correctly I did us_west_2 instead of us-west-2.

scalp42 · 2019-08-06T01:14:55Z

I think there's a new issue now: #9617

rehevkor5 · 2019-08-13T17:44:44Z

I had the same problem when using terraform import with a -var-file and aws provider like:

provider "aws" {
  region = var.region
}

Error output:

Error: Invalid AWS Region: 

  on ../terraform/modules/cluster/main.tf line 1, in provider "aws":
   1: provider "aws" {

I had to replace the variable with a hard-coded region in order to get it to work.

The annoying thing about it is that it appears (far as I can tell) to work just fine when doing plan/apply, and then surprises you with problems if you ever happen to use import.

mikhailadvani · 2019-09-05T15:21:33Z

faced the same issue during import of resources with terraform v0.12.8 and AWS provider v2.26.0 and v2.27.0

kartvep · 2019-09-23T16:59:22Z

Same issue with provider.aws v2.29.0

kartvep · 2019-09-24T13:12:19Z

Looks like for import context is initialized with some short circuit.
If variable used for region doesn't have default value, import fails with Error: Invalid AWS Region: as described above.
But if default value added for this variable, import operation uses this value instead of given to module's parameter.

main.tf:

module "tst" {
  source = "./tst"
  region = "aws-ie"
}

tst/main.tf:

variable "region" {
   default = "WAT?"
}

local {
   regions = { "aws-ie" = "eu-west-1" }
}

provider "aws" {
  region = local.regions[var.region]
}
...

terraform import module.tst.resource resource_id fails like this:

Error: Invalid index

  on tst/main.tf line 2, in provider "aws":
   2:   region = local.regions[var.region]
    |----------------
    | local.regions is object with 10 attributes
    | var.region is "WAT?"

The given key does not identify an element in this collection value.

Terraform v0.12.7
+ provider.aws v2.29.0

UPD: same error with Terraform v0.12.9

fernanen · 2019-12-11T07:06:25Z

In the off chance this helps someone who has the same issue but for a different reason, I accidentally had underscores instead of dashes.

I was passing an undeclared and uninitialized Linux variable when running an Apply like so:
TF_VAR_aws_region=$AWS_REGION Terraform apply

After setting my variable AWS_REGION with the right region - I was able to proceed with the build.

vianel · 2020-02-03T19:55:17Z

faced the same issue terraform = 0.12.20
"aws" version = "~> 2.45.0"

this works for me 👇

I had to replace the variable with a hard-coded region in order to get it to work.

jessesanford · 2020-02-04T23:38:11Z

Same here with "aws" version 2.40.0

vazhnov · 2020-02-20T13:39:17Z

The same problem with "profile" too, not only "region". I couldn't do import until hardcoded profile name.

Error message:

Error: No valid credential sources found for AWS Provider.
	Please see https://terraform.io/docs/providers/aws/index.html for more information on
	providing credentials for the AWS Provider

terraform = 0.12.20, through tfenv.
provider.aws 2.49

llamahunter · 2020-05-18T19:22:05Z

This seems to be a deep terraform bug in the way import runs vs plan or apply . hashicorp/terraform#13018

amitcloudworld · 2020-06-26T10:01:40Z

Region name must be like this other wise you will get error for region ok region= "us-west-1a" you need to remove a this is the right way to keep your regino name region = "us-west-1"

happy

sosimon · 2020-08-26T20:04:18Z

I have run into this a few times now - I end up manually editing all the providers in all my modules inside .terraform from

provider "aws" {
  region = var.region
}

to

provider "aws" {
  region = "us-east-1"
}

and then tf import again.

… local environment variables hashicorp/terraform-provider-aws#8040

dyegoe · 2021-04-19T13:03:19Z

I don't know if it is related, but the error is the same, at least. Still happen on v0.15.0 + AWS v3.37.0

Terraform v0.15.0
+ provider registry.terraform.io/hashicorp/aws v3.37.0

#########################
locals {
  region               = "eu-north-1"
  resource_name_prefix = "elastic-lab"
  common_tags = {
    project     = "elastic-lab"
    workspace   = "elastic-lab"
    environment = "lab"
    region      = "${local.region}"
    terraform   = "true"
  }
}

#########################
provider "aws" {
  region = local.region
}

If I plan, it goes well

% terraform plan -out deploy.plan
module.vpc.aws_vpc.this[0]: Refreshing state... [id=vpc-04059f72fbd29c65a]
module.vpc.aws_subnet.public[0]: Refreshing state... [id=subnet-048d25053a9462e08]
module.vpc.aws_subnet.public[2]: Refreshing state... [id=subnet-06e137f834aafb643]
module.vpc.aws_subnet.public[1]: Refreshing state... [id=subnet-05292f8ea1a41e5d2]
module.vpc.aws_route_table.public[0]: Refreshing state... [id=rtb-03f14abf8d3dbcff3]
module.vpc.aws_internet_gateway.this[0]: Refreshing state... [id=igw-04ef51cea1a9b3432]
module.vpc.aws_route.public_internet_gateway[0]: Refreshing state... [id=r-rtb-03f14abf8d3dbcff31080289494]
module.vpc.aws_route_table_association.public[0]: Refreshing state... [id=rtbassoc-04433f9202cebccf9]
module.vpc.aws_route_table_association.public[2]: Refreshing state... [id=rtbassoc-0c75e1cf254ec8112]
module.vpc.aws_route_table_association.public[1]: Refreshing state... [id=rtbassoc-096033c5f5206f58e]

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your configuration and the remote system(s). As a result, there are no actions to take.

But if I try to destroy

% terraform destroy              
module.vpc.aws_vpc.this[0]: Refreshing state... [id=vpc-04059f72fbd29c65a]
module.vpc.aws_internet_gateway.this[0]: Refreshing state... [id=igw-04ef51cea1a9b3432]
module.vpc.aws_route_table.public[0]: Refreshing state... [id=rtb-03f14abf8d3dbcff3]
module.vpc.aws_subnet.public[2]: Refreshing state... [id=subnet-06e137f834aafb643]
module.vpc.aws_subnet.public[0]: Refreshing state... [id=subnet-048d25053a9462e08]
module.vpc.aws_subnet.public[1]: Refreshing state... [id=subnet-05292f8ea1a41e5d2]
module.vpc.aws_route.public_internet_gateway[0]: Refreshing state... [id=r-rtb-03f14abf8d3dbcff31080289494]
module.vpc.aws_route_table_association.public[2]: Refreshing state... [id=rtbassoc-0c75e1cf254ec8112]
module.vpc.aws_route_table_association.public[0]: Refreshing state... [id=rtbassoc-04433f9202cebccf9]
module.vpc.aws_route_table_association.public[1]: Refreshing state... [id=rtbassoc-096033c5f5206f58e]
╷
│ Error: Invalid AWS Region: 
│ 
│   on main.tf line 19, in provider "aws":
│   19: provider "aws" {
│

thinkspill · 2021-04-19T17:49:17Z

I'm also seeing this for the first time today, on 0.15.0.

freakinhippie · 2021-04-19T20:46:11Z

I am seeing this issue too, using terraform v0.15.0, and aws v3.37.0.

bflad · 2021-04-19T20:48:01Z

It looks like this is a bug upstream in Terraform CLI version 0.15.0 (hashicorp/terraform#28428 / hashicorp/terraform#28444), which could be addressed next Terraform CLI release.

saivarunr · 2021-04-20T14:12:00Z

Works fine when apply, destroy does not work.

╷
│ Error: Invalid AWS Region:
│
│ on .terraform/modules/deploy-eks/main.tf line 24, in provider "aws":
│ 24: provider "aws" {
│
╵

However, had to edit the file deploy-eks/main.tf inside .terraform directory to make destroy work.

saivarunr · 2021-04-20T15:17:23Z

We could circumvent this by configuring the aws provider in the parent module, passing it to deploy-eks module as provider.

pschulten · 2021-04-23T07:50:43Z

I just build the CLI from main, and it fixes it

brikis98 · 2021-04-27T15:24:18Z

Seeing the same issue. apply works fine, but on destroy, any nested provider block with region set to a variable gives an "Invalid AWS Region" error.

brikis98 · 2021-04-27T15:25:12Z

BTW, this worked fine with Terraform 0.14.x, but is newly broken with Terraform 0.15.x.

antondemidov · 2021-04-29T10:29:58Z

seems it was fixed in 0.15.1

mhvelplund · 2021-05-25T05:25:46Z

seems it was fixed in 0.15.1

I tried with 0.15.4 and it workd. So; with 0.15.0 I can init and plan, but not destroy. Bug seems fixed in the subsequent patch 🤷‍♀️

breathingdust · 2022-01-11T22:28:44Z

Closing this as this appears to have been resolved in an upstream Terraform patch landing in 0.15.1. If I have closed this in error, do let me know and I will reopen.

markhuge · 2022-03-08T00:51:11Z

seems to have resurfaced in 1.1.7 with aws provider 4.4.0.

terraform plan fails when the region is set from the provider config, but will proceed if I set an env var:

provider "aws" {
  region = "us-west-2"
  alias = "west"
}

Error: error configuring Terraform AWS Provider: error validating provider credentials: error calling sts:GetCallerIdentity: operation error STS: GetCallerIdentity, failed to resolve service endpoint, an AWS region is required, but was not found

github-actions · 2022-05-10T02:18:18Z

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.

bflad added the provider Pertains to the provider itself, rather than any interaction with AWS. label Mar 23, 2019

aeschright added the needs-triage Waiting for first response or review from a maintainer. label Jun 24, 2019

aeschright added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 9, 2019

dpedu mentioned this issue Feb 20, 2020

IAM instance profile <name> EntityAlreadyExists, but it actually didn't. hashicorp/terraform#24177

Closed

ghost mentioned this issue Feb 21, 2020

IAM instance profile <name> EntityAlreadyExists, but it actually didn't. #12121

Closed

shinjonathan added a commit to shinjonathan/terraform-aws-postgres-vpc that referenced this issue Sep 23, 2020

Addresses required region error which was looking up region info from…

cf127a5

… local environment variables hashicorp/terraform-provider-aws#8040

bbenligiray mentioned this issue Oct 18, 2020

Terraform fails at getting the region as a variable api3dao/airnode#110

Closed

mxiamxia mentioned this issue Apr 23, 2021

lock the tf version to fix aws resource destroy error aws-observability/aws-otel-collector#471

Merged

antonbabenko mentioned this issue Apr 26, 2021

refactor: remove existing vpc endpoint configurations from base module and move into sub-module terraform-aws-modules/terraform-aws-vpc#635

Merged

1 task

breathingdust closed this as completed Jan 11, 2022

github-actions bot locked as resolved and limited conversation to collaborators May 10, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Invalid AWS Region #8040

Invalid AWS Region #8040

scalp42 commented Mar 21, 2019

scalp42 commented Mar 21, 2019

squidfunk commented Jun 6, 2019

BovineEnthusiast commented Jun 18, 2019 •

edited

Loading

techiechap commented Jul 8, 2019

DrStrangepork commented Jul 12, 2019

BovineEnthusiast commented Aug 5, 2019

scalp42 commented Aug 6, 2019

rehevkor5 commented Aug 13, 2019 •

edited

Loading

mikhailadvani commented Sep 5, 2019 •

edited

Loading

kartvep commented Sep 23, 2019

kartvep commented Sep 24, 2019 •

edited

Loading

fernanen commented Dec 11, 2019 •

edited

Loading

vianel commented Feb 3, 2020

jessesanford commented Feb 4, 2020

vazhnov commented Feb 20, 2020

llamahunter commented May 18, 2020

amitcloudworld commented Jun 26, 2020

sosimon commented Aug 26, 2020

dyegoe commented Apr 19, 2021

thinkspill commented Apr 19, 2021

freakinhippie commented Apr 19, 2021

bflad commented Apr 19, 2021

saivarunr commented Apr 20, 2021

saivarunr commented Apr 20, 2021

pschulten commented Apr 23, 2021

brikis98 commented Apr 27, 2021

brikis98 commented Apr 27, 2021

antondemidov commented Apr 29, 2021

mhvelplund commented May 25, 2021

breathingdust commented Jan 11, 2022

markhuge commented Mar 8, 2022

github-actions bot commented May 10, 2022

Invalid AWS Region #8040

Invalid AWS Region #8040

Comments

scalp42 commented Mar 21, 2019

Community Note

Terraform Version

Terraform Configuration Files

Debug Output

Expected Behavior

Actual Behavior

Steps to Reproduce

References

scalp42 commented Mar 21, 2019

squidfunk commented Jun 6, 2019

BovineEnthusiast commented Jun 18, 2019 • edited Loading

techiechap commented Jul 8, 2019

DrStrangepork commented Jul 12, 2019

BovineEnthusiast commented Aug 5, 2019

scalp42 commented Aug 6, 2019

rehevkor5 commented Aug 13, 2019 • edited Loading

mikhailadvani commented Sep 5, 2019 • edited Loading

kartvep commented Sep 23, 2019

kartvep commented Sep 24, 2019 • edited Loading

fernanen commented Dec 11, 2019 • edited Loading

vianel commented Feb 3, 2020

jessesanford commented Feb 4, 2020

vazhnov commented Feb 20, 2020

llamahunter commented May 18, 2020

amitcloudworld commented Jun 26, 2020

sosimon commented Aug 26, 2020

dyegoe commented Apr 19, 2021

thinkspill commented Apr 19, 2021

freakinhippie commented Apr 19, 2021

bflad commented Apr 19, 2021

saivarunr commented Apr 20, 2021

saivarunr commented Apr 20, 2021

pschulten commented Apr 23, 2021

brikis98 commented Apr 27, 2021

brikis98 commented Apr 27, 2021

antondemidov commented Apr 29, 2021

mhvelplund commented May 25, 2021

breathingdust commented Jan 11, 2022

markhuge commented Mar 8, 2022

github-actions bot commented May 10, 2022

BovineEnthusiast commented Jun 18, 2019 •

edited

Loading

rehevkor5 commented Aug 13, 2019 •

edited

Loading

mikhailadvani commented Sep 5, 2019 •

edited

Loading

kartvep commented Sep 24, 2019 •

edited

Loading

fernanen commented Dec 11, 2019 •

edited

Loading