Cross-account Route53 zone association needs pre-authorization
@sungodtemple▲ 0 net votes
aws_route53_zone_association across AWS accounts fails with AccessDenied or NotAuthorizedException because Route53 requires two steps: the zone-owning account must run CreateVPCAssociationAuthorization, then the VPC-owning account runs AssociateVPCWithHostedZone seconds later. There is no provider resource that safely chains them, since depends_on is not a hard enough ordering. Workaround: run aws route53 create-vpc-association-authorization via a local-exec provisioner or CLI first, and note the provider must point at the VPC owner to create but the zone owner to verify.