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

aws_elb_service_account errors for GovCloud region us-gov-west-1 #3373

Closed
mgresko opened this issue Feb 14, 2018 · 4 comments
Closed

aws_elb_service_account errors for GovCloud region us-gov-west-1 #3373

mgresko opened this issue Feb 14, 2018 · 4 comments

Comments

@mgresko
Copy link

mgresko commented Feb 14, 2018

Terraform is erroring out on Govcloud region when trying to get the elb service account

Terraform Version

Terraform v0.11.3

  • provider.aws v1.1.0
  • provider.template v1.0.0

Affected Resource(s)

  • aws_elb_service_account

Terraform Configuration Files

data "aws_elb_service_account" "main" {}

data "aws_iam_policy_document" "logging" {
    statement {
        sid = "AllowLogsWritten"
        effect = "Allow"
        principals = {
            type = "AWS"
            identifiers = ["${data.aws_elb_service_account.main.arn}"]
        }
        actions = ["s3:PutObject"]
        resources = [
            "${aws_s3_bucket.logging.arn}/log/*"
        ]
    }
}

Expected Behavior

The region should be found and resolve the account id 048591011584. https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-access-logs.html

Actual Behavior

Terraform error

Error: Error refreshing state: 1 error(s) occurred:

* data.aws_elb_service_account.main: 1 error(s) occurred:

* data.aws_elb_service_account.main: data.aws_elb_service_account.main: Unknown region ("us-gov-west-1")

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform apply

Important Factoids

GovCloud

References

@mgresko
Copy link
Author

mgresko commented Feb 14, 2018

Nevermind... this is fixed in a newer version of provider. Unfortunately, I am stuck at v1.1.0 until #2534 is fixed. :(

@mgresko mgresko closed this as completed Feb 14, 2018
@bflad
Copy link
Contributor

bflad commented Feb 14, 2018

@mgresko looks like this was actually fixed this week in #3315 and already merged into master. This will be released with v1.10.0 of the AWS provider, likely next week.

@mgresko
Copy link
Author

mgresko commented Feb 14, 2018

@bflad if #2534 could make it in v1.10.0 then all would be well :)

@ghost
Copy link

ghost commented Apr 8, 2020

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 Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants