aws-ip-ranges VS cloud

Specifically, I used a little script I have that made this animation, which is part of my AWS IP Range's repo.

And yeah, this means lots of EC2 instances have their own IP address. This is why AWS hash over 74 million public IPv4 addresses, and why the mass majority of them, something like 75%, are used for EC2.

Just a heads up, AWS just added 4,718,592 new IPs in their second largest expansion to date.

> Moreover, we did not find any 240/4 prefix in the official prefix list shared by Amazon

Yeah, so about that:

https://github.com/seligman/aws-ip-ranges/commit/2e0d9d87d4f...

They did briefly list 252.0.0.0/10 in their published list of IP ranges. The people I spoke with about this at the time either claimed it was a mistake, or the state of the world that I should get used to (it broke some surprisingly fragile scripts on my side for silly reasons).

Given they removed it from their list of IPs 27 hours later, I'm guessing I wasn't the only person freaking out. But yeah, they use it internally, and it leaks from time to time in surprising ways.

They have north of 66 million IP addresses, so if they're running out, that's an impressive feat.

History of AWS's IP Ranges, and a more recent history/comparison of the size of IP Pools of different Cloud Providers

This is sourced from a document that AWS publishes, called ip-ranges.json, as archived in my GitHub repo, with a little help from the Internet Archive's Wayback Machine for the first year or so of data before I was archiving changes via a script.

According to https://github.com/seligman/aws-ip-ranges, they have acquired 5,505,024 IPv4 address on Aug 12. This apparently their largest purchase to date, and puts them in control of 1.75% of all IPv4 address. In the world.

AWS adds an extra 5.5M IPv4 addresses\ (146 comments)

It’s not just BigQuery. Pricing for cloud services is increasing across every provider. Azure increased prices in the EU recently https://news.microsoft.com/europe/2023/01/05/consistent-glob...

For AWS, one of the people behind https://ec2instances.info showed that the price/performance ratio for newer instances is rising, https://github.com/patmyron/cloud/#compute--memory-unit-pric... meaning cloud users are paying more for less.

Incredible writeup! Unfortunate ap-northeast-3's so prevalent since it's usually the smallest and least supported public AWS region due to being a ["local region" with only 1 public AZ for years](https://aws.amazon.com/blogs/aws/aws-asia-pacific-osaka-regi...):

https://github.com/patmyron/cloud/

---

ap-northeast-1, eu-west-1 seems like the best pair sticking to AWS regions that have most resource types available

luckily not one of the largest regions:

https://github.com/patmyron/cloud/#ip-addresses-per-region

relative availability per region graphed here