To create a custom VPC (Virtual Private Cloud) in AWS, you use the "VPC only" option in the AWS Management Console to define your own virtual network space and core configurations.
A custom VPC provides granular control over your network environment, allowing you to specify IP address ranges, subnets, route tables, network gateways, and security settings according to your specific requirements. The process involves configuring the basic network parameters of the VPC itself before adding other components like subnets.
Steps to Create a Custom VPC
Follow these steps to create a custom VPC using the AWS console:
- On the VPC dashboard in the AWS Management Console, choose Create VPC.
- For Resources to create, select the VPC only option. This choice allows you to build your network infrastructure manually after creating the base VPC.
- (Optional) For Name tag, enter a descriptive name for your VPC. This helps in identifying your VPC easily among others.
- For IPv4 CIDR block, enter the primary IPv4 address range for your VPC. This block must be a valid CIDR block (e.g.,
10.0.0.0/16,172.31.0.0/16,192.168.0.0/16). This is a required field. You can add secondary IPv4 CIDR blocks later if needed. - (Optional) To create a dual-stack VPC that supports both IPv4 and IPv6 traffic, you can specify an IPv6 CIDR block. You can choose to let Amazon assign an IPv6 CIDR block or associate one you own.
- (Optional) Choose a Tenancy option for the instances launched into your VPC.
Default: Instances run on shared hardware (this is the default and recommended for most use cases).Dedicated: Instances run on single-tenant hardware dedicated to you.
Once you have configured these options, you can proceed to create the VPC. After creation, you will need to manually add subnets, internet gateways, route tables, and other network components to make the VPC functional for hosting resources.
Key Configuration Options Overview
Here's a summary of the main options when creating a custom VPC:
| Option | Description | Requirement |
|---|---|---|
| Resources to create | Defines whether only the VPC is created (VPC only) or if subnets and other components are also set up (VPC and more). Choose VPC only for a custom setup. |
Required |
| Name tag | Assigns a name to your VPC resource. | Optional |
| IPv4 CIDR block | Specifies the primary private IPv4 address range that your VPC will use. Must be a valid CIDR block. | Required |
| IPv6 CIDR block | Adds an IPv6 address range, enabling dual-stack networking support. | Optional |
| Tenancy | Determines if instances launched in the VPC run on shared or dedicated hardware. | Optional |
By following these steps and selecting the "VPC only" option, you establish the foundation of your custom network environment in AWS.
