Amazon Drops Prices On Multiple Zone Database Service
By Charles Babcock
InformationWeek
Amazon pricing is specific to region, such as U.S. East or U.S. West, so the reduction amount will depend on where the Multi-AZ deployment occurs. A small server running a multi-zone instance of MySQL or Oracle in U.S. East has been reduced 15% from $0.18 to $0.153 per hour; the same pricing holds true for U.S. West (Oregon). In U.S. West (Northern California), however, the reduction was from $0.23 to $0.187. Data centers are cheaper to operate in Oregon, close to inexpensive hydropower and cool, dry air.
The steepest reduction, 32%, applied to Amazon Web Services' newest region, Sao Paulo, Brazil, where prices dropped from $0.30 to $0.204.
[ Want more on how cloud competitors have cut prices? See Microsoft Answers Amazon With Azure Cloud Price Cuts. ]
In the Dublin, Ireland, Amazon facility, pricing fell 27%, from $0.23 to $0.167. Three centers in Asia Pacific -- Singapore, Tokyo and Sydney -- all saw reductions of 15%; in Tokyo's case, from $0.24 to $0.204.
Any database instance activated under AWS's relational database service automatically gets a live backup copy, with failover automated between the two. Such an architecture protects against the failure of a disk containing data the database needs or failure of the database system itself.
But with the Multi-AZ option, the backup will be created in a different availability zone from the primary copy. In Amazon lingo, an availability zone is roughly an independent data center, or section of a data center complex, with its own supply of communications and power. If one availability zone loses power, others at the same location should not be affected. For instance, Amazon offers five zones in its most popular facility, U.S. East.
As usual in the case of price reductions, the announcement came in a blog by Jeff Barr, AWS chief evangelist, on Feb. 13. They were retroactive to Feb. 1. "We are making the Multi-AZ deployment model an even better value, with price reductions ranging from 15% to 32%," he wrote.
Amazon has repeatedly urged customers to make use of different availability zones if they want to ensure that their databases and other workloads continue to run in the event of an outage. But in most instances, the second copy has resulted in a second server charge, running up the user's routine costs and redeemed only in the unlikely event of an outage.
The price reductions announced for Multi-AZ RDS instances will give customers a big incentive to adopt a second zone in database operations. They represent an overdue modification to AWS pricing, if Amazon wants to more broadly encourage the adoption of multiple availability zone ops.
Attend Interop Las Vegas May 6-10, and attend the most thorough training on Apple deployment at the NEW Mac & iOS IT Conference. Join us in Las Vegas for access to 125+ workshops and conference classes, 350+ exhibiting companies, and the latest technology. Use Priority Code TLIWEEK by March 2 to save an extra $100 off the early bird price of Conference Passes. Register for Interop today!
Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).
 |
To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Subscribe to RSS
InformationWeek Reports
Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.
Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.
Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.
The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.
