new r3 instances are available.

http://aws.typepad.com/aws/2014/04/now-available-new-memory-optimized-ec2-instances.html

Model vCPU Mem (GiB) SSD Storage (GB)
r3.large 2 15 1 x 32
r3.xlarge 4 30.5 1 x 80
r3.2xlarge 8 61 1 x 160
r3.4xlarge 16 122 1 x 320
r3.8xlarge 32 244 2 x 320

Memory Optimized - Current Generation
r3.large 2 6.5 15 1 x 32 SSD $0.175 per Hour
r3.xlarge 4 13 30.5 1 x 80 SSD $0.350 per Hour
r3.2xlarge 8 26 61 1 x 160 SSD $0.700 per Hour
r3.4xlarge 16 52 122 1 x 320 SSD $1.400 per Hour
r3.8xlarge 32 104 244 2 x 320 SSD $2.800 per Hour

m1.small 1 1 1.7 1 x 160 $0.044 per Hour
m1.medium 1 2 3.75 1 x 410 $0.087 per Hour
m1.large 2 4 7.5 2 x 420 $0.175 per Hour
m1.xlarge 4 8 15 4 x 420 $0.350 per Hour

Not sure where this is being pulled from, but currently the site reports m3.xlarge instances as having 1000 Mbps of EBS optimized bandwidth but according to http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html , it only has 500.

c1.medium 2 5 1.7 1 x 350 $0.130 per Hour
c1.xlarge 8 20 7 4 x 420 $0.520 per Hour

Add the ability to choose between EBS Optimized pricing and regular

Cool looking project. Could you add an explicit license? I can submit a pull request if that'd help. I have a mild preference for MIT or BSD licenses. Thanks.

Documented for reference. http://aws.typepad.com/aws/2013/11/a-generation-of-ec2-instances-for-compute-intensive-workloads.html

Another column (or two) that divides the the cost by the number of compute units and amount of RAM.

See http://aws.amazon.com/windows/

Picking an AMI with SQL Server can run up to 5x as expensive (if you have a Small instance). I made the mistake of picking the wrong AMI, and would love to help others avoid it.

There is a jquery loading error.
TypeError: jQuery.fn.dataTableExt is undefined
http://www.ec2instances.info/default.js
Line 189

TypeError: $.fn.dataTableExt is undefined
http://www.ec2instances.info/default.js
Line 165

only showing us east region currently.

Excerpt from
https://aws.amazon.com/ec2/pricing/

m3.xlarge 4 13 15 2 x 40 SSD $0.450 per Hour
m3.2xlarge 8 26 30 2 x 80 SSD $0.900 per Hour

The page says that m1.large has High / 500Mbps I/O performance but Amazon's own instance type page says that it's Moderate.

What evidence is used to justify the High designation? Or is it mislabeled?

I can see different price
if I change Costs-> Yearly and back to Hourly.

Error reproduction:

"Step1"
load : http://www.ec2instances.info/
( default: Costs: Hourly)
hi1.4xlarge Linux:$3.10 per hour

"Step2"
change: Costs-> Yearly

"Step3"
change back: Costs-> Hourly

now: hi1.4xlarge Linux:$2.10 per hour
and it is not a real price.

Out of frustration, I had to ask this publicly at http://www.quora.com/How-many-number-of-application-users-can-a-1-ECU-or-VCPU-of-1-7GB-RAM-comfortably-serve

Can get it here: http://aws.amazon.com/ec2/pricing/pricing-on-demand-instances.json

m2.xlarge 2 6.5 17.1 1 x 420 $0.245 per Hour
m2.2xlarge 4 13 34.2 1 x 850 $0.490 per Hour
m2.4xlarge 8 26 68.4 2 x 840 $0.980 per Hour
cr1.8xlarge 32 88 244 2 x 120 SSD $3.500 per Hour

It was added in October: http://aws.amazon.com/about-aws/whats-new/2014/10/23/announcing-the-aws-eu-frankfurt-region/

Show a list of currencies as a dropdown, that changes the prices column similar to the Costs dropdown.

There's a few api's around for currency conversion, including sending a request to:

http://www.google.com/ig/calculator?hl=en&q=1usd+in+gbp

...and parsing the json that is returned.

You'd want to show a warning that currencies are approximate.

Similar to the existing I/O performance column.

m3.medium 1 3 3.75 1 x 4 SSD $0.070 per Hour
m3.large 2 6.5 7.5 1 x 32 SSD $0.140 per Hour
m3.xlarge 4 13 15 2 x 40 SSD $0.280 per Hour
m3.2xlarge 8 26 30 2 x 80 SSD $0.560 per Hour

M4 instances were just announced.

$ fab build
Parsing instance types...
ERROR: Unable to scrape site data: Expected 12 columns in the table, but got 4
Loading data from www/instances.json...
Rendering to www/index.html...

Done.

new m3 instances are available. all m3 instances can be instance store-backed backed.

http://aws.typepad.com/aws/2014/01/aws-update-new-m3-features-reduced-ebs-prices-reduced-s3-prices.html

http://aws.amazon.com/ec2/instance-types/

Instance Family
Instance Type Processor Arch vCPU ECU Memory (GiB) Instance Storage (GB) EBS-optimized Available Network Performance
General purpose m3.medium 64-bit 1 3 3.75 1 x 4 SSD_6 - Moderate
General purpose m3.large 64-bit 2 6.5 7.5 1 x 32 SSD_6 - Moderate
General purpose m3.xlarge 64-bit 4 13 15 2 x 40 SSD_6 Yes Moderate
General purpose m3.2xlarge 64-bit 8 26 30 2 x 80 SSD_6 Yes High

Instance Family Instance Type Processor Arch vCPU ECU Physical Processor Intel® AES-NI Intel® AVX† Intel® Turbo
General purpose m3.medium 64-bit 1 3 Intel Xeon E5-2670 Yes Yes Yes
General purpose m3.large 64-bit 2 6.5 Intel Xeon E5-2670 Yes Yes Yes
General purpose m3.xlarge 64-bit 4 13 Intel Xeon E5-2670 Yes Yes Yes
General purpose m3.2xlarge 64-bit 8 26 Intel Xeon E5-2670 Yes Yes Yes

http://aws.amazon.com/ec2/pricing/

Region:
vCPU ECU Memory (GiB) Instance Storage (GB) Linux/UNIX Usage
General Purpose - Current Generation
m3.medium 1 3 3.75 1 x 4 SSD $0.113 per Hour
m3.large 2 6.5 7.5 1 x 32 SSD $0.225 per Hour
m3.xlarge 4 13 15 2 x 40 SSD $0.450 per Hour
m3.2xlarge 8 26 30 2 x 80 SSD $0.900 per Hour

We need a new column to distinguish between "VPC only" vs. "EC2 Classic & VPC"

Regarding the new instance types M4 and C4, they can only be spun up in a VPC. Note this is also true for T2 as well.

Instance Types Available Only in a VPC
Instances of the following instance types are not supported in EC2-Classic and must be launched in a VPC:

• C4
• M4
• T2

Additionally they appear to be 64 bit HVM only too:

The instances support 64-bit HVM AMIs launched within a VPC.

AWS lists these instance types as having 2x as many vCPU as is listed on the site (probably due to hyper-threading?)

http://aws.amazon.com/ec2/previous-generation/

This then in turn leads to inflated ECU per core as compared to the newer instances like c3 and c4s.

From http://aws.typepad.com/aws/2013/11/build-3d-streaming-applications-with-ec2s-new-g2-instance-type.html

NVIDIA GRID™ (GK104 "Kepler") GPU (Graphics Processing Unit), 1,536 CUDA cores and 4 GB of video (frame buffer) RAM.
Intel Sandy Bridge processor running at 2.6 GHz with Turbo Boost enabled, 8 vCPUs (Virtual CPUs).
15 GiB of RAM.
60 GB of SSD storage.

HVM virt type
26 ECUs
0.65/hour linux
0.767/hour windows

5% price drop for some instance types.

https://aws.amazon.com/blogs/aws/the-new-m4-instance-type-bonus-price-reduction-on-m3-c4/
http://aws.amazon.com/ec2/pricing/

eg, m3.medium was $0.070/hour and is now $0.067/hour

c3.large 2 7 3.75 2 x 16 SSD $0.105 per Hour
c3.xlarge 4 14 7.5 2 x 40 SSD $0.210 per Hour
c3.2xlarge 8 28 15 2 x 80 SSD $0.420 per Hour
c3.4xlarge 16 55 30 2 x 160 SSD $0.840 per Hour
c3.8xlarge 32 108 60 2 x 320 SSD $1.680 per Hour

The new D2 instances are not included yet.

In #37 a tool was introduced to update the contents of this site automatically by scraping the AWS site. Unfortunately Amazon's latest site design and is no longer providing all the necessary info.

Specifically:

• of cores and compute units

• of drives & their size

• Architecture

The instance types page used to contain a nice table of all the instance types and their basic stats, but now only has a few less-descriptive tables for the newer instance types. The previous generation instance types page has some of this info, but not everything.

I'm still looking for a place to get this data. Unfortunately they don't have an API exposing it.

Would it be possible to split the "compute units" column, which currently contains strings like 7 (2 core x 3.5 unit) into three columns

• Compute Units
• Num Cores
• Units/core

This would make it easier to select instance types for more- or less- parallelizable workloads.

hvm column This seems very important! You can not resize instances arbitrarily. hvm only runs on hvm, paravirtual on paravirtual. there is some overlap, yes, but not entirely. I am hitting this problem a lot lately, in that I can not re-size instances. a cc2.8xlarge can not become a small, and vice versa.

When I visit the page, turn off some columns, and come back I notice two things.

First, the table remembers to hide the columns (which is good).

Second, the column selector now shows all columns as blue, meaning active (which is bad). In other words, the column selector does not remember its state the way the table does.

http://aws.typepad.com/aws/2012/10/new-ec2-second-generation-standard-instances-and-price-reductions-1.html

https://twitter.com/thelenshar/status/276229798492250112

http://help.hipchat.com/knowledgebase/articles/112160-hipchat-crashes-after-updating-air-or-sharing-an-a

Basically, cat /proc/cpuinfo on each instance type and include the data.

There is a new scale of prices and new configurations → http://aws.amazon.com/ec2/#pricing

related:

http://aws.typepad.com/aws/2012/03/ec2-updates-new-instance-64-bit-bit-ubiquity-ssh-client.html
http://aws.typepad.com/aws/2012/03/dropping-prices-again-ec2-rds-emr-and-elasticache.html

Excerpt from
https://aws.amazon.com/ec2/instance-types/

Compute optimized c3.large 64-bit 2 7 3.75 2 x 16 SSD - Moderate
Compute optimized c3.xlarge 64-bit 4 14 7.5 2 x 40 SSD Yes Moderate
Compute optimized c3.2xlarge 64-bit 8 28 15 2 x 80 SSD Yes High
Compute optimized c3.4xlarge 64-bit 16 55 30 2 x 160 SSD Yes High
Compute optimized c3.8xlarge 64-bit 32 108 60 2 x 320 SSD - 10 Gigabit4

Hi,

The M3 instances networking infomation has been updated on the AWS site. Can anyone update this site? I use this frequently but I am not familiar enough with this site to make the changes.

http://aws.amazon.com/ec2/instance-types/

Info from this page in some form would be very useful to include:

http://aws.amazon.com/amazon-linux-ami/instance-type-matrix/

With the announcement of the new c4 instance types, (http://aws.amazon.com/ec2/instance-types/?sc_ichannel=em&sc_icountry=global&sc_icampaigntype=launch&sc_icampaign=em_130722160&sc_idetail=em_2057599741&ref_=pe_411040_130722160_17#compute-optimized), we should be including c4 instance types in the table.

The filter button is pretty broken on my Firefox (Iceweasel 1.0.12).

Would be great to have the same site for RDS.
Do you have any plans?

Documented for reference. http://aws.typepad.com/aws/2013/11/coming-soon-the-i2-instance-type-high-io-performance-via-ssd.html

It would be more appropriate to call the "Core" column either "vCPU" or "hyperthread" or add a tooltip with explanation. Viz each vCPU is a hyperthread of an Intel Xeon core for M3, C4, C3, R3, HS1, G2, I2, and D2.

The default sort by "Name" isn't particularly useful. Usually I want to sort by "beefiness" so I habitually click on "Linux cost" every time I open the page. Maybe this would be a better default sort? (It only differs from "Windows cost" by one transposition.)

Id like to see how on demand instances compare to reserved instances in terms of price but your site only seems to mention the on demand instance pricing. This would require a couple extra columns for the upfront and hourly prices. A user should be able to do price calculations based on how often their instances are running on average (percentage over time period). The data feed of prices is available from amazon here

http://aws.amazon.com/ec2/pricing/ri-light-linux.json
http://aws.amazon.com/ec2/pricing/ri-light-mswin.json
http://aws.amazon.com/ec2/pricing/ri-medium-linux.json
http://aws.amazon.com/ec2/pricing/ri-medium-mswin.json
http://aws.amazon.com/ec2/pricing/ri-heavy-linux.json
http://aws.amazon.com/ec2/pricing/ri-heavy-mswin.json

The two "enterprise Linux" offerings seem to have different pricing from "normal" Linux (and from each other). For the sake of completeness, would it make sense to add columns for this, was done for the "Windows SQL" types?