In this tutorial, you will learn how to create an environment to run your MySQL database (we call this environment an 'instance'), connect to the database, and delete the DB instance. We will do this using Amazon Relational Database Service (Amazon RDS) in this tutorial.
When you click here, the AWS management console will open in a new browser window, so you can keep this step-by-step guide open. When this screen loads, find Amazon RDS under Database and click to open the Amazon RDS Console.
In this step, we will use Amazon RDS to create a MySQL DB Instance with db.t2.micro DB instance class, 5 GB of storage, and automated backups enabled with a retention period of one day.
a. In the top right corner of the Amazon RDS console, select the Region in which you want to create the DB instance.
Note: Amazon cloud computing resources are housed in highly available data center facilities in different areas of the world. Each Region contains multiple distinct locations called 'Availability Zones,' or AZs. You have the ability to choose which Region to host your Amazon RDS activity in.
b. In the navigation pane on the left, click Instances. Then click Launch DB Instance.
c. You now have options to select your engine. For this tutorial, click the MySQL icon and then click Select.
d. The next screen gives you options to choose your environment. Select the MySQL option under Dev/Test and click Next Step.
e. You will now configure your DB instance. The list below shows the example settings you can use for this tutorial:
- License Model: Select the default general-public-license to use the general license agreement for MySQL. MySQL has only one license model.
- DB Engine Version: Select the default version of MySQL. Note that Amazon RDS supports multiple versions of MySQL in some Regions.
- DB Instance Class: Select db.t2.micro --- 1vCPU, 1 GIB RAM. This equates to 1 GB memory and 1 vCPU. To see a list of supported instance classes, see Amazon RDS Product Details.
- Multi-AZ Deployment: Select No to create your DB instance in a single Availability Zone for this tutorial. Using a Multi-AZ Deployment will automatically provision and maintain a synchronous standby replica in a different Availability Zone. Note that you will have to pay for Multi-AZ Deployment. For more information, see High Availability Deployment.
- Storage Type: Select General Purpose (SSD). For more information about storage, see Storage for Amazon RDS.
- Allocated Storage: Type 5 to allocate 5 GB of storage for your database. You can scale up to a maximum of 6 TB with Amazon RDS for MySQL.
- DB Instance Modifier: Type a name for the DB instance that is unique for your account in the Region you selected. For this tutorial, we will name it rds-mysql-10minTutorial.
- Master Username: Type a username that you will use to log in to your DB instance. We will use masterUsername in this example.
- Master Password: Type a password that contains from 8 to 41 printable ASCII characters (excluding /,", and @) for your master user password.
- Confirm Password: Retype your password
- Allocated Storage: Type 5 to allocate 5 GB of storage for your database. For more information about storage allocation, see Amazon Relational Database Service Features. (switch ordering, its after storage type)
Click Next Step
f. You are now on the Configure Advanced Settings page where you can provide additional information that Amazon RDS needs to launch the MySQL DB instance. The list below shows settings for our example DB instance.
- VPC: Select Default VPC. For more information about VPC, see Amazon RDS and Amazon Virtual Private Cloud (VPC).
- Subnet Group: Choose the default subnet group. For more information about subnet groups, see Working with DB Subnet Groups.
- Publicly Accessible: Choose Yes. This will allocate an IP address for your database instance so you can directly connect to the database from your own device.
- Availability Zone: Choose No Preference. See Regions and Availability Zones for more details.
- VPC Security Group(s): Select Create New Security Group. This will create a security group that will allow connection from the IP address of the device you are currently using, to the database created.
- Database Name: Type a database name that is 1 to 64 alpha-numeric characters. If you do not provide a name, Amazon RDS will not automatically create a database on the DB instance you are creating.
- Database Port: Leave the default value of 3306.
- DB Parameter Group: Leave the default value of default.mysql5.6. For more information, see Working with DB Parameter Groups.
- Option Group: Select the default value of default:mysql5.6. Amazon RDS uses option groups to enable and configure additional features. For more information, see Working with Option Groups.
- Enable Encryption: For this task, select No to disable encryption. For more information, see Encrypting Amazon RDS Resources.
- Backup Retention Period: You can choose the number of days to retain the backup you take. For this tutorial, set this value to 1.
- Backup Window: Use the default of No Preference.
- Enable Enhanced Monitoring: Enabling Enhanced Monitoring will give you metrics in real time for the operating system (OS) that your DB instance runs on. For more information, see Viewing DB Instance Metrics.
- Auto Minor Version Upgrade: Select Yes to receive automatic updates when they become available.
- Maintenance Window: Select No Preference.
Click Launch DB Instance
g. Your DB Instance is now being created. Click View Your DB Instance
Note: Depending on the DB instance class and storage allocated, it could take several minutes for the new DB instance to become available.
The new DB instance appears in the list of DB instances on the Amazon RDS console. The DB instance will have a status of creating until the DB instance is created and ready for use. When the state changes to available, you can connect to a database on the DB instance.
Feel free to move on to the next step as you wait for the DB instance to become available.
Once the database instance creation is complete and the status changes to available, you can connect to a database on the DB instance using any standard SQL client. In this step, we will download MySQL Workbench which is a popular SQL client.
Note: Remember to use MySQL Workbench from the same device from which you created the DB Instance. The security group your database is placed in is configured to allow connection only from the device from which you created the DB instance.
b. You will be prompted to login, sign up, or begin your download. You can click No thanks, just start my download for a quick download.
a. Launch the MySQL Workbench application and go to Database > Connect to Database (Ctrl+U) from the menu bar.
b. A dialogue box appears. Enter the following:
- Hostname: You can find your hostname on the Amazon RDS console as shown in the screenshot to the right.
- Port: The default value should be 3306.
- Username: Type in the username you created for the Amazon RDS database. Our example was 'masterUsername.'
- Password: Click Store in Vault and enter the password you used while creating the Amazon RDS database.
c. You are now connected to the database! On the MySQL Workbench, you will see various schema objects available in the database. Now you can start creating tables, insert data, and run queries.
You can easily delete the MySQL DB Instance from the Amazon RDS console. In fact, it is a best practice to delete instances you are no longer using so you don’t keep getting charged for them.
a. Go back to your Amazon RDS Console. Select Instance Actions and click Delete from the dropdown menu.
b. You are asked to create a final snapshot. For our example, select No in the drop-down, check the acknowledgment box, and click Delete.
Note: Deleting your DB Instance may take a few minutes
You have created, connected to, and deleted a MySQL Database Instance with Amazon RDS. Amazon RDS makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing you up to focus on your applications and business.