AWS to start charging for IPv4 usage, but critical services don't support IPv6
1–10 of 245 posts
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#2"A price hike by any other name costs just as much."
(I didn't bother looking for the quote's source.)
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#3IPv6 and Python3 are case studies in how not to roll out a new version unless you're cool with multi-decade upgrade windows.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#4Anyone that is surprised by this behavior from AWS probably has very little experience using it. The whole console is full of dark pattens to get you to setup larger than needed defaults and accidentally leave things running.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#5"A price hike by any other name costs just as much." (I didn't bother looking for the quote's source.)
It's James T. Kirk's. I think.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#6Do the other cloud providers give you IPv4 endpoints for free? I didn't think that was the case. (ie I thought AWS was just falling into line with the others on charging).
As for the "critical services not supporting IPv6" in the post I was quite surprised that it's such a short list of things that don't work - I would have expected more. They've obviously made a ton of progress.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#7IPv6 and Python3 are case studies in how not to roll out a new version unless you're cool with multi-decade upgrade windows.
Is there an alternative, though? Both Python3 and IPv6 both solve problems that would have been at least as painful to do incrementally, IMHO.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#8"A price hike by any other name costs just as much." (I didn't bother looking for the quote's source.)
Abraham Lincoln, I'm pretty sure.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#9Do the other cloud providers give you IPv4 endpoints for free? I didn't think that was the case. (ie I thought AWS was just falling into line with the others on charging). As for the "critical services not supporting IPv6" in the post I was quite surprised that it's such a short list of things that don't work - I would have expected more. They've obviously made a ton of progress.
DigitalOcean do.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#10Do the other cloud providers give you IPv4 endpoints for free? I didn't think that was the case. (ie I thought AWS was just falling into line with the others on charging). As for the "critical services not supporting IPv6" in the post I was quite surprised that it's such a short list of things that don't work - I would have expected more. They've obviously made a ton of progress.
Azure and Google Cloud don't, and they didn't have full ipv6 support when making the change either