3 ms·
Anther example of big cloud providers not taking v6 seriously - AWS wouldn't even let your IPv6 hosts talk to their API: $ dig +short a ec2.amazonaws.com 5
by nousermane 5y ago
Anther example of big cloud providers not taking v6 seriously - AWS wouldn't even let your IPv6 hosts talk to their API:
$ dig +short a ec2.amazonaws.com
52.46.140.46
$ dig +short aaaa ec2.amazonaws.com
(no response)
- usrlocal1023 5y agoThey now have a dual stack EC2 API endpoint. But you have to go out of your way to use as it is on a totally different domain, and also it is limited to few regions. us-east-2 region for example api.ec2.us-east-2.aws https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Using_Endpoints.html#ipv6 https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Using...
- colmmacc 5y agoOur reason for this is that customers may have IP-based rules in their IAM policies. If we silently turned on IPv6 for existing endpoints, those policies would suddenly break without notice. Hence new names and SDK options for dual-stack.
- corty 5y agoSame with GCP, they just announced IPv6 availability for VMs in the last few days. Unbelievably you couldn't even get a IPv6 address for a GCP instance up to now! APIs don't work over IPv6, and lots of other stuff doesn't as well.