1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
If your workloads need both public IPv4 and IPv6 addresses for communication, you may prefer the dualstack Lightsail instances listed here under Bundles with public IPv4 address.
The Bundles with IPv6 address only listed above are meant for workloads that don't need to communicate over public IPv4. They however do still have a private IPv4 address and coupled with Lightsail's VPC Peering option, you could, use a NAT64 in EC2 with your Lightsail IPv6 bundle instances.
Thanks.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
AWS OFFICIELA mis à jour il y a un an
Even GitHub does not support IPv6, So It is required to use NAT64, DNS64 for connecting to them. (I don't need public IPv4 address for inbound, Just needs NAT-ed outbound.)
So you mean, I can peering with VPC to use NAT64, DNS64?
Yes we understand, everybody is still catching up to IPv6 unfortunately :|
If you have NAT64 and DNS64 setup in EC2 to work with your Default VPC, and then peer with Lightsail VPC, you should be able to get the IPv6 bundle instances to work with it.