1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta 6 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 8 mesi fa
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.