Ec2 with IPv6, no public ipv4, how to make connection to dynamodb / s3 / ses ?

0

Connection to dynamodb / s3 / ses fails from the ec2 instance running with ipv6 address only, no public ipv4, how can it work?

It was working when I had a public ipv4

已提問 6 個月前檢視次數 421 次
1 個回答
0

Are you using VPC private endpoint to connect to these services? If so, you might need to enable IPv6 on the endpoints. Here is a nice blog to take you over the change needed: https://aws.amazon.com/blogs/networking-and-content-delivery/expedite-your-ipv6-adoption-with-privatelink-services-and-endpoints/ A typical path for an upgrade, ensure the SG and routing tables are updated: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html *However, some AWS services do not support IPv6 only like Dynamodb. * You can look at deploying NAT64 for your use-case where you want IPv6-only subnets to speak to IPv4 network. Check here: https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-nat64-dns64.html#nat-gateway-nat64-what-is

profile pictureAWS
AmerO
已回答 6 個月前
  • So in other words, it's not possible without using extra stuff that adds additional costs?

    The only reason I'm moving from ipv4 is that you make us pay for it after February.

    Yet you're not supporting IPv6 on your services like Dynamodb.

  • You can track changes in IPv6 adoption in this AWS doc. https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html If you find the information provided helpful, please accept the answer.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南