By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

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

Topics
Networking & Content Delivery
Tags
IPv6
Language
English
SpaceVerse
asked 6 months ago394 views
1 Answer
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
answered 5 months ago
  • SpaceVerse
    5 months ago

    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.

  • AmerO
    5 months ago

    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.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content