[Update: As predicted, these numbers are already out of date and Amazon has added more public IP address ranges for use by EC2 in various regions.]
Each standard Amazon EC2 instance has a public IP address. This is true for normal instances when they are first brought up and for instances which have had elastic IP addresses assigned to them. Your EC2 instance still has a public IP address even if you have configured the security group so that it cannot be contacted from the Internet, which happens to be the default setting for security groups.
Amazon has made public the EC2 IP address ranges that may be in use for each region.
From this information, we can calculate the absolute upper limit for the number of concurrently running standard EC2 instances that could possibly be supported in each region. At the time of this writing I calculate the hard upper limits to be:
| EC2 Region | Max Instances* |
|---|---|
| us-east-1 | 585,704 |
| us-west-1 | 98,298 |
| eu-west-1 | 135,156 |
| ap-southeast-1 | 43,000 |
| ap-northeast-1 | 34,808 |
*Caveats:
An upper limit based on the IP address ranges does not tell you what the real number of possible instances is in a given EC2 region. It’s just an upper limit.
Amazon is sure to keep requesting, reserving, and announcing more IP addresses than is actively needed by EC2 at any point in time. Only they know the growth buffer percentage that they like to maintain.
Amazon may need to use different ranges of IP addresses for different groups of instances in different parts of their network, even in the same data center or availability zone, so they may publish and start using new ranges of IP addresses even before they are even near using up the capacity of previous ranges.
Amazon is free to add new IP address blocks to the list at any time as they keep growing, and they do. The specific numbers above could be out of date by the time you read this.
There are probably some IP addresses in each range that are reserved for various networking devices and protocols.
This calculation is for concurrently running EC2 instances. Many instances run for just a few minutes or hours and another instance, perhaps for another customer, can start up and use that same IP address moments later.
EC2 instances running inside Amazon VPC don’t necessarily use up an external IP address in Amazon’s EC2 public IP address ranges, so they are not included in the upper limits.
I am not a networking expert. I only play one at my startup.
Anything else I’m missing?
[Update 2012-12-27: Correct URL for Amazon’s latest IP address list.]
Follow Eric Hammond on Twitter
For those lacking a calculator (what are you reading this on?) those numbers total up to 896,966. Let's just call that "nearly a million" public IP addresses reserved by Amazon for use with EC2 instances!
Except many people use VPC so they have a NAT and behind that NAT have many more computers and only one Elastic ip ;). We had 100 nodes running behind "one Elastic ip" early this week for some tests.
dean.hiller:
Yes, I mentioned VPC in the notes.
Well, the most important point is that a lot of people actually use load-balancers (both manually or configured by beans-talk or cloud-fromation) and you don't need IPs for each of the servers behind a load-balancer. In our cases the number of servers per IP is roughly 1:100 and keeps growing.
AItOawk1m3IK4oSEGrQPDwDV6iL5huIOzg9_LY0:
Your EC2 instances behind an EC2 ELB (Elastic Load Balancer) do use a public IP address even if they are not accessible through that public IP address because of security group rules.
In fact, you are using "number of instances plus one" public IP addresses because the load balancer itself is probably using an IP address in the EC2 space (anybody verified this?)