Today, Amazon Relational Database Service (Amazon RDS) announced support for MySQL version 9.7, the latest Long-Term Support (LTS) major version from the MySQL community, in addition to MySQL 8.0 and 8.4. As with prior versions, you can bring your existing MySQL code, applications and tools to Amazon RDS. For customers who need more time to upgrade, Amazon RDS continues to offer earlier major versions under RDS Extended Support: MySQL 8.0 entered RDS Extended Support on August 1, 2026, and MySQL 5.7 remains available under RDS Extended Support through June 30, 2029.

MySQL 9.7 is the second LTS Release from the community, following MySQL 8.4. It includes the features delivered across the 9.0 through 9.6 Innovation Releases and adds 9.7-specific capabilities. In this post, we explore notable features, list breaking changes and provide recommendations to ease the migration of your workloads to this version.

Note for MySQL 5.7 customers: RDS Extended Support for MySQL 5.7 on Amazon Aurora MySQL-Compatible Edition and Amazon RDS for MySQL has been extended through June 30, 2029 (previously February 28, 2027), with no change to Extended Support pricing. During this period, AWS plans to provide critical security patches and bug fixes. If you’re running MySQL 5.7 workloads, you can use this additional time to plan and validate upgrades to MySQL 8.4 or to the latest 9.7 without disruption (follow the upgrade path). For details, see Amazon Aurora and RDS for MySQL expand Extended Support for MySQL 5.7 through June 2029.

Before we turn to RDS for MySQL 9.7, we first revisit the MySQL versioning model. The community classifies every engine release as either an Innovation Release or a Long-Term Support (LTS) Release.

  • Innovation Releases: Released frequently for early and rapid experimentation, giving access to the latest features and changes. Each Innovation Release is supported only until the next Innovation Release, so support cycles are short. The MySQL community classified versions 9.0 through 9.6 as Innovation Releases. Because of their short lifecycle, RDS offers these versions in the Amazon RDS Database Preview Environment.
  • Long-Term Support (LTS) Releases: LTS Releases include stable, proven features, including functionality introduced in prior Innovation Releases. Features can be added or removed only in the first release of an LTS series (for example, 9.7.0) and there are no removals later in the series. Incremental releases within an LTS series (such as 9.7.1 and 9.7.2) contain only the fixes needed to reduce behavior-change risk and prioritize backward compatibility and security. MySQL 9.7 is an LTS series and follows MySQL 8.4 as the next LTS baseline.

Note that MySQL 9.7 is the final release line to use the current sequential version numbers. Subsequent Innovation and LTS Releases move to calendar versioning in a YY.M format. For example, MySQL 26.7 is the July 2026 release. An LTS Release keeps its YY.M version fixed throughout that series’ support lifecycle.

For more information, review MySQL Releases: Innovation and LTS.

Upgrading your Amazon RDS for MySQL 8.4 database to MySQL 9.7

Before planning your upgrade, review the MySQL community’s upgrade path guidelines and release model. MySQL supports upgrading to the next LTS series but not skipping one, so the path is LTS-to-LTS: MySQL 8.4 to MySQL 9.7. If you’re running MySQL 8.0, upgrade to 8.4 first, then to 9.7.

You have multiple options when upgrading: use Amazon RDS Blue/Green deployments, read replicas, or an in-place upgrade. We recommend blue/green deployments to minimize risk and downtime. A blue/green deployment creates two environments, your current production environment (Blue) and a staging environment (Green), kept in sync with native logical replication. You can safely test your application against 9.7 on the Green environment and promote it only after you’re confident in compatibility, without impacting production.

Before you upgrade, note the following requirements and limitations:

  • rdsproxyadmin becomes a reserved user. In MySQL 9.7, rdsproxyadmin is protected on all hosts, so you can no longer create, drop, rename, or change privileges for it. RDS Proxy creates and manages this user automatically when you register a proxy target, so if you use RDS Proxy, leave it in place. If you created the rdsproxyadmin user yourself, drop or rename it before you upgrade.
  • Blue/Green deployments are supported. RDS for MySQL supports Blue/Green deployments on all available 5.7, 8.0 and 8.4 versions. If you’re running MySQL 5.7, you can’t move directly to 9.7. Upgrade in steps, using a blue/green deployment for each hop: 5.7 to 8.0, then 8.0 to 8.4, then 8.4 to 9.7.
  • Replication from a MySQL 5.7 source to a 9.7 replica isn’t supported. Use a supported intermediate major version if you need to replicate between these versions.
  • Replicas running gtid_mode=OFF aren’t supported targets. RDS for MySQL 9.7 defaults to gtid_mode=ON_PERMISSIVE, which assigns global transaction identifiers (GTIDs) to new transactions. Raise any self-managed or external replica to at least OFF_PERMISSIVE before upgrading.
  • Multi-AZ DB clusters (Multi-AZ with two readable standbys) aren’t supported at launch. Amazon RDS for MySQL 9.7 doesn’t support Multi-AZ DB cluster deployments at GA and upgrades to 9.7 from an 8.4 Multi-AZ DB cluster with two readable standbys are blocked. Use a Single-AZ or Multi-AZ DB instance (single standby) deployment for 9.7.

In the following sections, we discuss changes introduced with MySQL 9.7 that might be relevant for your applications.

Changed parameter defaults

Amazon RDS for MySQL offers the 9.7 LTS series at minor version 9.7.4. Because MySQL 9.7 is an LTS series, its incremental releases (9.7.1 through 9.7.4) contain only bug and security fixes. No features are added or removed and no parameter defaults change, after 9.7.0. Every default change in the following table was introduced earlier in the 9.x Innovation series (specifically MySQL 9.5.0) and is carried into the 9.7 LTS baseline that 9.7.4 ships. The 9.7.0 release itself introduced no default changes. We recommend thoroughly testing your applications with these defaults before upgrading. The following table shows the default changes, relative to MySQL 8.4, for parameters available on Amazon RDS for MySQL:

Parameter MySQL 8.4 Default MySQL 9.7 Default
explain_format TRADITIONAL TREE
explain_json_format_version 1 2
innodb_change_buffering none all
innodb_log_writer_threads ON (dedicated log writer threads always enabled) Binary-log aware: if log_bin=ON, ON when CPUs > 32 (otherwise OFF). If log_bin=OFF, ON when CPUs > 4 (otherwise OFF)
binlog_transaction_dependency_history_size 25,000 (max 1,000,000) 10,000,000 (max 100,000,000)

The change to explain_format is especially visible: a bare EXPLAIN now returns TREE-format output instead of the traditional tabular format, which can affect tooling that parses EXPLAIN results. If you set any of these parameters explicitly in a parameter group today, review whether the new defaults better fit your workload before overriding them.

In addition to the preceding community defaults, Amazon RDS for MySQL 9.7 applies the following default values changes (relative to MySQL 8.4):

  • require_secure_transport now defaults to ON, so client connections must use SSL/TLS.
  • gtid_mode now defaults to ON_PERMISSIVE.
  • group_replication_ssl_mode defaults to REQUIRED, enforcing SSL for Group Replication (active-active cluster) communication.
  • authentication_policy allows only caching_sha2_password (the removed mysql_native_password plugin is no longer accepted).
  • innodb_change_buffer_max_size now defaults to 5 (down from 25), as a percentage of the buffer pool.
  • back_log now defaults to 10000 (up from 151).

Community MySQL 9.5.0 changed gtid_mode and enforce_gtid_consistency to ON. Amazon RDS for MySQL 9.7 keeps enforce_gtid_consistency=OFF and uses gtid_mode=ON_PERMISSIVE. See the following Amazon RDS for MySQL 9.7 enhancements section for details, including the note on active-active clusters (Group Replication is supported on all MySQL 9.7, 8.4 versions and on MySQL 8.0.35+).

New capabilities in MySQL 9.7

MySQL 9.7 adds several notable capabilities, highlighted in the following sections.

Hypergraph Optimizer

MySQL 9.7 makes the Hypergraph Optimizer available in the engine. It’s disabled by default and controlled through the optimizer_switch system variable, which you can set per session, globally, persisted, or per statement:

-- Session scope SET optimizer_switch = 'hypergraph_optimizer=on'; -- Per-statement hint SELECT /*+ SET_VAR(optimizer_switch = 'hypergraph_optimizer=on') */ ... ;

The Hypergraph Optimizer can improve plan quality for complex queries with many joins. We recommend evaluating it against representative queries before enabling it broadly. On Amazon RDS for MySQL, the session and per-statement forms shown earlier work unchanged. To enable it for an entire instance, set optimizer_switch in a DB parameter group.

JSON Duality Views

MySQL 9.7 introduces JSON Duality Views, which you can use to access relational tables as JSON documents, with support for data manipulation language (DML), not just data definition language (DDL), and auto-increment. This provides a bridge for applications that work naturally with JSON while keeping data in normalized relational tables.

Group Replication enhancements

MySQL 9.7 adds several Group Replication components that improve operational visibility and resilience:

  • Replication Applier Metrics Component: extended statistics for lag, throughput, queued work and worker behavior.
  • Group Replication Flow Control Statistics Component: visibility into cluster throttling.
  • Group Replication Resource Manager Component: automatic eviction of unhealthy members and automatic rejoin.
  • Group Replication Primary Election Component: up-to-date-aware primary election that prefers the most current member.

Security and authentication changes

MySQL 9.7 changes how accounts authenticate and how connections are secured. Review the following changes before you upgrade.

Removal of mysql_native_password

The mysql_native_password authentication plugin has reached the end of its deprecation path. It was deprecated in MySQL 8.0.34, disabled by default in MySQL 8.4 and removed as of MySQL 9.0, so it doesn’t exist in MySQL 9.7. Accounts that still authenticate with mysql_native_password can’t connect after the upgrade. The server also rejects native-password authentication requests from older client programs that lack the CLIENT_PLUGIN_AUTH capability.

Before upgrading, migrate any such accounts to caching_sha2_password (the default authentication plugin since MySQL 8.0) and update client drivers accordingly. To find affected accounts on your MySQL 8.4 instance, check for users whose plugin is still mysql_native_password:

SELECT user, host FROM mysql.user WHERE plugin = 'mysql_native_password';

On RDS for MySQL 9.7, the authentication_policy parameter can’t name mysql_native_password, because the plugin no longer exists. If you set that parameter in your current parameter group, make sure it specifies caching_sha2_password instead.

PBKDF2 storage format for caching_sha2_password

MySQL 9.7 adds a PBKDF2 storage format for caching_sha2_password credentials. On Amazon RDS for MySQL you select the format with caching_sha2_password_storage_format, which accepts CRYPT5 or PBKDF2_SHA512. The default remains CRYPT5.

RDS for MySQL 9.7 also makes the related caching_sha2_password_proxy_users parameter modifiable. It adds proxy-user support for the plugin and takes effect only when check_proxy_users is enabled.

Removed and deprecated variables

Several variables and plugins present in MySQL 8.4 are removed in the 9.x series. Review and update any automation, monitoring, or parameter groups that reference them before upgrading, because setting a removed variable can cause startup or upgrade issues.

Variable / plugin Replacement or behavior
mysql_native_password (plugin) Removed. Migrate accounts to caching_sha2_password
mysql_native_password_proxy_users Removed with the mysql_native_password plugin. Was customer-visible and modifiable in 8.4
replica_parallel_type Parallel replication now uses LOGICAL_CLOCK exclusively
group_replication_allow_local_lower_version_join Version compatibility is enforced automatically. No longer configurable
temptable_use_mmap Feature removed
innodb_undo_tablespaces Removed. The setting had been ignored since MySQL 8.0.14 (use CREATE/DROP UNDO TABLESPACE instead)

Replication variable renames (master/slave to source/replica)

MySQL has completed its shift from master/slave terminology to source/replica. As part of that change, MySQL 9.5.0 renamed the semisynchronous replication plugins: semisync_master became semisync_source and semisync_slave became semisync_replica.

On Amazon RDS for MySQL, the following parameters are visible but RDS-managed, so you can’t set them yourself. Their names still change with the upgrade, which matters if your monitoring, dashboards, or automation read them through SHOW VARIABLES or SHOW STATUS:

MySQL 8.4 MySQL 9.7
rpl_semi_sync_master_enabled rpl_semi_sync_source_enabled
rpl_semi_sync_slave_enabled rpl_semi_sync_replica_enabled
rpl_semi_sync_master_timeout rpl_semi_sync_source_timeout
rpl_semi_sync_master_wait_point rpl_semi_sync_source_wait_point
rpl_semi_sync_master_wait_for_slave_count rpl_semi_sync_source_wait_for_replica_count
rpl_semi_sync_master_wait_no_slave rpl_semi_sync_source_wait_no_replica
rpl_semi_sync_master_target_apply_lag rpl_semi_sync_source_target_apply_lag

Update any monitoring or automation that reads these names before upgrading.

Removed functions

MySQL 9.x moves some built-in SQL functions out of the server core. Review your code for the functions described in the following section before you upgrade.

MD5() and SHA1() SQL functions aren’t available

In MySQL 9.x, the MD5() and SHA1() SQL functions were moved out of the server core into a separate classic_hashing component. Amazon RDS for MySQL 9.7 doesn’t offer the classic_hashing component, so the MD5() and SHA1() SQL functions aren’t available.

Before upgrading, review your application and stored programs for use of MD5() and SHA1(). For hashing needs, use SHA2() (for example, SHA2(col, 256)), which remains available. There is no supported MD5() replacement, so plan application changes where it’s used.

Transitional foreign key handling variables

Amazon RDS for MySQL 9.7 sets innodb_native_foreign_keys=ON by default, so foreign key checks and cascade operations are handled by the InnoDB engine, the same behavior as MySQL 8.4. Cascaded changes are therefore not individually written to the binary log and change-data-capture (CDC) tools such as AWS Database Migration Service (AWS DMS) and Debezium see the same events they did on 8.4.

In community MySQL, innodb_native_foreign_keys defaults to OFF and the SQL layer performs foreign key cascades, which does write each cascaded change to the binary log, increasing binlog volume and surfacing those changes to CDC. The parameter is customer-modifiable, so if you set innodb_native_foreign_keys=OFF on RDS, plan for those additional binlog entries.

innodb_native_foreign_keys and enable_cascade_triggers are transitional variables introduced in the 9.x series (innodb_native_foreign_keys in 9.6, enable_cascade_triggers in 9.7) and already marked for eventual removal, so avoid building long-term dependencies on them.

Amazon RDS for MySQL 9.7 enhancements

Beyond the community engine changes described earlier, Amazon RDS for MySQL 9.7 makes several RDS-specific parameter-group and default choices. The changes most likely to affect an existing 8.4 workload are highlighted here.

Connections require TLS by default

require_secure_transport now defaults to ON in RDS for MySQL 9.7, changed from OFF in 8.4. Clients that connect without SSL/TLS are rejected. Before upgrading, confirm that your applications and drivers connect over TLS, or set require_secure_transport=OFF in your parameter group if you must continue to allow non-TLS connections.

GTID defaults on RDS

Community MySQL changed the GTID defaults to ON in 9.5.0. Amazon RDS for MySQL 9.7 deliberately doesn’t adopt those values as-is:

  • enforce_gtid_consistency stays OFF, unchanged from 8.4. Enable it explicitly if your workload needs GTID consistency enforcement.
  • gtid_mode moves from OFF_PERMISSIVE (8.4) to ON_PERMISSIVE, promoting GTIDs rather than enforcing them.

This keeps GTID behavior close to 8.4 while moving in the community’s direction.

Because ON_PERMISSIVE assigns GTIDs to new transactions, two things change for replication. First, a replica running gtid_mode=OFF isn’t a supported target for a 9.7 source, although it was supported for an 8.4 source at OFF_PERMISSIVE. If you replicate from Amazon RDS for MySQL to a self-managed or external replica, set that replica to at least OFF_PERMISSIVE before you upgrade. Replication into 9.7 from a source without GTIDs is unaffected. Second, GTIDs now appear in the binary log, so verify any tool that reads binlogs directly. GTID auto-positioning still requires gtid_mode=ON. Moving to ON requires setting enforce_gtid_consistency=ON first, which rejects GTID-unsafe statements such as a transaction that updates both InnoDB and MyISAM tables.

Group Replication (active-active clusters)

For active-active clusters that use the MySQL Group Replication plugin, group_replication_ssl_mode now defaults to REQUIRED, enforcing SSL for Group Replication communication.

Authentication changes

  • authentication_policy can’t name mysql_native_password, because the plugin is removed from the engine. Set it to caching_sha2_password instead (see Removal of mysql_native_password).
  • ssl_cipher is now dynamic: it can be changed without a restart (it was static in 8.4).

Password validation moves to the component

RDS for MySQL 9.7 uses component-based password validation exclusively (the plugin form is gone):

  • The validate-password parameter is replaced by rds.validate_password, which controls installation of the validate_password component.
  • The underscore-style variables are renamed to dot-notation, for example validate_password_length becomes validate_password.length and validate_password_policy becomes validate_password.policy. Two new checks are available: validate_password.changed_characters_percentage and validate_password.check_user_name.

Because the parameters are renamed, your existing validate_password_* values don’t carry across the upgrade. A value set in your 8.4 parameter group isn’t applied in 9.7, and password validation falls back to the component defaults, which might be weaker than your current policy. Record your current validate_password_* values before you upgrade, then set the matching validate_password.* parameters in your 9.7 parameter group. Also update any automation that references the old validate_password_* names or the validate-password plugin.

New customer-visible parameters

RDS for MySQL 9.7 exposes several new modifiable parameters:

Parameter Purpose
activate_mandatory_roles Activate mandatory roles in addition to an account’s default roles (new in 9.7. Defaults to ON)
innodb_native_foreign_keys InnoDB-level foreign key checks and cascades. Defaults to ON on RDS (same as 8.4). See Transitional foreign key handling variables
caching_sha2_password_storage_format Storage format for caching_sha2_password credentials (CRYPT5 or PBKDF2_SHA512. Default CRYPT5)
caching_sha2_password_proxy_users Whether caching_sha2_password supports proxy users (effective only with check_proxy_users)
enable_cascade_triggers Execute triggers on child tables during foreign key cascade operations (transitional)
table_open_cache_triggers Maximum number of cached open tables with loaded triggers
connection_memory_status_limit Per-connection memory threshold before the status counter increments
global_connection_memory_status_limit Total connection-memory threshold before the status counter increments

Other parameter changes

  • Removed variables: see the preceding Removed and deprecated variables section (replica_parallel_type, innodb_undo_tablespaces and temptable_use_mmap).
  • replica_parallel_workers minimum allowed value changes from 0 to 1: single-threaded applier mode is gone.
  • binlog_transaction_dependency_history_size allowed range on RDS expands to 1 to 100,000,000.
  • Character sets: the utf8 alias appears as utf8mb3 in the allowed values for the character_set_* parameters and the utf8 collations are renamed to utf8mb3_*.

Migration checklist

The following checklist recaps the changes covered in this post so that you can work through them as a single list when upgrading from MySQL 8.4 to 9.7. The list moves from tasks to complete before you start the upgrade, through changed defaults to review, to new capabilities worth evaluating after you’re running 9.7.

  1. If RDS Proxy isn’t attached, drop the rdsproxyadmin user if it exists. In MySQL 9.7, rdsproxyadmin becomes a reserved user on all hosts and must be absent before you upgrade. If RDS Proxy is attached, it creates and manages this user, so leave it in place.
  2. Confirm your deployment type is supported. Multi-AZ DB clusters (two readable standbys) aren’t supported at launch and upgrades from an 8.4 Multi-AZ DB cluster are blocked.
  3. Migrate any accounts using mysql_native_password to caching_sha2_password (the plugin is removed as of 9.0) and update client drivers.
  4. Review your application and stored programs for MD5() and SHA1(). These SQL functions aren’t available in RDS for MySQL 9.7. For hashing, use SHA2() (for example, SHA2(col, 256)), which remains available. There is no supported MD5() replacement, so plan application changes where it’s used.
  5. Move password validation from the validate-password plugin to the validate_password component. RDS for MySQL 9.7 provides the component form only: the plugin is replaced by rds.validate_password and the validate_password_* variables are renamed to dot notation, for example validate_password_length becomes validate_password.length. Update automation that references the plugin or the old variable names.
  6. Confirm that applications and drivers connect over SSL/TLS. require_secure_transport now defaults to ON, so non-TLS connections are rejected. Set require_secure_transport=OFF in your parameter group if you must allow them.
  7. Update monitoring and automation that read the semisynchronous replication variables and status. They were renamed from master and slave to source and replica, for example rpl_semi_sync_master_timeout becomes rpl_semi_sync_source_timeout. These parameters are visible but RDS-managed, so you can’t set them yourself.
  8. Remove references to replica_parallel_type and group_replication_allow_local_lower_version_join, which are removed in the 9.x series.
  9. Check for schema objects named with the new reserved keywords EXTERNAL and LIBRARY (reserved as of MySQL 9.7). A reserved word must be quoted with backticks to be used as an identifier, so quote or rename any database, table, or column that uses them. When you create a 9.7 instance, don’t pass EXTERNAL or LIBRARY as the initial database name (--db-name) in the create-db-instance call, because a reserved word isn’t accepted there.
  10. Review explain_format. The default changed from TRADITIONAL to TREE, so update any tooling that parses EXPLAIN output. Note that explain_json_format_version now defaults to 2.
  11. Review innodb_change_buffering. The default changed from none to all.
  12. Review innodb_log_writer_threads. The 8.4 default was always ON. In 9.7 it’s binary-log and CPU aware, so it can default to OFF on smaller instances.
  13. Review binlog_transaction_dependency_history_size. The default increased from 25,000 to 10,000,000 (allowed range up to 100,000,000).
  14. Confirm the RDS for MySQL 9.7 defaults for gtid_mode and enforce_gtid_consistency. Community MySQL changed both to ON in 9.5.0 and RDS manages them through the parameter group.
  15. Consider JSON Duality Views for JSON-relational workloads.
  16. Evaluate the Hypergraph Optimizer for complex, multi-join queries. It’s opt-in through optimizer_switch and disabled by default.
  17. Test thoroughly in a Blue/Green deployment, on the Green environment, before promoting.

Conclusion

In this post, we reviewed the MySQL community versioning model, the new capabilities in MySQL 9.7, key security and replication changes, removed and transitional variables and a recommended upgrade approach using Amazon RDS Blue/Green deployments. We encourage you to test MySQL 9.7’s new features with your workloads. To get started, create or upgrade a database instance on the Amazon RDS console. For more information, see the Amazon RDS for MySQL User Guide.

Sources

 


About the authors

Sabalesh Mahajan

Sabalesh Mahajan

Sabalesh is a Senior Database Engineer at Amazon Web Services, with 19 years of experience in databases. He collaborates closely with the Amazon RDS product teams, contributing his expertise to the development and enhancement of innovative products.

Akshat Nehra

Akshat Nehra

Akshat is a Software Development Engineer on the Amazon RDS for MySQL and MariaDB Engine team at Amazon Web Services, where he mostly works on the data plane. He focuses on delivering new community engine versions, contributing fixes upstream to the MySQL and MariaDB communities and security enhancements, helping make engine upgrades safe, reliable and seamless for customers.

Chelluru V N S S Vidyadhar

Chelluru V N S S Vidyadhar

Chelluru is a Senior Database Engineer at Amazon Web Services with 14 years of experience in open source databases.