StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8676062
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2011-12-30T04:06:08.777
FavoriteCount
0
LastActivityDate
2018-02-07T11:33:02.220
LastEditDate
2018-02-07T11:33:02.220
LastEditorUserId
868947
OwnerUserId
1074655
ParentId
3636578
PostTypeId
2
Score
37
ViewCount
0
LastEditorDisplayName
text
Body
UPDATE: AWS has pricing API nowadays: <a href="https://aws.amazon.com/blogs/aws/new-aws-price-list-api/" rel="nofollow noreferrer">https://aws.amazon.com/blogs/aws/new-aws-price-list-api/</a> Original answer: This is something I have asked for (via AWS evangelists and surveys) previously, but hasn't been forthcoming. I guess the AWS folks have more interesting innovations on their horizon. As pointed out by @brokenbeatnik, there is an API for spot-price history. API docs here: <a href="http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeSpotPriceHistory.html" rel="nofollow noreferrer">http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeSpotPriceHistory.html</a> I find it odd that the spot-price history has an official API, but that they didn't do this for on-demand services at the same time. Anyway, to answer the question, yes you can query the advertised AWS pricing... The best I can come up with is from examining the (client-side) source of the various services' pricing pages. Therein you'll find that the tables are built in JS and populated with JSON data, data that you can GET yourself. E.g.: <ul> <li><a href="http://aws.amazon.com/ec2/pricing/pricing-on-demand-instances.json" rel="nofollow noreferrer">http://aws.amazon.com/ec2/pricing/pricing-on-demand-instances.json</a></li> <li><a href="http://aws.amazon.com/s3/pricing/pricing-storage.json" rel="nofollow noreferrer">http://aws.amazon.com/s3/pricing/pricing-storage.json</a></li> </ul> That's only half the battle though, next you have to pick apart the object format to get at the values you want, e.g., in Python this gets the Hi-CPU On-Demand Extra-Large Linux Instance pricing for Virginia: <pre><code>>>> import json >>> import urllib2 >>> response = urllib2.urlopen('http://aws.amazon.com/ec2/pricing/pricing-on-demand-instances.json') >>> pricejson = response.read() >>> pricing = json.loads(pricejson) >>> pricing['config']['regions'][0]['instanceTypes'][3]['sizes'][1]['valueColumns'][0]['prices']['USD'] u'0.68' </code></pre> Disclaimer: Obviously this is not an AWS sanctioned API and as such I wouldn't recommend expecting stability of the data format or even continued existence of the source. But it's there, and it beats transcribing the pricing data into static config/source files!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAre there any API's for Amazon Web Services PRICING?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJimilian
UserOwnerUserId
1. USBlairo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COIt's also worth noting a caveat with reading spot price history from the API - it will only show changes between your start+end time. Some instance types aren't supported in certain availability zones (and detecting this is quite hard since if you ask for the last 24 hours of spot price data an unchanged price would look like an unsupported instance type in that region (or vice versa)
 singulars
 PostPostId
 PO
 UserUserId
 USPeter

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.