3 ms·

I am also curious what your use-case is for every instance inside of your VPC having a publically routable IPv6 address. Usually you only need public addresses

• jdub 10y ago
  Use case: Never having to maintain a NAT instance (or, worse, but necessary: failover NAT instances). That's how I tend to use AWS at the moment, with IPv4. Almost every resource (except AWS services) has a public IP assigned, few have open inbound security groups, most have open outbound security groups (but the option to restrict is handy).
• knorrie 10y ago
  An instance might want to reach anything on the internet that's using an IPv6 address is a use case. Also, having instances connect to IPv6 parts of the internet while you can see which subnet of your vpc the traffic originates from, and maybe filter on that fact. Having routable addresses is a different thing than them being public or private, which is determined by the fact if you accept traffic to them or not when it arrives at the last hop before entering your vpc.
• lmm 10y ago
  It's still nice to be able to give each host a globally unique address even if most of them aren't publicly accessible. It means that you never e.g. have routing clashes when VPNing into your datacenter from public wifi somewhere.