Switch to IPv6 from Ipv4

Question

We are building a website and we recently saw some charges related to a Public IPv4 address used on the App server(EC2 instance). I did some reading and found out that AWS does not charge for IPv6 addresses. Our DB server is an RDS and is within a private subnet. 
We are still in Development and hope to migrate to Production in the next 2 months.
I want to know if there are any cons to moving to IPv6, from a general perspective and AWS perspective. I have been reading some articles on the web and I couldn't find anything major that advised against the transition to IPv6 for a new application. Thanks for your help in advance.

Accepted Answer

Hello.

I think the disadvantage of moving to IPv6-only is that users who currently use ISPs that can only use IPv4 will not be able to access applications.  
Additionally, some AWS services do not support IPv6, so applications may not be able to access AWS services until IPv6 is supported.  
If the cost of IPv4 is not acceptable, I think it is better to use only IPv6 only.  
https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html

Therefore, I thought it would be a good idea to host IPv4 and IPv6 in a dual stack at first, and then transition to IPv6-only in the future.  
IPv6 has greater advantages than IPv4, but support is delayed in some aspects, so you must accept these disadvantages when using them.

Answer

Hi

Please look at the resources posted https://repost.aws/questions/QUPlstoCQoSOmzt15LMd0C1g/migrating-from-an-ipv4-network-to-an-ipv6-network

**Alternative Solution:**
 Using a private network Ec2(Without Public IP) with a frontend Application Load Balancer (ALB) is a great alternative

https://docs.aws.amazon.com/whitepapers/latest/how-aws-pricing-works/architecture.html#:~:text=ELB%20balances%20traffic%20to%20the,enhances%20data%20durability%20and%20availability.

Switch to IPv6 from Ipv4

Relevant content