Amazon RDS is designed for developers or businesses who require the full features and capabilities of a relational database, or who wish to migrate existing applications and tools that utilize a relational database. It gives you access to the full capabilities of a MySQL 5.1 database running on your own Amazon RDS database instance.
To use Amazon RDS, you simply:
Simple to Deploy – Amazon RDS makes it easy to go from project conception to deployment. Use simple API calls to access the capabilities of a production-ready relational database without worrying about infrastructure provisioning or installing and maintaining database software.
Managed – Amazon RDS handles generic, time-consuming database management tasks, such as patch management and backup, which allows you to pursue higher value application development or database refinements.
Compatible – With Amazon RDS, you get full native access to a MySQL database. This means Amazon RDS works with your existing tools, applications, and drivers. You can port an existing database to Amazon RDS without changing a line of code – just point your tools or applications at your Amazon RDS DB Instance and you are ready to go.
Scalable – With a simple API call you can scale the compute and storage resources available to your database to meet your business needs and application load.
Reliable – Amazon RDS runs on the same highly reliable infrastructure used by other Amazon Web Services. AmazonRDS gives you additional peace of mind by enabling automated database backup. For typical workloads, this allows you to restore your DB Instance to any point in time during your retention period, up to the last five minutes. And, there is no additional charge for backup storage, up to 100% of your primary provisioned storage size.
Designed for use with other Amazon Web Services – Amazon RDS is tightly integrated with other Amazon Web Services. For example, an application running in Amazon EC2 will experience low-latency database access to an Amazon RDS DB Instance in the same region.
Secure – Amazon RDS provides web service interfaces to configure firewall settings that control network access to your database.
Inexpensive – You pay very low rates and only for the resources you actually consume. There are no long-term contracts or up-front commitments to use Amazon RDS.
Amazon RDS currently supports five DB Instance Classes:
For each DB Instance class, RDS provides you with the ability to select from 5GB to 1TB of associated storage capacity. One ECU provides the equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor.
Pay only for what you use. There is no minimum fee. Estimate your monthly bill using the AWS Simple Monthly Calculator.
On Demand Instance Pricing:
|DB Instance Class||Price Per Hour|
|Small DB Instance||$0.11|
|Large DB Instance||$0.44|
|Extra Large DB Instance||$0.88|
|Double Extra Large DB Instance||$1.55|
|Quadruple Extra Large DB Instance||$3.10|
For each DB Instance class, Amazon RDS provides you the ability to select from 5 GB to 1 TB of associated storage capacity for your primary data set.
Backup storage is the storage associated with your automated database backups and any user-initiated DB Snapshots you have taken. Increasing your backup retention period or taking additional database snapshots increases the backup storage consumed by your database.
Data transferred between two Amazon Web Services within the same region (e.g. between Amazon RDS US and AmazonEC2 US) is free of charge. Data transferred between AWS services in different regions will be charged as Internet Data Transfer on both sides of the transfer.
Data Transfer In
- All Data Transfer $0.10 per GB
Data Transfer Out
- First 10 TB per Month $0.17 per GB
- Next 40 TB per Month $0.13 per GB
- Next 100TB per Month $0.11 per GB
- Over 150 TB per Month $0.10 per GB
All pricing listed above is for DB Instances running in the US Region. We expect to make the service available in the EU Region in the coming months.
New Features for Amazon RDS Coming Soon
To help you better plan future hardware and software investments, Amazon RDS would like to share the following features that we plan to make available in the coming months:
- Reserved DB Instances — With Reserved DB Instances you pay a low, one-time fee and in turn receive a discount on the ongoing hourly usage charge for that DB Instance. Reserved DB Instances can provide substantial savings over owning your own hardware or even running only On-Demand DB Instances.
- High Availability Offering — For developers and business who want additional resilience beyond the automated backups provided by Amazon RDS at no additional charge. With the high availability offer, developers and business can easily and cost-effectively provision synchronously replicated DB Instances in multiple availability zones (AZ’s), to protect against failure within a single location.
For sure this is a very significant thing; providing a MySQL database AND backup support is definitely another giant step in the right direction -- and great news for Cloud developers.
>> "This may well prove to be the cloud news of the week"
Monitor the compute and storage resource utilization of your DB Instance, for no additional charge, via Amazon CloudWatch. If at any point you need additional capacity, you can scale the compute and storage resources associated with your DB Instance with a simple API call.
Amazon CloudWatch is a web service that provides monitoring for AWS cloud resources, starting with Amazon EC2. It provides customers with visibility into resource utilization, operational performance, and overall demand patterns—including metrics such as CPU utilization, disk reads and writes, and network traffic. To use Amazon CloudWatch, simply select the AmazonEC2 instances that you’d like to monitor; within minutes, Amazon CloudWatch will begin aggregating and storing monitoring data that can be accessed using the AWS Management Console, web service APIs or Command Line Tools.
Performance to disk may be improved, relative to running MySQL as an AMI.
And why is "doing it yourself" somehow better? Are restaurants and catering services for people who "are not smart enough to cook a meal for thmselves"? There are a lot more productive ways for a Cloud developer to spend their time than to show how "smart they are" by "doing it themselves". Persistence ought to be for the asking.
>> "for people not smart enough to figure out how to do it themselves"
Take the case of a multi-tier/multi-platform application. ie multiple
web servers, multiple application servers and a DB layer.
How would scalability work?
At the individual application component level (eg OS instance?
At the whole of application level (ie overall response time)?
Who provides the monitoring and feedback capability? The user or the
Or have I got this wrong?
Ok, how do you get away without having a dba? I don't see it.
You need someone to transfer the data, execute any additional programming, retrieve the results.. Then there is the master data issues... How does this happen without an admin ?
That it lacked true auto scaling at launch told me they were just trying to get it to market before full azure launch.
I'm utterly perplexed what you might be talking about. What real
scaling can you do w/ MySQL w/o resorting to partitioning, sharding or
other techniques that break the relational model?