6:08pm I need to create more pricing structures as I didn’t code region support for S3 and
SimpleDb.SDB regions:
- US-East (Northern Virginia) Region,
- US-West (Northern California) Region,
- EU (Ireland)
RegionSDB metrics:
- Machine Utilization (BoxUsage)
- Data Transfer In (DataTransfer-In-Bytes)
- Date Transfer Out (DataTransfer-Out-Bytes)
- Structured Data Storage (TimedStorage-ByteHrs)
I only started instance in the US-West region, so to get the proper usage type code I need to start one instance on the east code and one in Ireland. I assume the Box Usage codes should be USW1-BoxUsage and EU-BoxUsage. Now I cannot just assume, if only amazon had this documented, that would save me numerous hours digging around. Hey, I’m sure I’ll get the complete list from somewhere as soon I’m done reverse engineering all that.
So I’ve create two new SimpleDB databases, one in each region I didn’t try yet. Let’s see when do start showing up in the usage log. Actually it seemed instant. I just reloaded the logs in my tool and saw the European usage:
And the West coast usage:
So that’s gonna be pretty easy to configure. This said that makes me want to program the region aggregation right away. Now I just need to know when they added the regions to ensure proper price calculation for historical periods. Note that the TimedStorage-ByteHrs didn’t appear yet, so I assume I need to wait one hour for this usage to appear.
In the mean time let’s create some S3 buckets across the planet. For S3 they are also 3 regions: US Standard Region, US-West (Northern California) Region, EU (Ireland) Region. Now I assume that the US Standard Region is the US-East (Northern Virginia) as in Sdb. I’m using Transmit but it supports only two regions North America (Default) and Europe. So I created a European one and copied a few files. From the api I must use the s3-us-west-1.amazonaws.com end point for reach the US-West Region.
Note from the API doc “The US Standard Region provides eventual consistency for all requests. The EU (Ireland) and Northern California Regions provide read-after-write consistency for PUTS of new objects and eventual consistency for overwrite PUTS and DELETES.” I now create a us-west-1 bucket and added the same file than I did to the European bucket.
The European bucket already showed up in the usage files:
So there seems to be some consistency and the usage codes start with “EU-“, so hopefully the US West ones will start with “USW1-“. Now I need to figure out the Requests-Tier1. Thanks to google I figured these out:
- Requests-Tier1 is for PUT , COPY, POST , or LIST requests
- Requests-Tier2 is for GET and all other requests (except DELETE)
- Requests-NoCharge is for DELETE requests
All right, the US West bucket operations started to show up:
7:49pm I was expecting TimedStorage-ByteHrs to appear for SimpleDb, but they didn’t. So I’ll check them later as this needs to be coded into the price calculation.
There are only a few more details to code (and lots’ to test) before I can call the price structure complete. But that was one of the major aspects of this application. Yea.
On a side note I spoke with Juan Sanchez to see if he can spice up this application a little. He sounded interested so we need to flesh out the details of our collaboration but that would be awesome. He also didn’t seem to like the name of the app, AwsUsageAnalyzr, which I totally agree and came up with a cool new name. So we will use the new name for the first test release, so stay tuned…more in a few weeks.
8:26pm Me fried! I guess getting up at 5am to work out, it’s to good for my late night coding! That’s it for today, a great day as the todo list (for the beta) is really getting shorter. I hope the Adobe guys move faster with they payment solution otherwise I will need to spend time to use an alternate solution, which may not be a bad idea based that the other payment solution seem to charge less. But you can beat adding payment processing support with one line of code. So what’s left on the todo? Mainly the usage and pricing graph may have to be selected based on context as in some context one or the other doesn’t apply. Also the graph is not very readable so I may need to aggregate the values further just for the graph or see if I should use a different graph style all together. Other than a few navigation shortcuts would be welcome and maybe improving the login into the amazon website…If it would be for Adobe I would start an alpha version today just for the adventurous!
Enjoy!
Daniel.
