3 ms·
Is the gateway described here: https://aws.amazon.com/blogs/aws/let-your-ipv6-only-workloads-connect-to-ipv4-services/ https://aws.amazon.com/blogs/aws/let-your
by jeroenhd 3y ago
Is the gateway described here: https://aws.amazon.com/blogs/aws/let-your-ipv6-only-workloads-connect-to-ipv4-services/ https://aws.amazon.com/blogs/aws/let-your-ipv6-only-workload... no longer available?
- ianburrell 3y agoI didn't know about that.
- lxgr 3y agoThat's the wrong direction (IPv6 clients calling IPv4 services). That doesn't help you for running a service yourself.
- dastbe 3y agoyou can run an NLB that terminates v4 and forwards to v6 internally: https://aws.amazon.com/about-aws/whats-new/2020/11/network-load-balancer-supports-ipv6/ https://aws.amazon.com/about-aws/whats-new/2020/11/network-l...
- cyberax 3y agoELBs (Elastic Load Balancer) supported IPv6 termination since 2011.
- jeroenhd 3y agoYou'll need something it you want to download files from Github, because for some stupid reason they still don't provide IPv6 services for cloning and such.
- mnutt 3y agoIt looks to be available, but (from the bottom of the article) "Regular NAT gateway charges may apply."
- jwlake 3y agoYes the problem is NAT gateways are expensive, not free. AWS could easily run a "central" 6 to 4 in each region (not in your VPC), which the incremental cost of using would be near 0. Then you could use pure v6 (no IP charges). And actually be able to talk to things like github, stripe, apple, etc.