Launching a MySQL DB Instance

To launch a MySQL DB Instance

Once you have selected MySQL as your DB Engine, the wizard displays the DB Instance Details page for MySQL. The most important parameters you set here are for the DB Instance Class in the DB Instance Class drop-down list and the Allocated Storage text box. The DB Instance class defines the CPU and memory capacity of your DB Instance, which can impact processing speed and responsiveness. The allocated storage value determines how much storage is allocated for this DB Instance. Note that these two values are used to calculate the cost of your DB Instance.

1. On the DB Instance Details page, specify your DB Instance information as shown in the following table, then click Continue.

   For this parameter...	...Do this:
   License Model	Select the default, General-Public-License, to use the general license agreement for MySQL.
   DB Engine Version	Select 5.5.20 to use the default version of MySQL. Note that RDS supports additional versions of MySQL.
   DB Instance Class	Select db.m1.small to select a configuration that equates to 1.7 GB memory, 1 ECU (1 virtual core with 1 ECU), 64-bit platform, and moderate I/O capacity. for more information about the capacity for all the DB Instance class options, see Amazon Relational Database Service Features.
   Multi-AZ Deployment	Select No to not request that your database be made available in multiple availability zones. For more information about multiple availability zones, see the RDS documentation.
   Auto Minor Version Upgrade	Select Yes to enable your DB Instance to receive minor DB Engine version upgrades automatically when they become available.
   Allocated Storage	Type 5 to allocate 5 GB of storage for your database. In some cases, allocating a higher amount of storage for your DB Instance than the size of your database can improve I/O performance. For more information about storage allocation, see Amazon Relational Database Service Features.
   Use Provisioned IOPS	Leave the check box unselected. This option turns on Provisioned IOPS (I/O operations per second), a high-performance storage option in RDS that is optimized for I/O-intensive, transactional (OLTP) database workloads. For more information about high performance storage, see Provisioned IOPS.
   DB Instance Identifier	Type a name for the DB Instance that is unique for your account in the region you selected. You may chose to add some intelligence to the name such as including the region and DB Engine you selected, for example west2-mysql-instance1.
   Master User Name	Type a name using alphanumeric characters that you will use as the master user name to log on to your DB Instance with all database privileges.
   Master User Password	Type a password that contains from 8 to 16 printable ASCII characters (excluding /,", and @) for your master user password.

2. On the Additional Configuration page, you provide additional information that RDS needs to launch the DB Instance for MySQL. Specify your DB Instance information as shown in the following table, then click Continue.

   

   For this parameter...	...Do this:
   Database Name	Type a name for your database of up to 8 alpha-numeric characters. If you do not provide a name, Amazon RDS will not create a database on the DB Instance you are creating.
   Database Port	Leave the default value of 3306 unless you have a specific port you want to access the database through. MySQL installations default to port 3306.
   Choose a VPC	Leave the default value of Not in VPC unless you are creating this DB Instance in a Virtual Private Cloud with a DB Subnet Group.
   Availability Zone	Leave the default of No Preference unless you want to specify a particular Availability Zone. If you selected Yes for the Multi-AZ Deployment parameter on the previous page, you will not have any options here.
   Option Group	Select the default value of default:mysql-5-5 since this option group is used with the MySQL version you selected on the previous page, in this case version 5.5.20.
   DB Parameter Group	Leave the default value of default.mysql5.5 unless you created your own DB Parameter group.
   DB Security Groups	Select the security group that you created in the Authorize Access step of this guide.

3. On the Management Options page, you can specify backup and maintenance options for your DB Instance. For this example, accept the default values, and then click Continue. Note that setting the Backup Retention Period to zero disables automatic backups.

   

   In addition, Federated Storage Engine is currently not supported by Amazon RDS for MySQL.

   Note

   The Point-In-Time-Restore and Snapshot Restore features of Amazon RDS for MySQL require a crash recoverable storage engine and are supported for the InnoDB storage engine only. While MySQL supports multiple storage engines with varying capabilities, not all of them are optimized for crash recovery and data durability. For example, the MyISAM storage engine does not support reliable crash recovery and may result in lost or corrupt data when MySQL is restarted after a crash, preventing Point-In-Time-Restore or Snapshot restore from working as intended.

   If you would like to convert existing MyISAM tables to InnoDB tables, you can use the alter table command (e.g., alter table TABLE_NAME engine=innodb;). Note that MyISAM and InnoDB have different strengths and weaknesses, so you should fully evaluate the impact of making this switch on your applications before doing so.

4. On the Review page, review the options for your DB Instance:

   If you need to correct any options, click Back to return to previous pages and make corrections. You can also modify a DB Instance from the AWS Console after you have launched a DB Instance.

   If all your options are entered correctly, click the Launch DB Instance button to launch your new DB Instance.

   

5. On the dialog box that indicates that your DB Instance is being created, click the Close button.

   

6. On the AWS Management Console, the new DB Instance appears in the list of DB Instances. The DB Instance will have a status of creating until the DB Instance is created and ready for use. Depending on the DB Instance class and store allocated, it could take several minutes for the new instance to be created.

   

   Once your DB instance changes to the available state, you can connect to it.