-
Step 1: In the AWS console search field, type in "VPC" and select the VPC service.
-
Step 2: You should see a list of your VPCs organized by region. Click the "Create VPC" button.
-
Step 3: A new tab will open. Ensure the "VPC and more" option is checked.
For the "Name tag auto-generation" section, add a name that will allow you to identify these
resources later. The author used "testSbS", as this VPC is for testing during future
step by step guides. If you want a VPC for production use, choose a name that makes sense.
Note: once you enter the name, the names of the resources in the right hand box will update.
-
Step 4: Scroll down. You should leave the defaults, assuming they include two AZs, two
public subnets, and two private subnets.
-
Step 5: Scroll down. Under "NAT gateways" select "Zonal". You can select "In 1 AZ" to
reduce costs. Be aware that you may need "1 per AZ" if you want higher availability, depending
on your use case. The author selected "1 per AZ." You can leave or remove the S3 Gateway; it
is not needed for this guide.
-
Step 6: Scroll down. Leave the DNS settings checked. Click the "Create VPC" button.
-
Step 7: You will see a status screen that shows the steps AWS is taking. Note that it
may take a few minutes for this process to finish. Scroll down and click the "View VPC" button
when done.
-
Step 8: You will need to configure the public subnets in your VPC to automatically assign
public IP addresses to resources such as EKS pods launched in the VPC.
Note: if you change this setting for the public subnets in your VPC after pods have been deployed,
they will not get a public IP address. The setting to automatically assign public IP addresses
must be set before the pods are deployed.
Click on the "Subnets" menu option on the left. You should see a list of your subnets.
If you have a default VPC in the same region, you can see the subnets related to the new VPC
via the "Name" column. You should see both public and private subnets.
-
Step 9: For each of the public subnets you created for the VPC above, you will need to
enable the "Auto-assign public IPv4 address" setting.
Note: this only applies to public subnets, not private subnets.
Click on the "Subnet ID" field to open the details page.
-
Step 10: Note that the Auto-assign public IPv4 address field is set to No.
-
Step 11: Click on the "Actions" button and select "Edit subnet settings."
-
Step 12: In the new screen, check the box for "Enable auto-assign public IPv4 address".
Scroll to the bottom of the page and click the "Save changes" button.
-
Step 13: You should be prompted with a green banner at the top of the page that confirms
your changes. You should also see the Auto-assign public IPv4 address field is now set to Yes.
-
Step 14: Repeat these steps for the other public subnet in your VPC.
This completes this guide.