Release: Amazon Relational Database Service

Release Notes>Amazon RDS>Release: Amazon Relational Database Service
This is the initial release of the Amazon Relational Database Service.


Submitted By: GeorgeNickels@AWS
Release Date: October 22, 2009 12:00 AM GMT
Latest Version: 2009-10-16
Latest WSDL:
Created On: October 27, 2009 1:43 AM GMT
Last Updated: December 29, 2009 1:28 AM GMT

These release notes provide a summary of all New Features, Resolved Issues, and Known Issues in this version of the Amazon Relational Database Service.

New Features

Feature Description

New service, new documentation

This is the first release of the Amazon Relational Database Service (Amazon RDS). This web service makes it easier to set up, operate, and scale a relational database in the cloud.

Amazon RDS gives you access to many of the capabilities of a familiar MySQL database server. This means the code, applications, and tools you already use today with your existing MySQL databases work with Amazon RDS with little or no modification. Amazon RDS automatically backs up your database and maintains the database software that powers your DB Instance. With Amazon RDS, you can scale your database instance’s compute resources and storage capacity to meet your application’s demand. As with all Amazon Web Services, there are no up-front investments and you pay only for the resources you use.

Amazon RDS provides cost-efficient and resizable capacity for an industry-standard relational database. The service manages common database administration tasks, freeing up developers to focus on what makes their applications and businesses unique.

Known Issues

InnoDB engine support only Amazon RDS automated backups and DB Snapshots are currently supported for the InnoDB engine only. Use of these features with other MySQL engines, including MyISAM, may lead to unreliable behavior while restoring from backups. Specifically, since storage engines like MyISAM do not support reliable crash recovery, your tables can be corrupted in the event of a crash. For this reason, we encourage you to use the InnoDB storage engine. If you choose to use MyISAM, you can attempt to manually repair tables that become damaged after a crash using the REPAIR command ((see: However, as noted in the MySQL documentation, there is a good chance that you will not be able to recover all your data. If you wish to take DB snapshots with MyISAM tables, follow these steps:
(i) Stop all activity to your MyISAM tables (i.e., close all sessions),
(ii) lock and flush each of your MyISAM tables, and then (iii) issue a CreateDBSnapshot API call or use the RDSCLI rds-create-db-snapshot command. When the snapshot has completed, release the locks and resume activity on the MyISAM tables. These steps force MyISAM to flush data stored in memory to disk thereby ensuring a clean start when you restore from a DB snapshot. Finally, if you would like to convert existing MyISAM tables to InnoDB tables, you can use alter table command (e.g., alter table engine=innodb;).
To find out the list of MyISAM tables owned by you, you can run the following query:
"select table_schema, table_name from information_schema.tables where engine='MyISAM' and table_schema not in ('mysql','information_schema');
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.