Virtual Private Cloud

AWS uses a Virtual Private Cloud (VPC) to create a virtual network that resembles a traditional network.
Your cloud controller and clusters are launched into AWS network infrastructure and depending on with which
deployment options, you can use existing VPCs or have new VPCs created for you.

Clusters

(Default) To have the cluster created in the same VPC as the cloud controller but in a new subnet, or

To have the cluster created in a different existing VPC and an existing subnet

Creating Clusters into a Different VPC

By default, cluster node instances are installed into the same VPC as the cloud controller instance and a new subnet is created for each cluster:

Optionally, you can select to create clusters in your own existing VPC and subnet. This choice is available
under NETWORK & SECURITY > Advanced when creating your cluster.

When you launch a cluster inside a different VPC than the one in which your cloud controller is running, make sure that the VPC configuration fulfills the requirements listed in Configuring Your Own VPC.

Configuring Your Own VPC

If using your own VPC, make sure that:

You have either two private subnets or two public subnets available to create an Amazon RDS DB subnet group for an RDS DB instance to use in a VPC.

The subnet specified when creating a controller or cluster exists within the specified VPC.

Your VPC has an Internet gateway attached.

Your VPC has a route table attached.

The route table includes a rule that routes all traffic (0.0.0.0/0) to the Internet gateway.

The DNS resolution and DNS hostnames are set to “yes”:

Learn More

For instructions on how to create a VPC for an RDS DB instance, refer to this Amazon tutorial.