- Newest
- Most votes
- Most comments
Hello realtebo,
please look at the solution it will be helpful for you
When attempting to attach an AWS Elastic Load Balancer (ELB) to an IPv6-only subnet, a limitation arises due to ELB's requirement of at least 8 free IP addresses in each subnet, which is designed for IPv4 subnets. Unfortunately, ELB doesn't currently support IPv6-only subnets. To work around this constraint, one option is to create dual-stack subnets supporting both IPv4 and IPv6, allowing ELB attachment to the IPv4 portion. Alternatively, consider using AWS Application Load Balancer (ALB), which supports dual-stack endpoints and thus accommodates IPv6 traffic. Another approach involves directly routing IPv6 traffic to instances if they support IPv6.
Could you please find the below link if you get more information and if you follow step by step:
https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
"ELB doesn't currently support IPv6-only subnets" . Does it mean it need a public ipv4 or a private ipv4 ? if it requires a ipv4, it's not a problem, we will convert ipv6-only subnet to dual-stack subnet. We are doing all the needed to completely throw away elastic ip and any other paid ipv4
"Allocate IPv4 addresses to your IPv6-only subnets, effectively converting them to dual-stack subnets. You can do this by associating Elastic IPs (EIPs) with instances in those subnets or by using NAT Gateways for outbound traffic. Modify your ELB configuration to use these dual-stack subnets. Go to the AWS Management Console, navigate to the Load Balancers section, select your ELB, and update the subnets associated with it to include the newly converted dual-stack subnets. Verify that your application can still be accessed through the ELB using both IPv4 and IPv6 addresses". Test connectivity from both IPv4 and IPv6 clients to ensure that traffic is properly routed through the ELB to your backend instances.