3

I configured my Elastic Load Balancer to work as dualstack. I created records set on Route 53 with types A and AAAA pointing to Elastic Load Balancer. Over IPv4, it works

I used this site to test my site over IPv6: ipv6-test.com/validate.php

And it returns the following:

enter image description here

What I need to do to get the others two steps working?

VPC, Subnets and instances are configured to accept IPv6

Edit:

Route table:

enter image description here

  • 1
    Did you test an individual instance before you tested the ELB? Did you follow the instructions in the AWS EC2 IP6 guide? You didn't mention security group rules above, you may need to allow IP6 there or your NACLs. – Tim Dec 10 '17 at 18:04
  • Yes, I tested and worked. According to Amazon, ELB communicate with instance over IPv4 independently user connection type, however, the instances are configured to accept both. My security groups and NACLs are ok to IPv6 too. – dm707 Dec 10 '17 at 18:25
  • Not much anyone can do to help you with the information you've given. You're going to have to use a process of elimination. – Tim Dec 10 '17 at 18:56
  • I understand.. I tried to search but I didn't found something to help. Maybe someone faced the same issue and found some solution. But thanks to try @Tim – dm707 Dec 10 '17 at 19:13
  • 1
    Are your EC2 instances in a private or public subnet? Your route table has both EIGW and an IGW. The EIGW is for a private subnet. Also you have a static route for "2600:1....". If your EC2 instances are in a public subnet, remove the EIGW and the 2600... static route. If your EC2 instances are in a private subnet, create new a route table for the private subnet and put a NAT Gateway and EIGW in the private subnet route table and remove the EIGW and the 2600 .... from the public route table. – John Hanley Dec 10 '17 at 22:49
8

There is a long thread of comments on this question.

The solution is to change the route table to use the IGW (Internet Gateway) instead of the EIGW (Egress-Only Internet Gateway) to route the IPv6 traffic. Routing the IPv6 traffic thru the EIGW, in effect, makes the load balancers private and not publicly accessible.

0

I had similar problem but without Egress-Only Internet Gateway.

It was happening because my Application Load Balancer was configured with ELBSecurityPolicy-TLS-1-2-2017-01 and ipv6-test.com only supports up to ELBSecurityPolicy-2016-08.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.