Will Route53 Private Hosting Network Work on AWS VPC Peering in Two Accounts
I have a similar question: Will the Route53 private hosting network work on AWS VPC Peering , but with one difference.
Is it possible to install the same scenario when the two VPCs are in different accounts? So the hosted zone is in the same account with one VPC, and there is a second VPC, but in a different account (connected via VPC Peering).
source to share
Yes, you can use the private area with route 53 with a different account.
If you would like to link a VPC created with one AWS account to a private hosting zone created with a different account, follow this procedure:
To link an Amazon VPC and a private hosting zone created with different AWS accounts
Using the account that created the hosting zone, authorize the VPC to communicate with the private hosted zone using one of the following methods:
AWS SDK or AWS Tools for Windows PowerShell - See the related documentation on the AWS AWS CLI - See the route53 page in the Amazon Route 53 AWS API CLI Reference - See CreateVPCAssociationAuthorization in the Amazon Route 53 API Reference Note the following:
If you want to associate multiple VPCs created with the same account with a hosted zone created with a different account, you must send one authorization request for each VPC.
When you enable the association, you must provide the ID of the hosted zone, so the private hosted zone must already exist. You cannot use the Amazon Route 53 console to authorize a VPC association with a private hosting zone or to create an association. Using the account that created the VPC, associate the VPC with the hosted zone. As with authorizing an association, you can use the AWS SDK, Tools for Windows PowerShell, AWS CLI, or the Amazon Route 53 API. If you are using the API, use the AssociateVPCWithHostedZone action.
Optional, but recommended, remove authorization to associate the VPC with the hosted zone. Removing the authorization does not affect the association, it just prevents you from reassigning the hosted zone VPC in the future. If you want to re-associate the VPC with the hosted zone, you will need to repeat steps 1 and 2 of this procedure.
Note For a limit on the number of permissions you can create, see Restrictions on Entities.
source to share