News for hackers. Stuff that matters.
Re:The IPv6 Transition by thayne on Sunday October 20, 2024 @05:23PM (#41898591)
Yep, lots of AWS apis don't work over ipv6, and many require making requests outside the VPC, so you need to have at least one ipv4 address for a NAT.
Re:The IPv6 Transition by cyberax on Monday October 21, 2024 @01:05PM (#41906107)
You can use NAT64, it works with all the AWS services. Although it's pretty stupid that services like ECR don't have IPv6.
Re:The IPv6 Transition by thayne on Monday October 21, 2024 @02:18PM (#41906812)
NAT64 requires you to have a NAT with a public ipv4 address. Or possibly pay to use someone elses NAT.
Re:The IPv6 Transition by cyberax on Monday October 21, 2024 @02:47PM (#41907123)
AWS supports NAT64 automatically if you have an Internet gateway attached, you just need to set it up in the VPC settings.
Re:The IPv6 Transition by thayne on Monday October 21, 2024 @04:00PM (#41907924)
https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway...

Says you need to have an AWS NAT for that to work. And AFAIK, setting up a NAT requires an ipv4 elastic ip.

And it makes since that AWS would want customers to have their own IP for NAT64, so that if one customer does something to get the ip address blocklisted it doesn't impact other customers.

Re:The IPv6 Transition by cyberax on Monday October 21, 2024 @09:30PM (#41910308)
Yes, you're correct.

Though I don't think AWS cares too much about IP blocklist, you can always just get another elastic IP at any moment.