내용으로 건너뛰기

IPv6 support in AWS

1

There are a bunch of AWS services that do not support IPv6. For instance, Kinesis Firehose - my instance is unable to make Firehose API calls because it does not have a public IPv4 address.

I'm very disappointed that AWS lags so far behind in IPv6 adoption, especially when we're being charged extra for a public IPv4 address just so that we can communicate with AWS services.

질문됨 2년 전538회 조회

2개 답변
0

While the lack of IPv6 support in some AWS services is a limitation, using strategies like NAT Gateways, VPC Endpoints, and IPv6 transition mechanisms can help mitigate the issue. These solutions provide ways to enable communication with AWS services that require IPv4 without incurring additional costs for public IPv4 addresses. Keeping abreast of AWS updates is also crucial to leveraging new IPv6 capabilities as they become available.

전문가

답변함 2년 전

  • NAT gateways, VPC endpoints, and public IPv4 addresses all add costs. I should be able to communicate between my EC2 instance (which I pay for) and any AWS Service (which I pay for) and not have additional charges just for them to be able to communicate.

0

Although I dislike that a NAT gateway is required, I did find an officially-supported workaround for this issue:

  • Create a NAT gateway, if you don't already have one.
  • In the VPC routing table associated with the subnet for that instance, create a route for all traffic to '64:ff9b::/96' that forwards to the NAT gateway.
  • Make sure that DNS64 is enabled for the subnet.

Now, when an IPv6-only instance tries to talk to an IPv4-only AWS service, the DNS64 resolver will respond to the AAAA lookup with a special IPv6 address that starts with 64:ff9b, and has the IPv4 address embedded inside of it. This will route to the NAT gateway which will then un-wrap the IPv4 address and forward the request to the appropriate IPv4 endpoint.

답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

관련 콘텐츠