MySQL feature support on Amazon RDS
RDS for MySQL supports most of the features and capabilities of MySQL. Some features might have limited support or restricted privileges.
You can filter new Amazon RDS features on the What's
New with Database?MySQL 2022.
The following lists are not exhaustive.
Topics
MySQL feature support on Amazon RDS for MySQL major versions
In the following sections, find information about MySQL feature support on Amazon RDS for MySQL major versions:
For information about supported minor versions of Amazon RDS for MySQL, see Supported MySQL minor versions on Amazon RDS.
MySQL 9.7 support on Amazon RDS
MySQL 9.7 is a Long-Term Support (LTS) release. Amazon RDS supports the following new features and changes for your DB instances running MySQL version 9.7.
-
Reserved user for RDS Proxy – The
rdsproxyadminuser is a reserved user in MySQL 9.7. If you created a user namedrdsproxyadminyourself, not through RDS Proxy, drop or rename it before you upgrade. If RDS Proxy created the user, leave it in place. -
JSON Duality Views – You can now insert, update, and delete data through JSON duality views. Previously, the MySQL Community Edition supported only creating and querying them. Your applications can work with the same data as JSON documents or as relational rows. When you modify a JSON document through a duality view, MySQL applies the change to the underlying tables. To allow changes, the view definition must include modification annotations, and some statements, such as
REPLACE,INSERT ... ON DUPLICATE KEY UPDATE, and multi-row updates, aren't supported. For more information, see DML Operations on JSON Duality Viewsin the MySQL documentation. -
Hypergraph optimizer – The Hypergraph optimizer is an alternative query optimizer that you can turn on for complex queries that join many tables. It's off by default. To turn it on, set
hypergraph_optimizer=onin theoptimizer_switchparameter in a custom DB parameter group, or for the current session withSET SESSION optimizer_switch='hypergraph_optimizer=on'. We recommend that you test your workload with the Hypergraph optimizer before you turn it on for a production DB instance. For information about parameter groups, see Parameter groups for Amazon RDS. -
VECTOR data type – You can use the
VECTORdata type to store embeddings alongside your relational data. -
Active-active clusters – You can use RDS for MySQL 9.7 DB instances in active-active clusters. For more information, see Configuring active-active clusters for RDS for MySQL and Joining an active-active cluster with RDS for MySQL 9.7.
-
Security defaults – MySQL 9.7 on Amazon RDS includes the following security changes:
-
TLS required by default – In MySQL 9.7, the
require_secure_transportparameter defaults to1(ON). As a result, Amazon RDS rejects connections that don't use TLS. In MySQL 8.4, the default is0(OFF). To allow connections that don't use TLS, setrequire_secure_transportto0in a custom DB parameter group. For more information, see Requiring SSL/TLS for all connections to a MySQL DB instance on Amazon RDS. -
Post-quantum key exchange – As on RDS for MySQL 8.4.11 and higher, TLS 1.3 connections support the hybrid post-quantum key exchange groups
X25519MLKEM768andSecP256r1MLKEM768. To use them, your client's TLS library must support ML-KEM. -
mysql_native_passwordremoved – Themysql_native_passwordauthentication plugin isn't available in MySQL 9.7. Usecaching_sha2_passwordinstead. Before you upgrade to MySQL 9.7, change any database accounts that usemysql_native_password, because these accounts block the upgrade. Themysql_native_password_proxy_usersparameter is also removed. For more information, see MySQL default authentication plugin. -
PBKDF2-SHA512 password storage – You can choose to store
caching_sha2_passwordpassword hashes with PBKDF2-SHA512. To do so, set thecaching_sha2_password_storage_formatparameter toPBKDF2_SHA512in a custom DB parameter group. The new format applies only to passwords that you set or change after you modify the parameter. -
Password validation – The
validate_passwordplugin is removed in MySQL 9.7, and you can't install it. To turn on password validation, set therds.validate_passwordparameter in a custom DB parameter group. This parameter isn't set by default, so password validation is off. For more information, see Using password validation for MySQL 9.7.
-
-
New default values for parameters – The following parameters have new default values for MySQL 9.7 DB instances:
-
Several MySQL community parameter defaults changed. For example,
innodb_change_buffer_max_sizechanged from 25 to 5,innodb_change_bufferingfromnonetoall,binlog_transaction_dependency_history_sizefrom 25000 to 10000000,explain_json_format_versionfrom 1 to 2, andback_logto 10000. The newactivate_mandatory_rolesparameter isONby default, so roles named inmandatory_rolesare activated automatically when a user logs in. For more information, see What Is New in MySQL 9.7in the MySQL documentation. We recommend that you test your application's performance on RDS for MySQL 9.7 before you upgrade a production DB instance.
-
gtid-mode– The default value isON_PERMISSIVE. In MySQL 8.4, the default isOFF_PERMISSIVE. -
group_replication_ssl_modeandgroup_replication_recovery_use_ssl– The default values areREQUIREDandON. In MySQL 8.4, the defaults areDISABLEDandOFF.
-
-
New parameters – MySQL 9.7 adds the following parameters to the DB parameter group:
-
activate_mandatory_roles– This new parameter isONby default. -
caching_sha2_password_storage_format– This new parameter controls howcaching_sha2_passwordstores password hashes. The default isCRYPT5. -
caching_sha2_password_proxy_users– This new parameter isOFFby default. -
connection_memory_status_limitandglobal_connection_memory_status_limit– These new parameters set memory thresholds that increment status counters. They don't limit memory use. -
enable_cascade_triggers– This new parameter isOFFby default. -
innodb_native_foreign_keys– This new parameter isONby default, so InnoDB handles foreign key checks and cascades, as in MySQL 8.4. -
rds.validate_password– This new parameter turns thevalidate_passwordcomponent on or off. It isn't set by default, so password validation is off. -
table_open_cache_triggers– This new parameter controls the maximum number of open tables with fully loaded triggers. The default is524288. -
validate_password.*– These new parameters configure thevalidate_passwordcomponent, for examplevalidate_password.lengthandvalidate_password.policy.
-
-
Parameter behavior changes – If your custom DB parameter group for MySQL 8.4 sets any of the following parameters, update it in your custom DB parameter group for MySQL 9.7:
-
authentication_policy– The only allowed value is*:caching_sha2_password. -
validate-passwordandvalidate_password_*– Replaced byrds.validate_passwordand thevalidate_password.*parameters. -
replica_parallel_workers– The minimum value is1. -
character_set_*andcollation_*– Useutf8mb3orutf8mb4instead ofutf8, andutf8mb3_*collations instead ofutf8_*.
-
-
Removed parameters – RDS for MySQL removed the following parameters from parameter groups for MySQL 9.7 DB instances:
-
mysql_native_password_proxy_users -
replica_parallel_type -
temptable_use_mmap
-
-
Removed or changed functionality – The following functionality changed in MySQL 9.7:
-
MD5(),SHA1(), andSHA()functions – These functions aren't available on RDS for MySQL 9.7. UseSHA2()instead, or compute hashes in your application. If your views, stored routines, triggers, events, generated columns, column defaults,CHECKconstraints, or functional indexes use these functions, the upgrade precheck blocks the upgrade to MySQL 9.7. -
Reserved keywords – MySQL 9.7 adds the reserved keywords
EXTERNALandLIBRARY. The upgrade precheck blocks the upgrade if a stored procedure, stored function, trigger, or event uses either word unquoted in its body. Other objects namedEXTERNALorLIBRARYdon't block the upgrade, but SQL that refers to them without backticks fails after the upgrade. When you create a DB instance, the initial database name can't be a reserved word, includingEXTERNALorLIBRARY. For more information, see CreateDBInstance. For the full list, see Keywords and Reserved Wordsin the MySQL documentation.
-
For the changes between MySQL 8.4 and MySQL 9.7, see the following topics in the MySQL documentation:
-
MySQL 9.7 Release Notes
, and the release notes for MySQL 9.0 through 9.6 -
Server and Status Variables and Options Added, Deprecated, or Removed in MySQL 9.7
For information about upgrading to MySQL 9.7, see Upgrading to MySQL 9.7.
For a list of unsupported features, see MySQL features not supported by Amazon RDS.
MySQL 8.4 support on Amazon RDS
Amazon RDS supports the following new features for your DB instances running MySQL version 8.4 or higher.
-
Cryptographic library – RDS for MySQL replaced OpenSSL with AWS Libcrypto (AWS-LC), which is FIPS 140-3 certified. For more information, see the AWS-LC GitHub repository at https://github.com/aws/aws-lc
. -
TLS changes – RDS for MySQL only supports TLS 1.2 and TLS 1.3. For more information, see SSL/TLS support for MySQL DB instances on Amazon RDS.
-
memcached support – The memcached interface is no longer available on MySQL 8.4. For more information, see MySQL memcached support.
-
Default authentication plugin – The default authentication plugin is
caching_sha2_password. For more information, see MySQL default authentication plugin. -
mysqlpumpclient utility – Themysqlpumpclient utility is no longer available in MySQL 8.4. For more information, see Role-based privilege model for RDS for MySQL and mysqldump and mysqlpump in the AWS Prescriptive Guidance. -
Managed replication stored procedures – When using stored procedures to manage replication with a replication user configured with
caching_sha2_password, you must configure TLS by specifyingSOURCE_SSL=1.caching_sha2_passwordis the default authentication plugin for RDS for MySQL 8.4. -
Parameter behavior changes – The following parameters changed for MySQL 8.4.
-
innodb_dedicated_server– This parameter is now enabled by default. For more information, see Configuring buffer pool size and redo log capacity in MySQL 8.4 and higher. -
innodb_buffer_pool– The database engine now calculates this parameter, but you can override this setting. For more information, see Configuring buffer pool size and redo log capacity in MySQL 8.4 and higher. -
innodb_redo_log_capacity– This parameter now controls the size of the redo log files. The database engine now calculates this parameter, but you can override this setting. For more information, see Configuring buffer pool size and redo log capacity in MySQL 8.4 and higher.
-
-
Deprecated or removed parameters – RDS for MySQL removed the following parameters from parameter groups for MySQL 8.4 DB instances. The
innodb_redo_log_capacityparameter now controls the size of the redo log files.-
innodb_log_file_size -
innodb_log_files_in_group
-
-
New default values for parameters – The following parameters have new default values for MySQL 8.4 DB instances:
-
Various MySQL community parameters related to performance changed. For more information, see What is New in MySQL 8.4 since MySQL 8.0
. We recommend that you test your application's performance on RDS for MySQL 8.4 before migrating a production instance.
-
innodb_purge_threads– The default value is set to the formulaLEAST({DBInstanceVCPU/2},4)to prevent the InnoDB history list length from growing too large. -
group_replication_exit_state_action– The default value isOFFLINE_MODE, which aligns with the default in MySQL Community. For more information, see Considerations and best practices for RDS for MySQL active-active clusters. -
binlog_format– The default value isROW, which aligns with the default in MySQL Community. You can modify the parameter for Single-AZ DB instances or Multi-AZ DB instances, but not for Multi-AZ DB clusters. Multi-AZ DB clusters use semisynchronous replication, and whenbinlog_formatis set toMIXEDorSTATEMENT, replication fails.
-
-
Inclusive language changes – RDS for MySQL 8.4 includes changes from RDS for MySQL 8.0 related to keywords and system schemas for inclusive language. For more information, see Inclusive language changes for RDS for MySQL 8.4.
For a list of all MySQL 8.4 features and changes, see What Is New in
MySQL 8.4 since MySQL 8.0
For a list of unsupported features, see MySQL features not supported by Amazon RDS.
Supported storage engines for RDS for MySQL
While MySQL supports multiple storage engines with varying capabilities, not all of them are optimized for recovery and data durability. Amazon RDS fully supports the InnoDB storage engine for MySQL DB instances. Amazon RDS features such as Point-In-Time restore and snapshot restore require a recoverable storage engine and are supported for the InnoDB storage engine only. For more information, see MySQL memcached support.
The Federated Storage Engine is currently not supported by Amazon RDS for MySQL.
For user-created schemas, the MyISAM storage engine does not support reliable recovery and can result in lost or corrupt data when MySQL is restarted after a recovery, preventing Point-In-Time restore or snapshot restore from working as intended. However, if you still choose to use MyISAM with Amazon RDS, snapshots can be helpful under some conditions.
System tables in the mysql schema can be in MyISAM storage.
If you want to convert existing MyISAM tables to InnoDB tables, you can use the
ALTER TABLE command (for example, 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.
MySQL 5.1, 5.5, and 5.6 are no longer supported in Amazon RDS. However, you can restore existing MySQL 5.1, 5.5, and 5.6 snapshots. When you restore a MySQL 5.1, 5.5, or 5.6 snapshot, the DB instance is automatically upgraded to MySQL 5.7.
Using memcached and other options with MySQL on Amazon RDS
Most Amazon RDS DB engines support option groups that allow you to select
additional features for your DB instance. RDS for MySQL DB instances support the memcached option,
a simple, key-based cache. For more information about memcached and other options, see
Options for MySQL DB instances.
For more information about working with option groups, see
Working with option groups.
InnoDB cache warming for MySQL on Amazon RDS
InnoDB cache warming can provide performance gains for your MySQL DB instance by
saving the current state of the buffer pool when the DB instance is shut down, and then
reloading the buffer pool from the saved information when the DB instance starts up.
This bypasses the need for the buffer pool to "warm up" from normal database use and
instead preloads the buffer pool with the pages for known common queries. The file that
stores the saved buffer pool information only stores metadata for the pages that are in
the buffer pool, and not the pages themselves. As a result, the file does not require
much storage space. The file size is about 0.2 percent of the cache size. For example,
for a 64 GiB cache, the cache warming file size is 128 MiB. For more information on
InnoDB cache warming, see Saving
and restoring the buffer pool state
RDS for MySQL DB instances support InnoDB cache warming. To enable InnoDB cache warming,
set the innodb_buffer_pool_dump_at_shutdown and innodb_buffer_pool_load_at_startup
parameters to 1 in the parameter group for your DB instance. Changing these parameter values in a parameter group will
affect all MySQL DB instances that use that parameter group. To enable InnoDB cache warming for specific MySQL DB
instances, you might need to create a new parameter group for those instances. For information on parameter groups, see
Parameter groups for Amazon RDS.
InnoDB cache warming primarily provides a performance benefit for DB instances that use standard storage. If you use PIOPS storage, you do not commonly see a significant performance benefit.
If your MySQL DB instance does not shut down normally, such as during a failover, then the buffer pool state will not be saved to disk. In this case, MySQL loads whatever buffer pool file is available when the DB instance is restarted. No harm is done, but the restored buffer pool might not reflect the most recent state of the buffer pool prior to the restart. To ensure that you have a recent state of the buffer pool available to warm the InnoDB cache on startup, we recommend that you periodically dump the buffer pool "on demand."
You can create an event to dump the buffer pool automatically and on a regular
interval. For example, the following statement creates an event named
periodic_buffer_pool_dump that dumps the buffer pool every hour.
CREATE EVENT periodic_buffer_pool_dump ON SCHEDULE EVERY 1 HOUR DO CALL mysql.rds_innodb_buffer_pool_dump_now();
For more information on MySQL events, see Event
syntax
Dumping and loading the buffer pool on demand
You can save and load the InnoDB cache "on demand."
To dump the current state of the buffer pool to disk, call the mysql.rds_innodb_buffer_pool_dump_now stored procedure.
To load the saved state of the buffer pool from disk, call the mysql.rds_innodb_buffer_pool_load_now stored procedure.
To cancel a load operation in progress, call the mysql.rds_innodb_buffer_pool_load_abort stored procedure.
Inclusive language changes for RDS for MySQL 8.4
RDS for MySQL 8.4 includes changes from the MySQL 8.4 community edition related to
keywords and system schemas for inclusive language. For example, the SHOW REPLICA
STATUS command replaces SHOW SLAVE STATUS. These changes also
apply to RDS for MySQL 9.7, except that MySQL 9.7 removes
replica_parallel_type.
Configuration parameter name changes
The following configuration parameters have new names in RDS for MySQL 8.4.
For compatibility, you can check the parameter names in the mysql client
by using either name. You can only use the new names when modifying values in a custom
MySQL 8.4 parameter group. For more information, see Default and custom parameter groups.
| Name to be removed | New or preferred name |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The parameter replica_allow_batching isn't available because Amazon RDS doesn't support NDB clusters.
Stored procedure name changes
The following stored procedures have new names in RDS for MySQL 8.4.
For compatibility, you can use either name in the initial RDS for MySQL 8.4 release. The old procedure names are to be removed in a future release. For more information, see Configuring, starting, and stopping binary log (binlog) replication.
| Name to be removed | New or preferred name |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MySQL features not supported by Amazon RDS
Amazon RDS doesn't currently support the following MySQL features:
-
Authentication Plugin
-
Error Logging to the System Log
-
InnoDB Tablespace Encryption
-
NDB clusters
-
Password Strength Plugin
-
Persisted system variables
-
Rewriter Query Rewrite Plugin
-
Semisynchronous replication, except for Multi-AZ DB clusters
-
Transportable tablespace
-
X Plugin
Multi-AZ DB clusters aren't supported for RDS for MySQL 9.7. For more information, see Multi-AZ DB clusters and RDS for MySQL 9.7.
To deliver a managed service experience, Amazon RDS doesn't provide shell access to DB instances. It also restricts access to certain system procedures and tables that require advanced privileges. Amazon RDS supports access to databases on a DB instance using any standard SQL client application. Amazon RDS doesn't allow direct host access to a DB instance by using Telnet, Secure Shell (SSH), or Windows Remote Desktop Connection. When you create a DB instance, you are assigned as db_owner for all databases on that instance, and you have all database-level permissions except for those used for backups. Amazon RDS manages backups for you.