VPC and subnets
When registering an AWS environment in CDP, you will be asked to select a VPC and two or more subnets.
You have two options:
- Use your existing VPC and subnets for provisioning CDP resources.
- Have CDP create a new VPC and subnets. All CDP resources will be provisioned into this new VPC and subnets.
Existing VPC and subnets
Verify the limits of the VPC and subnets available in your AWS account to ensure that you have enough resources to create clusters in CDP.
If you would like to use your own AWS VPC, it must meet the following requirements.
Depending on the CDP services that you are planning to use, you may also need the following:
New VPC and subnets
If you choose to allow CDP to create a new VPC, three subnets will be created automatically. One subnet is created for each availability zone assuming three AZs per region; If a region has two AZs instead of three, then still three subnets are created, two in the same AZ.
You will need to specify a valid CIDR in IPv4 range that will be used to define the range of private IPs for EC2 instances provisioned into these subnets. Default is 10.10.0.0/16. Consider changing the IP range to correspond to corporate policies for standardized IP address ranges. The CIDR must match the <network mask>/16 pattern.
- 3 x /19 private subnets for FreeIPA, Data Lake, Data Hub, Data Warehouse, Machine Learning
- 3 x /24 public subnets
You can disable creating private subnets, in which case only 3 public subnets will be created.
By default, when creating a new network, CDP uses public endpoints. But during environment registration you can optionally select the “Create Private Endpoints” option to use private endpoints instead of public endpoints.
If you choose to use private endpoints, make sure to review Outbound network access destinations.