How To Configure IPv6 in AWS VPC (4 Min)

In this tutorial, you’ll learn how to configure IPv6 in AWS VPC.
—
Facebook: https://www.facebook.com/GokceDBsql
—
Video Transcript:
—
Hi guys, this is Abhi from Gokcedb. In this video, you’re going to learn how to configure IPv6 in your AWS VPC. Let’s start by navigating to the VPC service and then hitting the create VPC button. Give your VPC a name then select an ipv4 cider block.

For the 1Pv6 cider block, select the Amazon-provided option then select default. For tenancy, I’m going to select one for the Availability Zone, one for the public subnet, and one for the private subnet. Since I don’t want internet access in my internet private subnet, I’m going to select none for Nat Gateway and none for egress internet gateway.

Hit create VPC then wait for the VPC workflow to complete. Click on subnets in the left menu and confirmed that Public Sub and one private subnet for your Project VPC. In your private route table, you should only see local routes and in your public route table, you should see both local routes and routes to the internet gateway.

Click on Internet gateways and you should see one internet gateway attached to your project VPC. Next, create a security group and give it a name. Give it a description then select the project VPC from the VPC drop-down in the inbound rules section.

I’m going to add a rule for SSH from anywhere ipv4 and SSH from anywhere IPv6. Let’s also add a rule for ICMP from anywhere ipv4 and ICMP from anywhere IPv6. Click on create Security Group button then navigate to the ec2 dashboard.

Click on instance then hit launch instances. Give your instance a name, select an Ami then click on edit in network settings. Select project VPC then choose the private subnet.

Select disable for auto-assign public IP and enable for auto-assign IPv6 IP. Select the security group that we just created for the hit launch instance. Hit the refresh button and you should see your private instance in a pending State.

Let’s launch one more instance in our public subnet in the network settings. Select the project VPC and this time choose the public subnet. Enable auto-assign public IP and IPv6 then select our security group.

Hit launch instance then click on refresh and you should see our new instance in a pending state. For our public instance, you can see both our public ipv4 address and an IPv6 address attached to it. However, for our private instance, we only see the private ipv4 address and an IPv6 address.

Next, let’s SSH into our public using ec2 instance connect. I’m going to grab the IPv6 address of the private instance and then use the Ping 6 command to ping that server over ICMP V6. Looks like it was successful.

Now, watch what happens if I go back to our security group and delete the ICMP V6 rule. This time if I try to Ping our private server, I get a 100 percent loss. There you have it.

Make sure you like, subscribe, and turn on the notification bell. Until next time. .