Aurora MySQL configuration parameters
You manage your Amazon Aurora MySQL DB cluster in the same way that you manage other Amazon RDS DB instances, by using parameters in a DB parameter group. Amazon Aurora differs from other DB engines in that you have a DB cluster that contains multiple DB instances. As a result, some of the parameters that you use to manage your Aurora MySQL DB cluster apply to the entire cluster. Other parameters apply only to a particular DB instance in the DB cluster.
To manage cluster-level parameters, use DB cluster parameter groups. To manage instance-level parameters, use DB parameter groups. Each DB instance in an Aurora MySQL DB cluster is compatible with the MySQL database engine. However, you apply some of the MySQL database engine parameters at the cluster level, and you manage these parameters using DB cluster parameter groups. You can't find cluster-level parameters in the DB parameter group for an instance in an Aurora DB cluster. A list of cluster-level parameters appears later in this topic.
You can manage both cluster-level and instance-level parameters using the Amazon Web Services Management Console, the Amazon CLI, or the Amazon RDS API. You use separate commands for managing cluster-level parameters and instance-level parameters. For example, you can use the modify-db-cluster-parameter-group CLI command to manage cluster-level parameters in a DB cluster parameter group. You can use the modify-db-parameter-group CLI command to manage instance-level parameters in a DB parameter group for a DB instance in a DB cluster.
You can view both cluster-level and instance-level parameters in the console, or by using the CLI or RDS API. For example, you can use the describe-db-cluster-parameters Amazon CLI command to view cluster-level parameters in a DB cluster parameter group. You can use the describe-db-parameters CLI command to view instance-level parameters in a DB parameter group for a DB instance in a DB cluster.
Each default parameter group contains the default values for all parameters in the parameter group. If the parameter has "engine default" for this value, see the version-specific MySQL or PostgreSQL documentation for the actual default value.
For more information about DB parameter groups, see Working with parameter groups. For rules and restrictions for Aurora Serverless v1 clusters, see Parameter groups for Aurora Serverless v1.
Topics
Cluster-level parameters
The following table shows all of the parameters that apply to the entire Aurora MySQL DB cluster.
Parameter name | Modifiable | Notes |
---|---|---|
|
Yes |
Only affects clusters that use binary log (binlog) replication. For information about binlog replication, see Replication between Aurora and MySQL or between Aurora and another Aurora DB cluster (binary log replication). Removed from Aurora MySQL version 3. |
|
Yes |
Only affects clusters that use binary log (binlog) replication. For information about binlog replication, see Replication between Aurora and MySQL or between Aurora and another Aurora DB cluster (binary log replication). |
|
Yes |
Only affects clusters that use binary log (binlog) replication. For information about binlog replication, see Replication between Aurora and MySQL or between Aurora and another Aurora DB cluster (binary log replication). Removed from Aurora MySQL version 3. |
|
Yes |
Set this parameter to |
|
Yes |
For more information, see Performance considerations for Amazon Aurora MySQL replication. Doesn't apply to clusters that are part of an Aurora global database. Removed from Aurora MySQL version 3. |
|
Yes |
For more information, see Performance considerations for Amazon Aurora MySQL replication. Doesn't apply to clusters that are part of an Aurora global database. Removed from Aurora MySQL version 3. |
|
Yes |
This setting is available in Aurora MySQL version 3, but it isn't used. |
|
Yes |
This setting is turned on by default in Aurora MySQL 2.10 and higher. For more information, see Zero-downtime restart (ZDR) for Amazon Aurora MySQL. |
|
Yes |
For more information, see Loading data into an Amazon Aurora MySQL DB cluster from
text files in an Amazon S3 bucket. Currently not available in Aurora MySQL version
3. Use |
|
Yes |
This setting is turned on by default in Aurora MySQL 2.11 and higher. Use this setting to mask Aurora MySQL password hashes in the general, slow query, and audit logs. The
allowed values are |
|
Yes |
For more information, see Saving data from an Amazon Aurora MySQL DB cluster into text files in an Amazon S3
bucket. Currently not available in Aurora MySQL version
3. Use |
|
Yes |
|
|
Yes |
|
|
Yes |
For more information, see Invoking a Lambda function from an Amazon Aurora MySQL DB cluster. |
|
Yes |
Used when invoking the In Aurora MySQL version 2, the IAM role specified in
this parameter is used if an IAM role isn't specified for
In Aurora MySQL version 3, the IAM role specified for this parameter is always used. For more information, see Associating an IAM role with an Amazon Aurora MySQL DB cluster. |
|
Yes |
The Amazon CLI and RDS API report a value of |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
For more information, see Replication between Aurora and MySQL or between Aurora and another Aurora DB cluster (binary log replication). |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
No |
|
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL clusters use the InnoDB storage engine for all of your data. |
|
Sometimes |
Modifiable in Aurora MySQL version 2 and higher. |
|
Yes |
Indicates the status of the Event Scheduler. Modifiable only at the cluster level in Aurora MySQL version 3. |
|
Sometimes |
Modifiable in Aurora MySQL version 2 and higher. |
|
Yes |
The command to be run by the server for each client that connects. Use double quotes (") for settings to avoid connection failures, for example:
In Aurora MySQL version 3, this parameter doesn't apply for users who have the
|
|
Yes |
|
|
No |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
Yes |
This option is used to disable deadlock detection on Aurora MySQL version 3. On high-concurrency systems, deadlock detection can cause a slowdown when numerous threads wait for the same lock. Consult the MySQL documentation for more information on this parameter. |
|
Yes |
This parameter defines the default row format for InnoDB tables (including user-created InnoDB temporary tables). It applies to Aurora MySQL versions 2 and 3. Its value can be |
|
Yes |
This parameter affects how table storage is organized. For more information, see Storage scaling. |
|
Aurora MySQL version 2: Yes Aurora MySQL version 3: No |
For Aurora MySQL version 2, we highly recommend that you use the default value of For Aurora MySQL version 3, Aurora always uses the default value
of For more information, see Configuring how frequently the log buffer is flushed. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
|
|
Yes |
When turned on, records information about all InnoDB deadlocks in the Aurora MySQL error log. For more information, see Minimizing and troubleshooting Aurora MySQL deadlocks. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
Yes |
Removed from Aurora MySQL version 3. |
|
No |
Removed from Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 2. Allowed values are |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
Key cache for MyISAM tables. For more information, see keycache->cache_lock mutex. |
|
Yes |
|
|
Yes (Aurora MySQL version 2) Only at cluster creation time (Aurora MySQL version 3) |
In Aurora MySQL version 2.10 and higher 2.x versions, make sure to reboot all reader instances after changing this setting and rebooting the writer instance. For details, see Rebooting an Aurora MySQL cluster (version 2.10 and higher). In Aurora MySQL version 3, the value of this parameter is set permanently at the time the cluster is created. If you use a nondefault value for this option, set up your Aurora MySQL version 3 custom parameter group before upgrading, and specify the parameter group during the snapshot restore operation that creates the version 3 cluster. With an Aurora global database based on Aurora MySQL, you can't perform an in-place upgrade from
Aurora MySQL version 2 to version 3 if the |
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
Aurora MySQL version 2. Use |
|
No |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
When this parameter is turned on, the server permits no updates except from those performed by replica threads. In Aurora MySQL version 3, this parameter doesn't apply for users who have the
|
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 2 and 3. For more information, see Using SSL/TLS with Aurora MySQL DB clusters. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
For instructions on uploading the logs to Amazon CloudWatch Logs, see Publishing Amazon Aurora MySQL logs to Amazon CloudWatch Logs. |
|
No |
|
|
Yes |
|
|
No |
|
|
Yes |
Only applies to Aurora MySQL version 2 clusters, with MySQL 5.7 compatibility. |
|
Yes |
Aurora MySQL version 3 |
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
For more information, see TLS versions for Aurora MySQL. |
Instance-level parameters
The following table shows all of the parameters that apply to a specific DB instance in an Aurora MySQL DB cluster.
Parameter name | Modifiable | Notes |
---|---|---|
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
No |
|
|
Yes |
Set this parameter to |
|
Yes |
For more information, see Amazon Aurora MySQL lab mode. Removed from Aurora MySQL version 3. |
|
Yes |
This parameter is supported for Aurora MySQL version 2. It isn't supported for version 3. For more information, see Amazon Aurora MySQL out-of-memory issues . |
|
Yes |
Set to |
|
Yes |
Set to |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
No |
This parameter applies to Aurora MySQL version 3. |
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Sometimes |
Indicates the status of the Event Scheduler. Modifiable only at the cluster level in Aurora MySQL version 3. |
|
Yes |
|
|
No |
|
|
Yes |
|
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
For instructions on uploading the logs to CloudWatch Logs, see Publishing Amazon Aurora MySQL logs to Amazon CloudWatch Logs. |
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
Yes |
|
|
Yes |
|
|
Yes |
The command to be run by the server for each client that connects. Use double quotes (") for settings to avoid connection failures, for example:
In Aurora MySQL version 3, this parameter doesn't apply for
users who have the |
|
Yes |
|
|
Yes |
Modifying this parameter has no effect because
|
|
Yes |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
Yes |
The default value is represented by a formula. For details about how the
|
|
No |
Aurora MySQL doesn't use the InnoDB change buffer at all. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Modifying this parameter has no effect, because |
|
Yes |
This option is used to disable deadlock detection on Aurora MySQL version 3. On high-concurrency systems, deadlock detection can cause a slowdown when numerous threads wait for the same lock. Consult the MySQL documentation for more information on this parameter. |
|
Yes |
Removed from Aurora MySQL version 3. |
|
No |
|
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
When turned on, records information about all InnoDB deadlocks in the Aurora MySQL error log. For more information, see Minimizing and troubleshooting Aurora MySQL deadlocks. |
|
Yes |
|
|
Yes |
|
|
No |
|
|
No |
Aurora MySQL manages the read-only and read/write state of DB instances based on the type of cluster. For example, a provisioned cluster has one read/write DB instance (the primary instance) and any other instances in the cluster are read-only (the Aurora Replicas). |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
|
|
Yes |
Modifying this parameter has no effect because
|
|
Yes |
Aurora evaluates the minimum value of |
|
Yes |
This parameter applies to Aurora MySQL version 2. Allowed values are |
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
Key cache for MyISAM tables. For more information, see keycache->cache_lock mutex. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
Setting |
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
No |
|
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL version 2. Use |
|
No |
Aurora MySQL version 3 |
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
The default value is represented by a formula. For details about how the
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
For information about Aurora MySQL features that use this switch, see Best practices with Amazon Aurora MySQL. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2 only |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
|
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
No |
Aurora MySQL manages the connection properties and enforces consistent settings for all DB instances in a cluster. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
The default value is represented by a formula. For details about how the
Removed from Aurora MySQL version 3. |
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
When this parameter is turned on, the server permits no updates except from those performed by replica threads. Removed at the instance level from Aurora MySQL version 3. |
|
Yes |
|
|
No |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
No |
|
|
Yes |
Aurora MySQL version 3 |
|
Yes |
Aurora MySQL version 3 |
|
Yes |
Aurora MySQL version 3 |
|
Yes |
Aurora MySQL version 3 |
|
Yes |
Aurora MySQL version 3 |
|
Yes |
Aurora MySQL version 3 |
|
Yes |
|
|
Yes |
This parameter is always turned on in Aurora MySQL version 2. Trying to turn it off generates an error. Removed from Aurora MySQL version 3. |
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
No |
|
|
No |
|
|
Yes |
|
|
Yes |
Aurora MySQL version 2. Use |
|
Yes |
Aurora MySQL version 2. Use |
|
Yes |
Aurora MySQL version 2. Use |
|
Yes |
Aurora MySQL version 2. Use |
|
Yes |
Aurora MySQL version 2. Use |
|
Yes |
|
|
Yes |
For instructions on uploading the logs to CloudWatch Logs, see Publishing Amazon Aurora MySQL logs to Amazon CloudWatch Logs. |
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
|
|
Yes |
|
|
Yes |
This parameter applies to Aurora MySQL version 3. |
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
|
|
Yes |
|
|
No |
|
|
Yes |
The default value is represented by a formula. For details about how the
|
|
Yes |
The default value is represented by a formula. For details about how the
|
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. For details, see New temporary table behavior in Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. For details, see New temporary table behavior in Aurora MySQL version 3. |
|
Yes |
This parameter applies to Aurora MySQL version 3. For details, see New temporary table behavior in Aurora MySQL version 3. |
|
No |
|
|
Yes |
|
|
Yes |
|
|
Yes |
|
|
No |
Aurora MySQL uses managed instances where you don't access the file system directly. |
|
Yes |
|
|
Yes |
This parameter applies to Aurora MySQL version 3. It replaces |
|
Yes |
|
|
Yes |
Removed from Aurora MySQL version 3. It is replaced by |
|
Yes |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
No |
|
|
Yes |
Aurora evaluates the minimum value of |
MySQL parameters that don't apply to Aurora MySQL
Because of architectural differences between Aurora MySQL and MySQL, some MySQL parameters don't apply to Aurora MySQL.
The following MySQL parameters don't apply to Aurora MySQL. This list isn't exhaustive.
-
activate_all_roles_on_login
– This parameter doesn't apply to Aurora MySQL version 2. It is available in Aurora MySQL version 3. -
big_tables
-
bind_address
-
character_sets_dir
-
innodb_adaptive_flushing
-
innodb_adaptive_flushing_lwm
-
innodb_buffer_pool_chunk_size
-
innodb_buffer_pool_instances
-
innodb_change_buffering
-
innodb_checksum_algorithm
-
innodb_data_file_path
-
innodb_deadlock_detect
– This parameter doesn't apply to Aurora MySQL version 2. It is available in Aurora MySQL version 3. -
innodb_dedicated_server
-
innodb_doublewrite
-
innodb_flush_log_at_timeout
– This parameter doesn't apply to Aurora MySQL. For more information, see Configuring how frequently the log buffer is flushed. -
innodb_flush_method
-
innodb_flush_neighbors
-
innodb_io_capacity
-
innodb_io_capacity_max
-
innodb_log_buffer_size
-
innodb_log_file_size
-
innodb_log_files_in_group
-
innodb_log_spin_cpu_abs_lwm
-
innodb_log_spin_cpu_pct_hwm
-
innodb_max_dirty_pages_pct
-
innodb_numa_interleave
-
innodb_page_size
-
innodb_redo_log_capacity
-
innodb_redo_log_encrypt
-
innodb_undo_log_encrypt
-
innodb_undo_log_truncate
-
innodb_use_native_aio
-
innodb_write_io_threads
-
thread_cache_size
MySQL status variables that don't apply to Aurora MySQL
Because of architectural differences between Aurora MySQL and MySQL, some MySQL status variables don't apply to Aurora MySQL.
The following MySQL status variables don't apply to Aurora MySQL. This list isn't exhaustive.
-
innodb_buffer_pool_bytes_dirty
-
innodb_buffer_pool_pages_dirty
-
innodb_buffer_pool_pages_flushed
Aurora MySQL version 3 removes the following status variables that were in Aurora MySQL version 2:
-
AuroraDb_lockmgr_bitmaps0_in_use
-
AuroraDb_lockmgr_bitmaps1_in_use
-
AuroraDb_lockmgr_bitmaps_mem_used
-
AuroraDb_thread_deadlocks
-
available_alter_table_log_entries
-
Aurora_lockmgr_memory_used
-
Aurora_missing_history_on_replica_incidents
-
Aurora_new_lock_manager_lock_release_cnt
-
Aurora_new_lock_manager_lock_release_total_duration_micro
-
Aurora_new_lock_manager_lock_timeout_cnt
-
Aurora_oom_response
-
Aurora_total_op_memory
-
Aurora_total_op_temp_space
-
Aurora_used_alter_table_log_entries
-
Aurora_using_new_lock_manager
-
Aurora_volume_bytes_allocated
-
Aurora_volume_bytes_left_extent
-
Aurora_volume_bytes_left_total
-
Com_alter_db_upgrade
-
Compression
-
External_threads_connected
-
Innodb_available_undo_logs
-
Last_query_cost
-
Last_query_partial_plans
-
Slave_heartbeat_period
-
Slave_last_heartbeat
-
Slave_received_heartbeats
-
Slave_retried_transactions
-
Slave_running
-
Time_since_zero_connections
These MySQL status variables are available in Aurora MySQL version 2, but they aren't available in Aurora MySQL version 3:
-
Innodb_redo_log_enabled
-
Innodb_undo_tablespaces_total
-
Innodb_undo_tablespaces_implicit
-
Innodb_undo_tablespaces_explicit
-
Innodb_undo_tablespaces_active