ec2 pricing_and_capacity
-
$/mo,$/day,$/hr-- absolute prices by month, day, hour; I find it much easier to reason about always-on cluster decisions on a per-month basis. -
Mem/$,CPU/$-- relative cost of memory (in GB per dollar per hour) and CPU (in m1.small-equivalents per dollar per hour). -
mem-- GB of system RAM -
cpu-- total computer power in m1.small-equivalents (i.e. "5" means "roughly 5 times faster than an m1.small") -
cores-- separate cores; more is good if you're running highly parallel tasks; more is bad if your app has significant single-threaded sections -
cpcore-- CPU units per core -
storage-- on-disk ("ephemeral") storage, in GB -
disks-- number of separate volumes. Anm1.largehas 850 GB total, 2 volumes, so each is 425 GB large. -
ebs-opt-- whether the instance can be run in EBS-optimized mode (a kind of separate fast-track network channel specifically for EBS mounted volumes) -
IO-- Amazon's own description of the machine's IO. Don't take the difference between "Med" and "Hi" too seriously (ie. run your own tests) -- for some usages, the two backplanes of two m1.larges (each with "med" IO) will beat the equivalent cost of one c1.xlarge
code $/mo $/day $/hr Mem/$ CPU/$ mem cpu cores cpcore storage disks ebs-opt IO
t1.micro 15 0.48 .02 31 13 .61 0.25 1 .25 - 0 Lo
m1.small 44 1.44 .06 28 17 1.7 1 1 1 160 1 Med
m1.medium 88 2.88 .12 31 17 3.75 2 2 1 410 1 Med
c1.medium 106 3.48 .15 12 34 1.7 5 2 2.5 350 1 Med
m1.large 175 5.76 .24 31 17 7.5 4 2 2 850 2 Med
m1.large +ebs 194 6.36 .27 28 15 7.5 4 2 2 850 2 500 Med+EBS
m2.xlarge 300 9.84 .41 42 16 17.1 6.5 2 3.25 420 1 Med
m1.xlarge 351 11.52 .48 31 17 15. 8 4 2 1690 4 Hi
m3.xlarge 365 12.00 .50 30 26 15. 13 4 3.25 - 0 Med
m3.xlarge +ebs .53 15. 13 4 3.25 - 0 500 Med+EBS
m1.xlarge +ebs 387 12.72 .53 28 15 15. 8 4 2 1690 4 1000 Hi+EBS
c1.xlarge 424 13.92 .58 12 34 7. 20 8 2.5 1690 4 Hi
c1.xlarge +ebs .63 7. 20 8 2.5 1690 4 1000 Hi+EBS
m2.2xlarge 599 19.68 .82 42 16 34.2 13 4 3.25 850 2 Hi
m2.2xlarge +ebs .85 34.2 13 4 3.25 850 2 1000 Hi+EBS
m3.2xlarge 731 24.00 1.00 30 26 30. 26 8 3.25 - 0 Hi
m3.2xlarge +ebs 1.05 30. 26 8 3.25 - 0 1000 Hi+EBS
cc1.4xlarge 950 31.20 1.30 18 26 23. 33.5 8 4.2 1690 4 10gb
m2.4xlarge 1198 39.36 1.64 42 16 68.4 26 8 3.25 1690 2 Hi
m2.4xlarge +ebs 1235 40.56 1.69 40 15 68.4 26 8 3.25 1690 2 1000 Hi+EBS
cg1.4xlarge 1534 50.40 2.10 10 16 22. 33.5 8 4.2 1690 4 10gb
cc2.8xlarge 1753 57.60 2.40 25 37 60.5 88 16 5.5 3370 2 10gb
hi1.4xlarge 2265 74.40 3.10 20 11 60.5 35.2 16 2.2 2048 ssd 2 10gb
cr1.8xlarge 2557 84.00 3.50 70 25 244. 88 16 5.5 240 ssd 2 10gb
hs1.8xlarge 3361 110.40 4.60 25 8 117. 35 16 2.2 49152 24 10gb
Prices are for standard (non-reserved) instances. EBS-optimized instances are listed on their own line.
You may also enjoy the spreadsheet version of this (in OSX Numbers format, sorry)
$/GB..mo $/GB.mo $/Mio
EBS Volume $0.10
EBS I/O $0.10
EBS Snapshot S3 $0.083
Std $/GB.mo Red.Red. $/GB.mo
S3 1st tb $0.125 $0.093
S3 next 49tb $0.110 $0.083
S3 next 450tb $0.095 $0.073
(Cost of storage, neglecting I/O costs, and assuming the ratio of EBS volume size to snapshot size is as given)
The costs of EBS will be similar to the pricing structure of data storage on S3. There are three types of costs associated with EBS.
Storage Cost + Transaction Cost + S3 Snapshot Cost = Total Cost of EBS
NOTE: For current pricing information, be sure to check Amazon EC2 Pricing.
The cost of an EBS Volume is $0.10/GB per month. You are responsible for paying for the amount of disk space that you reserve, not for the amount of the disk space that you actually use. If you reserve a 1TB volume, but only use 1GB, you will be paying for 1TB.
- $0.10/GB per month of provisioned storage
- $0.10/GB per 1 million I/O requests
In addition to the storage cost for EBS Volumes, you will also be charged for I/O transactions. The cost is $0.10 per million I/O transactions, where one transaction is equivalent to one read or write. This number may be smaller than the actual number of transactions performed by your application because of the Linux cache for all file systems. $0.10 per 1 million I/O requests
Snapshot costs are compressed and based on altered blocks from the previous snapshot backup. Files that have altered blocks on the disk and then been deleted will add cost to the Snapshots for example. Remember, snapshots are at the data block level. $0.15 per GB-month of data stored $0.01 per 1,000 PUT requests (when saving a snapshot) $0.01 per 10,000 GET requests (when loading a snapshot)
NOTE: Payment charges stop the moment you delete a volume. If you delete a volume and the status appears as "deleting" for an extended period of time, you will not be charged for the time needed to complete the deletion.