AWS targets IPv6 migration for serverless container workloads

Amazon Web Services has propeled new support for IPv6-only subnets that can meet the needs of workloads that demand more IP addresses than IPv4 can readily prepare.

The labor is useful through Amazon Virtual Private Cloud (VPC) and suitable for workloads such as serverless and container applications according to a blog by Rohit Aswani a senior specialist solutions constructor and Aditya Santhanam a senior fruit director both with AWS. ’Workloads that are constrained by the limited size of the IPv4 address space can now migrate to an IPv6-only environment on AWS to layer up’ they wrote.

IPv6 deployment lead

’Additionally with this propel customers will be able to meet the demandments for adoption of IPv6-only network environments set by US federal government agencies and minimize the need for translation software or systems thereby creating a simplified IPv6-only constructorure.’

The all-IPv6 subnets are created within Amazon VPCs that support both IPv4 and IPv6 and they can be used as a locate to propel Elastic Compute Cloud (EC2) instances built on the AWS Nitro System. Nitro is AWS-built hardware and software that boost accomplishment availability and security.

Because the pool of IPv6 addresses that can be drawn on is approximately 18 quintillion the labor allows deployments to layer without requiring any IPv4 addressing in the subnet Aswani and Santhanam wrote.

AWS also made it easier to support mixed IPv4 and IPv6 workloads. The company said users can set their AWS load balancers to dual-stack mode letting it welcome both IPv4 or IPv6 client connections.

’While dual stack mode on internet-facing load balancers has been useful this propel extends support for inner load balancers by adding protections to help hinder unintended internet approach via IPv6 through an internet gateway’ AWS stated. Additionally application and network load balancers now support load balancing to targets with IPv6 addresses.

IPv6-only subnets IPv6-only EC2 instances as well as the load balancer dual-stack support are useful in all open AWS Regions.

The labor helps address the main problem that IPv6 was created explain: IPv4 addresses were running out. ’An increasing number of organizations are adopting IPv6 in their environments driven by the open IPv4 space exhaustion special IPv4 deficiency especially within large-layer networks and the need to prepare labor availability to IPv6-only clients’ Alexandra Huides an AWS senior networking specialist solutions constructor wrote in an earlier blog almost IPv6 options. 

IPv6 propeled in 2012 but as of November 2021 and despite its efficiency and security advantages adoption is somewhere between 32% and 37% according to Google.