AWS supports VPC Sharing, which allows customers to easily span out a single VPC across multiple participating accounts belonging to the same organization, where customers can create resources like EC2, Lambda, and others.
Starting with NSX Advanced Load Balancer version 22.1.2, shared VPC is supported for virtual services deployed in the AWS environment.
For more information on AWS Shared VPC, see Shared VPC.
Shared VPC has the following advantages.
Creating fewer VPCs to deploy the same workload as VPCs are shared across accounts.
High density of CIDR block usage for VPC subnets. Using shared VPCs avoids CIDR overlap issue that is encountered with multiple VPCs.
Prerequisites for Private Hosted Zone
When creating a Private Hosted Zone in Route53, a VPC association is required for the Hosted Zone to resolve queries. In the case of a shared VPC, a prior association with the owner account, as described below, is needed:
Create Association Request from Participating Account (the one creating the Private Hosted Zone). For more information, see Create VPC Association Authorization.
Create Association from the Owner Account with VPC and Hosted Zone ID. For more information, see Associate VPC With Hosted Zone.
Go to the Private Hosted Zone and click .
The following are the ways to create VPC Association:
AWS CLI
AWS SDK
AWS Route53 API
VPC association is not required for Public Hosted Zones.
