Associating an Amazon VPC and a private hosted zone that you created with different AWS accounts - Amazon Route 53

Associating an Amazon VPC and a private hosted zone that you created with different AWS accounts

If you want to associate a VPC that you created with one AWS account with a private hosted zone that you created with a different account, perform the following procedure:

To associate an Amazon VPC and a private hosted zone that you created with different AWS accounts
  1. Using the account that created the hosted zone, authorize the association of the VPC with the private hosted zone by using one of the following methods:

    Note the following:

    • If you want to associate multiple VPCs that you created with one account with a hosted zone that you created with a different account, you must submit one authorization request for each VPC.

    • When you authorize the association, you must specify the hosted zone ID, so the private hosted zone must already exist.

    • You can't use the Route 53 console either to authorize the association of a VPC with a private hosted zone or to make the association.

  2. Using the account that created the VPC, associate the VPC with the hosted zone. As with authorizing the association, you can use the AWS SDK, Tools for Windows PowerShell, the AWS CLI, or the Route 53 API. If you're using the API, use the AssociateVPCWithHostedZone action.

  3. Recommended – Delete the authorization to associate the VPC with the hosted zone. Deleting the authorization does not affect the association, it just prevents you from reassociating the VPC with the hosted zone in the future. If you want to reassociate the VPC with the hosted zone, you'll need to repeat steps 1 and 2 of this procedure.

    Note

    For the maximum number of authorizations that you can create, see Quotas on entities.