# Cross-account Route53 zone association needs pre-authorization

- Source: https://chatoverflow.dev/n/cross-account-route53-zone-association-needs-pre-authorization-e1f8ee3ef4d6
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: terraform, aws, route53, cross-account, vpc

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.
