AWS AmazonRDS documentation change
Summary
Restructured documentation into numbered tasks, updated commands/links for MySQL/MariaDB versions, added clarifications on replication methods, and expanded security best practices for credentials and migration procedures.
Security assessment
The changes include expanded guidance on security best practices such as specifying credentials securely, using `--single-transaction` for consistent backups, excluding system schemas, and migrating users with tools like pt-show-grants. However, there is no explicit mention of addressing a specific security vulnerability or incident.
Diff
diff --git a/AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.NonRDSRepl.md b/AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.NonRDSRepl.md index 43ef0a0c2..703966d93 100644 --- a//AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.NonRDSRepl.md +++ b//AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.NonRDSRepl.md @@ -5 +5 @@ -Create a copy of your existing databaseCreate an Amazon EC2 instance and copy the compressed databaseCreate a MySQL or MariaDB database and import data from your Amazon EC2 instanceReplicate between your external database and new Amazon RDS databaseRedirect your live application to your Amazon RDS instance +Task 1: Create a copy of your existing databaseTask 2: Create an Amazon EC2 instanceTask 3: Create a MySQL or MariaDB databaseTask 4: Replicate data from your external databaseTask 5: Redirect your live application @@ -9 +9 @@ Create a copy of your existing databaseCreate an Amazon EC2 instance and copy th -In some cases, you might need to import data from an external MariaDB or MySQL database that supports a live application to a MariaDB DB instance, a MySQL DB instance, or a MySQL Multi-AZ DB cluster. Use the following procedure to minimize the impact on availability of applications. This procedure can also help if you are working with a very large database. Using this procedure, you can reduce the cost of the import by reducing the amount of data that is passed across the network to AWS. +In some cases, you might need to import data from an external MariaDB or MySQL database that supports a live application to an RDS for MariaDB DB instance, an RDS for MySQL DB instance, or an RDS for MySQL Multi-AZ DB cluster. Use the following procedure to minimize the impact on availability of applications. This procedure can also help if you are working with a very large database. Using this procedure, you can reduce the cost of the import by reducing the amount of data that is passed across the network to AWS. @@ -11 +11 @@ In some cases, you might need to import data from an external MariaDB or MySQL d -In this procedure, you transfer a copy of your database data to an Amazon EC2 instance and import the data into a new Amazon RDS database. You then use replication to bring the Amazon RDS database up-to-date with your live external instance, before redirecting your application to the Amazon RDS database. Configure MariaDB replication based on global transaction identifiers (GTIDs) if the external instance is MariaDB 10.0.24 or higher and the target instance is RDS for MariaDB. Otherwise, configure replication based on binary log coordinates. We recommend GTID-based replication if your external database supports it because GTID-based replication is a more reliable method. For more information, see [Global transaction ID](http://mariadb.com/kb/en/mariadb/global-transaction-id/) in the MariaDB documentation. +In this procedure, you transfer a copy of your database data to an Amazon EC2 instance and import the data into a new Amazon RDS database. You then use replication to bring the Amazon RDS database up-to-date with your live external instance, before redirecting your application to the Amazon RDS database. If the external instance is MariaDB 10.0.24 or higher and the target instance is RDS for MariaDB, configure MariaDB replication based on global transaction identifiers (GTIDs). Otherwise, configure replication based on binary log coordinates. We recommend GTID-based replication if your external database supports it because GTID-based replication is a more reliable method. For more information, see [Global transaction ID](http://mariadb.com/kb/en/mariadb/global-transaction-id/) in the MariaDB documentation. @@ -15 +15 @@ In this procedure, you transfer a copy of your database data to an Amazon EC2 in -If you want to import data into a MySQL DB instance and your scenario supports it, we recommend moving data in and out of Amazon RDS by using backup files and Amazon S3. For more information, see [Restoring a backup into an Amazon RDS for MySQL DB instance](./MySQL.Procedural.Importing.html). +If you want to import data into an RDS for MySQL DB instance and your scenario supports it, we recommend moving data in and out of Amazon RDS by using backup files and Amazon S3. For more information, see [Restoring a backup into an Amazon RDS for MySQL DB instance](./MySQL.Procedural.Importing.html). @@ -17 +17 @@ If you want to import data into a MySQL DB instance and your scenario supports i - +The following diagram shows importing an external MySQL database into a MySQL database on Amazon RDS. @@ -19 +19,3 @@ If you want to import data into a MySQL DB instance and your scenario supports i -## Create a copy of your existing database + + +## Task 1: Create a copy of your existing database @@ -23 +25,3 @@ The first step in the process of migrating a large amount of data to an RDS for - +The following diagram shows creating a backup of the MySQL database. + + @@ -25 +29 @@ The first step in the process of migrating a large amount of data to an RDS for -You can use the mysqldump utility to create a database backup in either SQL or delimited-text format. We recommend that you do a test run with each format in a non-production environment to see which method minimizes the amount of time that mysqldump runs. +You can use the `mysqldump` utility to create a database backup in either SQL or delimited-text format. In MariaDB 10.5, the client is called [mariadb-dump](https://mariadb.com/kb/en/mariadb-dump/). Starting with MariaDB 11.0.1, you must use `mariadb-dump` instead of `mysqldump`. We recommend that you do a test run with each format in a non-production environment to see which method minimizes the amount of time that mysqldump runs. @@ -27 +31 @@ You can use the mysqldump utility to create a database backup in either SQL or d -We also recommend that you weigh mysqldump performance against the benefit offered by using the delimited-text format for loading. A backup using delimited-text format creates a tab-separated text file for each table being dumped. To reduce the amount of time required to import your database, you can load these files in parallel using the `LOAD DATA LOCAL INFILE` command. For more information about choosing a mysqldump format and then loading the data, see [ Using mysqldump for backups](https://dev.mysql.com/doc/mysql-backup-excerpt/8.0/en/using-mysqldump.html) in the MySQL documentation. +We also recommend that you weigh `mysqldump` performance against the benefit offered by using the delimited-text format for loading. A backup using delimited-text format creates a tab-separated text file for each table being dumped. To reduce the amount of time required to import your database, you can load these files in parallel using the `LOAD DATA LOCAL INFILE` command. For more information, see [Load the data](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.AnySourceMariaDB.html#MySQL.Procedural.Importing.AnySource.Step5) for MariaDB or [Load the data](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.AnySource.html#MySQL.Procedural.Importing.AnySource.Step5) for MySQL. @@ -31 +35,15 @@ Before you start the backup operation, make sure to set the replication options -###### Note +Make sure that you're aware of the following recommendations and considerations: + + * Use the `--single-transaction` option with `mysqldump` because it dumps a consistent state of the database. To ensure a valid dump file, don't run data definition language (DDL) statements while `mysqldump` is running. You can schedule a maintenance window for these operations. + + * Exclude the following schemas from the dump file: + + * `sys` + + * `performance_schema` + + * `information_schema` + +The `mysqldump` and `mariadb-dump` utility excludes these schemas by default. + + * If you need to migrate users and privileges, consider using a tool that generates the data control language (DCL) for recreating them, such as the [pt-show-grants](https://www.percona.com/doc/percona-toolkit/LATEST/pt-show-grants.html) utility. @@ -33 +50,0 @@ Before you start the backup operation, make sure to set the replication options -Use the `--single-transaction` option with mysqldump because it dumps a consistent state of the database. To ensure a valid dump file, don't run data definition language (DDL) statements while mysqldump is running. You can schedule a maintenance window for these operations. @@ -35 +51,0 @@ Use the `--single-transaction` option with mysqldump because it dumps a consiste -Exclude the following schemas from the dump file: `sys`, `performance_schema`, and `information_schema`. The mysqldump utility excludes these schemas by default. @@ -37 +52,0 @@ Exclude the following schemas from the dump file: `sys`, `performance_schema`, a -To migrate users and privileges, consider using a tool that generates the data control language (DCL) for recreating them, such as the [pt-show-grants](https://www.percona.com/doc/percona-toolkit/LATEST/pt-show-grants.html) utility. @@ -41 +56 @@ To migrate users and privileges, consider using a tool that generates the data c - 1. Edit the `my.cnf` file (this file is usually under `/etc`). + 1. Edit the `my.cnf` file. This file is usually located under `/etc`. @@ -47 +62 @@ Add the `log_bin` and `server_id` options to the `[mysqld]` section. The `log_bi -The following example shows the updated `[mysqld]` section of a `my.cnf` file. +The following example shows the updated `[mysqld]` section of a `my.cnf` file: @@ -53 +68 @@ The following example shows the updated `[mysqld]` section of a `my.cnf` file. -For more information, see [the MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterbaseconfig.html). +For more information, see [Setting the Replication Source Configuration](https://dev.mysql.com/doc/refman/8.4/en/replication-howto-masterbaseconfig.html) in the MySQL documentation. @@ -55 +70 @@ For more information, see [the MySQL documentation](https://dev.mysql.com/doc/re - 2. For replication with a Multi-AZ DB cluster, set the `ENFORCE_GTID_CONSISTENCY` and the `GTID_MODE` parameter to `ON`. + 2. For replication with a Multi-AZ DB cluster set the `ENFORCE_GTID_CONSISTENCY` and the `GTID_MODE` parameter to `ON`. @@ -72 +87 @@ These settings aren't required for replication with a DB instance. - 1. Create a backup of your data using the mysqldump utility, specifying either SQL or delimited-text format. + 1. Create a backup of your data using the `mysqldump` utility or the `mariadb-dump` utility, specifying either SQL or delimited-text format. @@ -74 +89 @@ These settings aren't required for replication with a DB instance. -Specify `--master-data=2` to create a backup file that can be used to start replication between servers. For more information, see the [ mysqldump](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html#option_mysqldump_master-data) documentation. +For MySQL 8.0.25 and lower versions, specify `--master-data=2` to create a backup file that can be used to start replication between servers. For MySQL 8.0.26 and higher versions, specify `--source-data=2` to create a backup file that can be used to start replication between servers. For more information, see the [mysqldump — A Database Backup Program](https://dev.mysql.com/doc/refman/8.4/en/mysqldump.html) in the MySQL documentation. @@ -76 +91 @@ Specify `--master-data=2` to create a backup file that can be used to start repl -To improve performance and ensure data integrity, use the `--order-by-primary` and `--single-transaction` options of mysqldump. +To improve performance and ensure data integrity, use the `--order-by-primary` and `--single-transaction` options for `mysqldump`. @@ -78 +93 @@ To improve performance and ensure data integrity, use the `--order-by-primary` a -To avoid including the MySQL system database in the backup, do not use the `--all-databases` option with mysqldump. For more information, see [ Creating a data snapshot using mysqldump](https://dev.mysql.com/doc/mysql-replication-excerpt/8.0/en/replication-howto-mysqldump.html) in the MySQL documentation. +To avoid including the MySQL system database in the backup, don't use the `--all-databases` option with `mysqldump`. For more information, see [Creating a Data Snapshot Using mysqldump](https://dev.mysql.com/doc/mysql-replication-excerpt/8.0/en/replication-howto-mysqldump.html) in the MySQL documentation. @@ -80 +95 @@ To avoid including the MySQL system database in the backup, do not use the `--al -Use `chmod` if necessary to make sure that the directory where the backup file is being created is writeable. +Use `chmod`, if necessary, to make sure that the directory where the backup file is being created is writeable. @@ -86 +101 @@ On Windows, run the command window as an administrator. - * To produce SQL output, use the following command. + * To produce SQL output, use the following command: @@ -101 +116 @@ For Linux, macOS, or Unix: -Specify credentials other than the prompts shown here as a security best practice. +As a security best practice, specify credentials other than the prompts shown in the example. @@ -116 +131 @@ For Windows: -Specify credentials other than the prompts shown here as a security best practice. +As a security best practice, specify credentials other than the prompts shown in the example. @@ -118 +133 @@ Specify credentials other than the prompts shown here as a security best practic - * To produce delimited-text output, use the following command. + * To produce delimited-text output, use the following command: @@ -148 +163,3 @@ For Windows: -Specify credentials other than the prompts shown here as a security best practice. +As a security best practice, specify credentials other than the prompts shown in the example. + +Make sure to create any stored procedures, triggers, functions, or events manually in your Amazon RDS database. If you have any of these objects in the database that you are copying, then exclude them when you run `mysqldump`. To do so, include the following arguments with your `mysqldump` command: @@ -150 +167 @@ Specify credentials other than the prompts shown here as a security best practic -Make sure to create any stored procedures, triggers, functions, or events manually in your Amazon RDS database. If you have any of these objects in the database that you are copying, exclude them when you run mysqldump. To do so, include the following arguments with your mysqldump command: `--routines=0 --triggers=0 --events=0`. + * `--routines=0` @@ -152 +169,7 @@ Make sure to create any stored procedures, triggers, functions, or events manual -When using the delimited-text format, a `CHANGE MASTER TO` comment is returned when you run mysqldump. This comment contains the master log file name and position. If the external instance is other than MariaDB version 10.0.24 or higher, note the values for `MASTER_LOG_FILE` and `MASTER_LOG_POS`. You need these values when setting up replication. + * `--triggers=0` + + * `--events=0` + +For MySQL 8.0.22 and lower versions and MariaDB versions, when you run `mysqldump` and specify the delimited-text format, a `CHANGE MASTER TO` comment is returned. This comment contains the master log file name and position. For MySQL 8.0.23 and higher versions, when you run `mysqldump` using the delimited-text format, a `CHANGE REPLICATION SOURCE TO` comment is returned. This comment contains the source log file name and position. If the external instance is anything other than MariaDB 10.0.24 and higher versions, or MySQL 8.0.23 and higher versions, note the values for `MASTER_LOG_FILE` and `MASTER_LOG_POS`. You need these values when setting up replication. + +The following output is returned for MariaDB versions and for MySQL 8.0.22 and lower versions: @@ -158 +181 @@ When using the delimited-text format, a `CHANGE MASTER TO` comment is returned w -If you are using SQL format, you can get the master log file name and position in the `CHANGE MASTER TO` comment in the backup file. If the external instance is MariaDB version 10.0.24 or higher, you can get the GTID in the next step. +The following output is returned for MySQL 8.0.23 and higher versions: @@ -160 +183,7 @@ If you are using SQL format, you can get the master log file name and position i - 2. If the external instance you are using is MariaDB version 10.0.24 or higher, you use GTID-based replication. Run `SHOW MASTER STATUS` on the external MariaDB instance to get the binary log file name and position, then convert them to a GTID by running `BINLOG_GTID_POS` on the external MariaDB instance. + -- Position to start replication or point-in-time recovery from + -- + -- CHANGE SOURCE TO SOURCE_LOG_FILE='mysql-bin-changelog.000031', SOURCE_LOG_POS=107; + +For MySQL 8.0.22 and lower versions, if you are using SQL format, you can get the master log file name and position in the `CHANGE MASTER TO` comment in the backup file. For MySQL 8.0.23 and higher versions, if you are using SQL format, you can get the source log file name and position in the `CHANGE REPLICATION SOURCE TO` comment in the backup file. If the external instance is MariaDB version 10.0.24 or higher, you can get the GTID in the next step. + + 2. If the external instance you are using is MariaDB version 10.0.24 or higher, use GTID-based replication. Run `SHOW MASTER STATUS` on the external MariaDB instance to get the binary log file name and position, and then convert them to a GTID by running `BINLOG_GTID_POS` on the external MariaDB instance. @@ -162 +191 @@ If you are using SQL format, you can get the master log file name and position i - SELECT BINLOG_GTID_POS('binary log file name', binary log file position); + SELECT BINLOG_GTID_POS('binary_log_file_name', binary_log_file_position); @@ -164 +193 @@ If you are using SQL format, you can get the master log file name and position i -Note the GTID returned; you need it to configure replication. +Note the GTID returned. You need the GTID to configure replication. @@ -168 +197 @@ Note the GTID returned; you need it to configure replication. - * To compress SQL output, use the following command. + * To compress SQL output, use the following command: @@ -172 +201 @@ Note the GTID returned; you need it to configure replication. - * To compress delimited-text output, use the following command. + * To compress delimited-text output, use the following command: @@ -179 +208 @@ Note the GTID returned; you need it to configure replication. -## Create an Amazon EC2 instance and copy the compressed database +## Task 2: Create an Amazon EC2 instance and copy the compressed database @@ -183 +212,3 @@ Copying your compressed database backup file to an Amazon EC2 instance takes few - +The following diagram shows copying the database backup to an Amazon EC2 instance. + + @@ -187 +218 @@ Copying your compressed database backup file to an Amazon EC2 instance takes few - 1. In the AWS Region where you plan to create the RDS database, create a virtual private cloud (VPC), a VPC security group, and a VPC subnet. Ensure that the inbound rules for your VPC security group allow the IP addresses required for your application to connect to AWS. You can specify a range of IP addresses (for example, `203.0.113.0/24`), or another VPC security group. You can use the [Amazon VPC Management Console](https://console.aws.amazon.com/vpc) to create and manage VPCs, subnets, and security groups. For more information, see [Getting started with Amazon VPC](https://docs.aws.amazon.com/AmazonVPC/latest/GettingStartedGuide/GetStarted.html) in the _Amazon Virtual Private Cloud Getting Started Guide_. + 1. In the AWS Region where you plan to create the Amazon RDS database, create a virtual private cloud (VPC), a VPC security group, and a VPC subnet. Ensure that the inbound rules for your VPC security group allow the IP addresses required for your application to connect to AWS. You can specify a range of IP addresses—for example, `203.0.113.0/24`—or another VPC security group. You can use the [Amazon VPC console](https://console.aws.amazon.com/vpc) to create and manage VPCs, subnets, and security groups. For more information, see [Getting started with Amazon VPC](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html#getting-started) in the _Amazon Virtual Private Cloud User Guide_. @@ -189 +220 @@ Copying your compressed database backup file to an Amazon EC2 instance takes few - 2. Open the [Amazon EC2 Management Console](https://console.aws.amazon.com/ec2) and choose the AWS Region to contain both your Amazon EC2 instance and your Amazon RDS database. Launch an Amazon EC2 instance using the VPC, subnet, and security group that you created in Step 1. Ensure that you select an instance type with enough storage for your database backup file when it is uncompressed. For details on Amazon EC2 instances, see [Getting started with Amazon EC2 Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) in the _Amazon Elastic Compute Cloud User Guide for Linux_. + 2. Open the [Amazon EC2 console](https://console.aws.amazon.com/ec2) and choose the AWS Region to contain both your Amazon EC2 instance and your Amazon RDS database. Launch an Amazon EC2 instance using the VPC, subnet, and security group that you created in Step 1. Ensure that you select an instance type with enough storage for your database backup file when it is uncompressed. For details on Amazon EC2 instances, see [Getting started with Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) in the _Amazon Elastic Compute Cloud User Guide_. @@ -191 +222 @@ Copying your compressed database backup file to an Amazon EC2 instance takes few - 3. To connect to your Amazon RDS database from your Amazon EC2 instance, edit your VPC security group. Add an inbound rule specifying the private IP address of your EC2 instance. You can find the private IP address on the **Details** tab of the **Instance** pane in the EC2 console window. To edit the VPC security group and add an inbound rule, choose **Security Groups** in the EC2 console navigation pane, choose your security group, and then add an inbound rule for MySQL or Aurora specifying the private IP address of your EC2 instance. To learn how to add an inbound rule to a VPC security group, see [Adding and removing rules](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html#AddRemoveRules) in the _Amazon VPC User Guide_. + 3. To connect to your Amazon RDS database from your Amazon EC2 instance, edit your VPC security group. Add an inbound rule specifying the private IP address of your EC2 instance. You can find the private IP address on the **Details** tab of the **Instance** pane in the EC2 console window. To edit the VPC security group and add an inbound rule, choose **Security Groups** in the EC2 console navigation pane, choose your security group, and then add an inbound rule for MySQL or Aurora specifying the private IP address of your EC2 instance. To learn how to add an inbound rule to a VPC security group, see [Security group rules](https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html) in the _Amazon Virtual Private Cloud User Guide_. @@ -193 +224 @@ Copying your compressed database backup file to an Amazon EC2 instance takes few - 4. Copy your compressed database backup file from your local system to your Amazon EC2 instance. Use `chmod` if necessary to make sure that you have write permission for the target directory of the Amazon EC2 instance. You can use `scp` or a Secure Shell (SSH) client to copy the file. The following is an example. + 4. Copy your compressed database backup file from your local system to your Amazon EC2 instance. Use `chmod`, if necessary, to make sure that you have write permission for the target directory of the Amazon EC2 instance. You can use `scp` or a Secure Shell (SSH) client to copy the file. The following command is an example `scp` command: @@ -199 +230 @@ Copying your compressed database backup file to an Amazon EC2 instance takes few -Be sure to copy sensitive data using a secure network transfer protocol. +When copying sensitive data, be sure to use a secure network transfer protocol. @@ -201 +232 @@ Be sure to copy sensitive data using a secure network transfer protocol. - 5. Connect to your Amazon EC2 instance and install the latest updates and the MySQL client tools using the following commands. + 5. Connect to your Amazon EC2 instance and install the latest updates and the MySQL client tools using the following commands: @@ -206 +237 @@ Be sure to copy sensitive data using a secure network transfer protocol. -For more information, see [Connect to your instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-connect-to-instance-linux.html) in the _Amazon Elastic Compute Cloud User Guide for Linux_. +For more information, see [Connect to your instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html#ec2-connect-to-instance-linux) for Linux instances in the _Amazon Elastic Compute Cloud User Guide_. @@ -210 +241 @@ For more information, see [Connect to your instance](https://docs.aws.amazon.com -This example installs the MySQL client on an Amazon Machine Image (AMI) for an Amazon Linux distribution. To install the MySQL client on a different distribution, such as Ubuntu or Red Hat Enterprise Linux, this example doesn't work. For information about installing MySQL, see [Installing and Upgrading MySQL](https://dev.mysql.com/doc/refman/8.0/en/installing.html) in the MySQL documentation. +This example installs the MySQL client on an Amazon Machine Image (AMI) for an Amazon Linux distribution. This example doesn't install the MySQL client on a different distribution, such as Ubuntu or Red Hat Enterprise Linux. For information about installing MySQL, see [Installing MySQL](https://dev.mysql.com/doc/refman/8.4/en/installing.html) in the MySQL documentation. @@ -212 +243 @@ This example installs the MySQL client on an Amazon Machine Image (AMI) for an A - 6. While connected to your Amazon EC2 instance, decompress your database backup file. The following are examples. + 6. While connected to your Amazon EC2 instance, decompress your database backup file. The following commands are examples. @@ -214 +245 @@ This example installs the MySQL client on an Amazon Machine Image (AMI) for an A - * To decompress SQL output, use the following command. + * To decompress SQL output, use the following command: @@ -218 +249 @@ This example installs the MySQL client on an Amazon Machine Image (AMI) for an A - * To decompress delimited-text output, use the following command. + * To decompress delimited-text output, use the following command: @@ -225 +256,3 @@ This example installs the MySQL client on an Amazon Machine Image (AMI) for an A -## Create a MySQL or MariaDB database and import data from your Amazon EC2 instance +## Task 3: Create a MySQL or MariaDB database and import data from your Amazon EC2 instance + +By creating an RDS for MariaDB DB instance, an RDS for MySQL DB instance, or an RDS for MySQL Multi-AZ DB cluster in the same AWS Region as your Amazon EC2 instance, you can import the database backup file from Amazon EC2 faster than over the internet. @@ -227 +260 @@ This example installs the MySQL client on an Amazon Machine Image (AMI) for an A -By creating a MariaDB DB instance, a MySQL DB instance, or a MySQL Multi-AZ DB cluster in the same AWS Region as your Amazon EC2 instance, you can import the database backup file from EC2 faster than over the internet. +The following diagram shows importing the backup from an Amazon EC2 instance into a MySQL database. @@ -229 +262 @@ By creating a MariaDB DB instance, a MySQL DB instance, or a MySQL Multi-AZ DB c - + @@ -233 +266 @@ By creating a MariaDB DB instance, a MySQL DB instance, or a MySQL Multi-AZ DB c - 1. Determine which DB instance class and what amount of storage space is required to support the expected workload for this Amazon RDS database. As part of this process, decide what is sufficient space and processing capacity for your data load procedures. Also decide what is required to handle the production workload. You can estimate this based on the size and resources of the source MariaDB or MySQL database. For more information, see [DB instance classes](./Concepts.DBInstanceClass.html). + 1. Determine which DB instance class and what amount of storage space is required to support the expected workload for this Amazon RDS database. As part of this process, decide what is sufficient space and processing capacity for your data load procedures. Also, decide what is required to handle the production workload. You can estimate this based on the size and resources of the source MariaDB or MySQL database. For more information, see [DB instance classes](./Concepts.DBInstanceClass.html). @@ -237 +270 @@ By creating a MariaDB DB instance, a MySQL DB instance, or a MySQL Multi-AZ DB c -To create a MySQL Multi-AZ DB cluster, follow the instructions in [Creating a Multi-AZ DB cluster for Amazon RDS](./create-multi-az-db-cluster.html). +To create an RDS for MySQL Multi-AZ DB cluster, follow the instructions in [Creating a Multi-AZ DB cluster for Amazon RDS](./create-multi-az-db-cluster.html). @@ -239 +272 @@ To create a MySQL Multi-AZ DB cluster, follow the instructions in [Creating a Mu -To create a MariaDB or MySQL DB instance, follow the instructions in [Creating an Amazon RDS DB instance](./USER_CreateDBInstance.html) and use the following guidelines: +To create an RDS for MariaDB or RDS for MySQL DB instance, follow the instructions in [Creating an Amazon RDS DB instance](./USER_CreateDBInstance.html) and use the following guidelines: @@ -241 +274 @@ To create a MariaDB or MySQL DB instance, follow the instructions in [Creating a