aws_route53_vpc_association_authorization - is this working as intended? #18176
Labels
question
A question about existing functionality; most questions are re-routed to discuss.hashicorp.com.
service/ec2
Issues and PRs that pertain to the ec2 service.
service/route53
Issues and PRs that pertain to the route53 service.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
Terraform version:
terraform_0.13.0
terraform_0.12.1
Issue: Following the documentation example works fine. However, i think this moves away from the actual real world example of a cross account vpc that has not been created by the terraform plan initiating the authorization. If you try and associate a vpc created outside the authorizing account, I still get a 401 saying that the authorizing account does not have rights to associate the vpc from the other aws account to the authorizing accounts private zone, even though the authorization resource has been created.
#14215
#12362
Im guessing the issue is here... arn:aws:ec2:eu-west-2:THISACCOUNT:vpc/vpc-001THATACCOUNT
The only difference from the example in the documentation is that the second accounts vpc is not created in the same tf plan .
The text was updated successfully, but these errors were encountered: