VPC and subnet (optional)

For getting started, CDP can create a VPC and subnets for you, but for production you may want to use your own VPC.

If you would like to use your own VPC, it needs to fulfill the following requirements:
  • The VPC has at least two subnets, each in a different availability zone.
  • The VPC subnets must be connected to an Internet Gateway OR a NAT Gateway. VPC should be able to make an outbound connection with the internet or set of CIDRs and ports provided by Cloudera.
  • Only public subnets are supported at this time.
  • If you are planning to use the Machine Learning service, you must tag the VPC and the subnets as shared so that Kubernetes can find them. For load balancers to be able to choose the subnets correctly, you are also required to tag private subnets with the kubernetes.io/role/internal-elb:1 tag, and public subnets with the kubernetes.io/role/elb:1 tag. For more information, refer to AWS account prerequisites for ML workspaces.

VPCs can be created and managed from the VPC console on AWS. For instructions on how to create a new VPC on AWS, refer to Create and configure your VPC in AWS documentation.