Q: Which versions of MySQL does Amazon RDS support?
Q: How does Amazon RDS distinguish between “major” and “minor” version releases?
In the context of MySQL, version numbers are organized as follows:
MySQL version = X.Y.Z
X = Major version, Y = Release level, Z = Version number within release series.
From the Amazon RDS standpoint, a version change would be considered major if either major version or release level is being changed. Example: going from 5.6.X -> 5.7.X.
A version change would be considered minor if the version number within the release is being changed. Example: going from 5.6.27 -> 5.6.29.
Q: Does Amazon RDS provide guidelines for upgrading engine versions or deprecation of engine versions that are currently supported?
Yes. Please refer to the Amazon RDS FAQs.
Q: What storage engines does Amazon RDS for MySQL support?
The Point-In-Time-Restore and Snapshot Restore features of Amazon RDS for MySQL require a crash-recoverable storage engine and are supported for 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, 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. However, if you still choose to use MyISAM with Amazon RDS, following these steps may be helpful in certain scenarios for DB snapshot restore functionality.
Federated Storage Engine is currently not supported by Amazon RDS for MySQL.
Q: What privileges are granted to the master user for an RDS MySQL DB instance?
When you create a new DB instance, the default master user that you use gets certain privileges. See Master User Account Privileges in the Amazon RDS User Guide for a list of the privileges.
Q: Which versions of Amazon RDS for MySQL supports Read Replicas?
DB Instances with MySQL version 5.5 or newer support creation of Read Replicas. Cross-region Read Replicas are supported on MySQL 5.6 and later. Automatic backups are supported only for Amazon RDS Read Replicas running MySQL 5.6 and later.
Automatic backups must be and remain enabled on the source DB Instance for Read Replica operations.
Q: Which storage engines are supported for use with Amazon RDS for MySQL Read Replicas?
Amazon RDS for MySQL Read Replicas require a transactional storage engine and are only supported for the InnoDB storage engine. Non-transactional MySQL storage engines such as MyISAM might prevent Read Replicas from working as intended. However, if you still choose to use MyISAM with Read Replicas, we advise you to watch the Amazon CloudWatch “Replica Lag” metric (available via the AWS Management Console or Amazon CloudWatch APIs) carefully and recreate the Read Replica should it fall behind due to replication errors. The same considerations apply to the use of temporary tables and any other non-transactional engines.
Q: Can I configure the replication between my source Amazon RDS for MySQL DB Instance and a Read Replica to use row-based replication?
You can set the binary logging format to row-based, for MySQL version 5.6 and later. By default, replication is set to mixed-format (which includes both row-based and statement-based replication) which should meet the requirements of most use cases. The MySQL documentation offers more information about the difference between mixed-format and row-based replication.
Q: My Amazon RDS for MySQL Read Replica appears “stuck” after a Multi-AZ failover and is unable to obtain or apply updates from the source DB instance. What do I do?
You may find in some cases that your Amazon RDS for MySQL Read Replica(s) aren’t able to receive or apply updates from their source Multi-AZ DB instance after a Multi-AZ failover. This may be due to MySQL binlog events not being flushed to disk at the time of the failover. It is important that you configure your MySQL DB instance for replication as described in the Amazon RDS User Guide.