Aurora MySQL configuration parameters - Amazon Aurora (original) (raw)

activate_all_roles_on_login

Yes

This parameter applies to Aurora MySQL version 3.

allow-suspicious-udfs

None

aurora_disable_hash_join

Yes

Set this parameter to ON to turn off hash join optimization in Aurora MySQL version 2.09 or higher. It isn't supported for version 3. For more information, see Parallel query for Amazon Aurora MySQL.

aurora_lab_mode

Yes

For more information, see Amazon Aurora MySQL lab mode. Removed from Aurora MySQL version 3.

aurora_oom_response

Yes

This parameter is supported for Aurora MySQL versions 2 and 3. For more information, see Troubleshooting out-of-memory issues for Aurora MySQL databases.

aurora_parallel_query

Yes

Set to ON to turn on parallel query in Aurora MySQL version 2.09 or higher. The oldaurora_pq parameter isn't used in these versions. For more information, see Parallel query for Amazon Aurora MySQL.

aurora_pq

Yes

Set to OFF to turn off parallel query for specific DB instances in Aurora MySQL versions before 2.09. In version 2.09 or higher, turn parallel query on and off withaurora_parallel_query instead. For more information, see Parallel query for Amazon Aurora MySQL.

aurora_read_replica_read_committed

Yes

Enables READ COMMITTED isolation level for Aurora Replicas and changes the isolation behavior to reduce purge lag during long-running queries. Enable this setting only if you understand the behavior changes and how they affect your query results. For example, this setting uses less-strict isolation than the MySQL default. When it's enabled, long-running queries might see more than one copy of the same row because Aurora reorganizes the table data while the query is running. For more information, seeAurora MySQL isolation levels.

aurora_tmptable_enable_per_table_limit

Yes

Determines whether the tmp_table_size parameter controls the maximum size of in-memory temporary tables created by the TempTable storage engine in Aurora MySQL version 3.04 and higher.

For more information, see Limiting the size of internal, in-memory temporary tables.

aurora_use_vector_instructions

Yes

When this parameter is enabled, Aurora MySQL uses optimized vector processing instructions provided by modern CPUs to improve performance on I/O-intensive workloads.

This setting is enabled by default in Aurora MySQL version 3.05 and higher.

autocommit

Yes

None

automatic_sp_privileges

Yes

None

back_log

Yes

None

basedir

Aurora MySQL uses managed instances where you don't access the file system directly.

binlog_cache_size

Yes

None

binlog_max_flush_queue_time

Yes

None

binlog_order_commits

Yes

None

binlog_stmt_cache_size

Yes

None

binlog_transaction_compression

Yes

This parameter applies to Aurora MySQL version 3.

binlog_transaction_compression_level_zstd

Yes

This parameter applies to Aurora MySQL version 3.

bulk_insert_buffer_size

Yes

None

concurrent_insert

Yes

None

connect_timeout

Yes

None

core-file

Aurora MySQL uses managed instances where you don't access the file system directly.

datadir

Aurora MySQL uses managed instances where you don't access the file system directly.

default_authentication_plugin

This parameter applies to Aurora MySQL version 3.

default_time_zone

None

default_tmp_storage_engine

Yes

The default storage engine for temporary tables.

default_week_format

Yes

None

delay_key_write

Yes

None

delayed_insert_limit

Yes

None

delayed_insert_timeout

Yes

None

delayed_queue_size

Yes

None

div_precision_increment

Yes

None

end_markers_in_json

Yes

None

eq_range_index_dive_limit

Yes

None

event_scheduler

Sometimes

Indicates the status of the Event Scheduler.

Modifiable only at the cluster level in Aurora MySQL version 3.

explicit_defaults_for_timestamp

Yes

None

flush

None

flush_time

Yes

None

ft_boolean_syntax

None

ft_max_word_len

Yes

None

ft_min_word_len

Yes

None

ft_query_expansion_limit

Yes

None

ft_stopword_file

Yes

None

general_log

Yes

For instructions on uploading the logs to CloudWatch Logs, see Publishing Amazon Aurora MySQL logs to Amazon CloudWatch Logs.

general_log_file

Aurora MySQL uses managed instances where you don't access the file system directly.

group_concat_max_len

Yes

None

host_cache_size

Yes

None

init_connect

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:

SET optimizer_switch="hash_join=off"

In Aurora MySQL version 3, this parameter doesn't apply for users who have the CONNECTION_ADMIN privilege, including the Aurora master user. For more information, see Role-based privilege model.

innodb_adaptive_hash_index

Yes

You can modify this parameter at the DB instance level in Aurora MySQL version 2. It's modifiable only at the DB cluster level in Aurora MySQL version 3.

The Adaptive Hash Index isn't supported on reader DB instances.

innodb_adaptive_max_sleep_delay

Yes

Modifying this parameter has no effect becauseinnodb_thread_concurrency is always 0 for Aurora.

innodb_aurora_max_partitions_for_range

Yes

In some cases where persisted statistics aren't available, you can use this parameter to improve the performance of row count estimations on partitioned tables.

You can set it to a value from 0–8192, where the value determines the number of partitions to check during row count estimation. The default value is 0, which estimates using all of the partitions, consistent with default MySQL behavior.

This parameter is available for Aurora MySQL version 3.03.1 and higher.

innodb_autoextend_increment

Yes

None

innodb_buffer_pool_dump_at_shutdown

None

innodb_buffer_pool_dump_now

None

innodb_buffer_pool_filename

None

innodb_buffer_pool_load_abort

None

innodb_buffer_pool_load_at_startup

None

innodb_buffer_pool_load_now

None

innodb_buffer_pool_size

Yes

The default value is represented by a formula. For details about how theDBInstanceClassMemory value in the formula is calculated, see DB parameter formula variables.

innodb_change_buffer_max_size

Aurora MySQL doesn't use the InnoDB change buffer at all.

innodb_compression_failure_threshold_pct

Yes

None

innodb_compression_level

Yes

None

innodb_compression_pad_pct_max

Yes

None

innodb_concurrency_tickets

Yes

Modifying this parameter has no effect, because innodb_thread_concurrency is always 0 for Aurora.

innodb_deadlock_detect

Yes

This option is used to disable deadlock detection in Aurora MySQL version 2.11 and higher and 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.

innodb_file_format

Yes

Removed from Aurora MySQL version 3.

innodb_flushing_avg_loops

None

innodb_force_load_corrupted

None

innodb_ft_aux_table

Yes

None

innodb_ft_cache_size

Yes

None

innodb_ft_enable_stopword

Yes

None

innodb_ft_server_stopword_table

Yes

None

innodb_ft_user_stopword_table

Yes

None

innodb_large_prefix

Yes

Removed from Aurora MySQL version 3.

innodb_lock_wait_timeout

Yes

None

innodb_log_compressed_pages

None

innodb_lru_scan_depth

Yes

None

innodb_max_purge_lag

Yes

None

innodb_max_purge_lag_delay

Yes

None

innodb_monitor_disable

Yes

None

innodb_monitor_enable

Yes

None

innodb_monitor_reset

Yes

None

innodb_monitor_reset_all

Yes

None

innodb_old_blocks_pct

Yes

None

innodb_old_blocks_time

Yes

None

innodb_open_files

Yes

None

innodb_print_all_deadlocks

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.

innodb_random_read_ahead

Yes

None

innodb_read_ahead_threshold

Yes

None

innodb_read_io_threads

None

innodb_read_only

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).

innodb_replication_delay

Yes

None

innodb_sort_buffer_size

Yes

None

innodb_stats_auto_recalc

Yes

None

innodb_stats_method

Yes

None

innodb_stats_on_metadata

Yes

None

innodb_stats_persistent

Yes

None

innodb_stats_persistent_sample_pages

Yes

None

innodb_stats_transient_sample_pages

Yes

None

innodb_thread_concurrency

None

innodb_thread_sleep_delay

Yes

Modifying this parameter has no effect becauseinnodb_thread_concurrency is always 0 for Aurora.

interactive_timeout

Yes

Aurora evaluates the minimum value of interactive_timeout and wait_timeout. It then uses that minimum as the timeout to end all idle sessions, both interactive and noninteractive.

internal_tmp_disk_storage_engine

Yes

Controls which in-memory storage engine is used for internal temporary tables. Allowed values areINNODB and MYISAM.

This parameter applies to Aurora MySQL version 2.

internal_tmp_mem_storage_engine

Sometimes

Controls which in-memory storage engine is used for internal temporary tables. Allowed values for writer DB instances areMEMORY and TempTable.

For reader DB instances, this parameter is set to TempTable and can't be modified.

This parameter applies to Aurora MySQL version 3.

join_buffer_size

Yes

None

keep_files_on_create

Yes

None

key_buffer_size

Yes

Key cache for MyISAM tables. For more information, see keycache->cache_lock mutex.

key_cache_age_threshold

Yes

None

key_cache_block_size

Yes

None

key_cache_division_limit

Yes

None

local_infile

Yes

None

lock_wait_timeout

Yes

None

log-bin

Setting binlog_format to STATEMENT, MIXED, or ROW automatically sets log-bin to ON. Setting binlog_format toOFF automatically sets log-bin to OFF. For more information, see Replication between Aurora and MySQL or between Aurora and another Aurora DB cluster (binary log replication).

log_bin_trust_function_creators

Yes

None

log_bin_use_v1_row_events

Yes

Removed from Aurora MySQL version 3.

log_error

None

log_error_suppression_list

Yes

Specifies a list of error codes that aren't logged in the MySQL error log. This allows you to ignore certain noncritical error conditions to help keep your error logs clean. For more information, see log_error_suppression_list in the MySQL documentation.

This parameter applies to Aurora MySQL version 3.03 and higher.

log_output

Yes

None

log_queries_not_using_indexes

Yes

None

log_slave_updates

Aurora MySQL version 2. Use log_replica_updates in Aurora MySQL version 3.

log_replica_updates

Aurora MySQL version 3

log_throttle_queries_not_using_indexes

Yes

None

log_warnings

Yes

Removed from Aurora MySQL version 3.

long_query_time

Yes

None

low_priority_updates

Yes

INSERT, UPDATE, DELETE, and LOCK TABLE WRITE operations wait until there's no pending SELECT operation. This parameter affects only storage engines that use only table-level locking (MyISAM, MEMORY, MERGE).

This parameter applies to Aurora MySQL version 3.

max_allowed_packet

Yes

None

max_binlog_cache_size

Yes

None

max_binlog_size

None

max_binlog_stmt_cache_size

Yes

None

max_connect_errors

Yes

None

max_connections

Yes

The default value is represented by a formula. For details about how theDBInstanceClassMemory value in the formula is calculated, see DB parameter formula variables. For the default values depending on the instance class, see Maximum connections to an Aurora MySQL DB instance.

max_delayed_threads

Yes

Sets the maximum number of threads to handle INSERT DELAYED statements.

This parameter applies to Aurora MySQL version 3.

max_error_count

Yes

The maximum number of error, warning, and note messages to be stored for display.

This parameter applies to Aurora MySQL version 3.

max_execution_time

Yes

The timeout for running SELECT statements, in milliseconds. The value can be from0–18446744073709551615. When set to 0, there is no timeout.

For more information, see max_execution_time in the MySQL documentation.

max_heap_table_size

Yes

None

max_insert_delayed_threads

Yes

None

max_join_size

Yes

None

max_length_for_sort_data

Yes

Removed from Aurora MySQL version 3.

max_prepared_stmt_count

Yes

None

max_seeks_for_key

Yes

None

max_sort_length

Yes

None

max_sp_recursion_depth

Yes

None

max_tmp_tables

Yes

Removed from Aurora MySQL version 3.

max_user_connections

Yes

None

max_write_lock_count

Yes

None

metadata_locks_cache_size

Yes

Removed from Aurora MySQL version 3.

min_examined_row_limit

Yes

Use this parameter to prevent queries that examine fewer than the specified number of rows from being logged.

This parameter applies to Aurora MySQL version 3.

myisam_data_pointer_size

Yes

None

myisam_max_sort_file_size

Yes

None

myisam_mmap_size

Yes

None

myisam_sort_buffer_size

Yes

None

myisam_stats_method

Yes

None

myisam_use_mmap

Yes

None

net_buffer_length

Yes

None

net_read_timeout

Yes

None

net_retry_count

Yes

None

net_write_timeout

Yes

None

old-style-user-limits

Yes

None

old_passwords

Yes

Removed from Aurora MySQL version 3.

optimizer_prune_level

Yes

None

optimizer_search_depth

Yes

None

optimizer_switch

Yes

For information about Aurora MySQL features that use this switch, see Best practices with Amazon Aurora MySQL.

optimizer_trace

Yes

None

optimizer_trace_features

Yes

None

optimizer_trace_limit

Yes

None

optimizer_trace_max_mem_size

Yes

None

optimizer_trace_offset

Yes

None

performance-schema-consumer-events-waits-current

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance-schema-consumer-events-waits-current. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance-schema-instrument

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance-schema-instrument. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema

Yes

If the Source column is set to Modified, Performance Insights is managing the Performance Schema. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_accounts_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_accounts_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_global_instrumentation

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_global_instrumentation. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_thread_instrumentation

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_thread_instrumentation. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_stages_current

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_stages_current. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_stages_history

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_stages_history. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_stages_history_long

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_stages_history_long. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_statements_current

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_statements_current. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_statements_history

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_statements_history. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_statements_history_long

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_statements_history_long. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_waits_history

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_waits_history. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_events_waits_history_long

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_events_waits_history_long. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_consumer_statements_digest

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_consumer_statements_digest. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_digests_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_digests_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_stages_history_long_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_stages_history_long_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_stages_history_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_stages_history_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_statements_history_long_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_statements_history_long_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_statements_history_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_statements_history_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_transactions_history_long_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_transactions_history_long_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_transactions_history_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_transactions_history_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_waits_history_long_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_waits_history_long_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_events_waits_history_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_events_waits_history_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_hosts_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_hosts_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_cond_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_cond_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_cond_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_cond_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_digest_length

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_digest_length. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_file_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_file_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_file_handles

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_file_handles. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_file_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_file_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_index_stat

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_index_stat. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_memory_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_memory_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_metadata_locks

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_metadata_locks. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_mutex_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_mutex_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_mutex_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_mutex_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_prepared_statements_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_prepared_statements_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_program_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_program_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_rwlock_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_rwlock_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_rwlock_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_rwlock_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_socket_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_socket_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_socket_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_socket_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_sql_text_length

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_sql_text_length. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_stage_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_stage_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_statement_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_statement_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_statement_stack

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_statement_stack. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_table_handles

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_table_handles. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_table_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_table_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_table_lock_stat

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_table_lock_stat. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_thread_classes

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_thread_classes. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_max_thread_instances

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_max_thread_instances. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_session_connect_attrs_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_session_connect_attrs_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_setup_actors_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_setup_actors_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_setup_objects_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_setup_objects_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_show_processlist

Yes

This parameter determines which SHOW PROCESSLIST implementation to use:

The default implementation iterates across active threads from within the thread manager while holding a global mutex. This can cause slow performance, especially on busy systems.
The alternative SHOW PROCESSLIST implementation is based on the Performance Schema processlist table. This implementation queries active thread data from the Performance Schema rather than the thread manager and doesn't require a mutex.

This parameter applies to Aurora MySQL version 2.12 and higher, and version 3.

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_show_processlist. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

performance_schema_users_size

Yes

If the Source column for the parameter performance_schema is set to Modified, performance schema is using the parameter performance_schema_users_size. For more information about enabling the Performance Schema, see Determining whether Performance Insights is managing the Performance Schema.

pid_file

None

plugin_dir

Aurora MySQL uses managed instances where you don't access the file system directly.

port

Aurora MySQL manages the connection properties and enforces consistent settings for all DB instances in a cluster.

preload_buffer_size

Yes

The size of the buffer that's allocated when preloading indexes.

This parameter applies to Aurora MySQL version 3.

profiling_history_size

Yes

None

query_alloc_block_size

Yes

None

query_cache_limit

Yes

Removed from Aurora MySQL version 3.

query_cache_min_res_unit

Yes

Removed from Aurora MySQL version 3.

query_cache_size

Yes

The default value is represented by a formula. For details about how theDBInstanceClassMemory value in the formula is calculated, see DB parameter formula variables.

Removed from Aurora MySQL version 3.

query_cache_type

Yes

Removed from Aurora MySQL version 3.

query_cache_wlock_invalidate

Yes

Removed from Aurora MySQL version 3.

query_prealloc_size

Yes

None

range_alloc_block_size

Yes

None

read_buffer_size

Yes

None

read_only

Yes

When this parameter is turned on, the server permits no updates except from those performed by replica threads.

For Aurora MySQL version 2, valid values are the following:

0 – OFF
1 – ON
{TrueIfReplica} – ON for read replicas. This is the default value.
{TrueIfClusterReplica} – ON for instances in replica clusters such as cross-Region read replicas, secondary clusters in an Aurora global database, and blue/green deployments.

We recommend that you use the DB cluster parameter group in Aurora MySQL version 2 to make sure that theread_only parameter is applied to new writer instances on failover.

Note

Reader instances are always read only, because Aurora MySQL sets innodb_read_only to1 on all readers. Therefore, read_only is redundant on reader instances.

Removed at the instance level from Aurora MySQL version 3.

read_rnd_buffer_size

Yes

None

relay-log

None

relay_log_info_repository

Yes

Removed from Aurora MySQL version 3.

relay_log_recovery

None

replica_checkpoint_group

Yes

Aurora MySQL version 3

replica_checkpoint_period

Yes

Aurora MySQL version 3

replica_parallel_workers

Yes

Aurora MySQL version 3

replica_pending_jobs_size_max

Yes

Aurora MySQL version 3

replica_skip_errors

Yes

Aurora MySQL version 3

replica_sql_verify_checksum

Yes

Aurora MySQL version 3

safe-user-create

Yes

None

secure_auth

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.

secure_file_priv

Aurora MySQL uses managed instances where you don't access the file system directly.

show_create_table_verbosity

Yes

Enabling this variable causes SHOW_CREATE_TABLE to display the ROW_FORMAT regardless of whether it's the default format.

This parameter applies to Aurora MySQL version 2.12 and higher, and version 3.

skip-slave-start

None

skip_external_locking

None

skip_show_database

Yes

None

slave_checkpoint_group

Yes

Aurora MySQL version 2. Use replica_checkpoint_group in Aurora MySQL version 3.

slave_checkpoint_period

Yes

Aurora MySQL version 2. Use replica_checkpoint_period in Aurora MySQL version 3.

slave_parallel_workers

Yes

Aurora MySQL version 2. Use replica_parallel_workers in Aurora MySQL version 3.

slave_pending_jobs_size_max

Yes

Aurora MySQL version 2. Use replica_pending_jobs_size_max in Aurora MySQL version 3.

slave_sql_verify_checksum

Yes

Aurora MySQL version 2. Use replica_sql_verify_checksum in Aurora MySQL version 3.

slow_launch_time

Yes

None

slow_query_log

Yes

For instructions on uploading the logs to CloudWatch Logs, see Publishing Amazon Aurora MySQL logs to Amazon CloudWatch Logs.

slow_query_log_file

Aurora MySQL uses managed instances where you don't access the file system directly.

socket

None

sort_buffer_size

Yes

None

sql_mode

Yes

None

sql_select_limit

Yes

None

stored_program_cache

Yes

None

sync_binlog

None

sync_master_info

Yes

None

sync_source_info

Yes

This parameter applies to Aurora MySQL version 3.

sync_relay_log

Yes

Removed from Aurora MySQL version 3.

sync_relay_log_info

Yes

None

sysdate-is-now

Yes

None

table_cache_element_entry_ttl

None

table_definition_cache

Yes

The default value is represented by a formula. For details about how theDBInstanceClassMemory value in the formula is calculated, see DB parameter formula variables.

table_open_cache

Yes

The default value is represented by a formula. For details about how theDBInstanceClassMemory value in the formula is calculated, see DB parameter formula variables.

table_open_cache_instances

Yes

None

temp-pool

Yes

Removed from Aurora MySQL version 3.

temptable_max_mmap

Yes

This parameter applies to Aurora MySQL version 3. For details, see New temporary table behavior in Aurora MySQL version 3.

temptable_max_ram

Yes

This parameter applies to Aurora MySQL version 3. For details, see New temporary table behavior in Aurora MySQL version 3.

temptable_use_mmap

Yes

This parameter applies to Aurora MySQL version 3. For details, see New temporary table behavior in Aurora MySQL version 3.

thread_cache_size

Yes

The number of threads to be cached. This parameter applies to Aurora MySQL versions 2 and 3.

thread_handling

None

thread_stack

Yes

None

timed_mutexes

Yes

None

tmp_table_size

Yes

Defines the maximum size of internal in-memory temporary tables created by the MEMORY storage engine in Aurora MySQL version 3.

In Aurora MySQL version 3.04 and higher, defines the maximum size of internal in-memory temporary tables created by the TempTable storage engine whenaurora_tmptable_enable_per_table_limit is ON.

For more information, see Limiting the size of internal, in-memory temporary tables.

tmpdir

Aurora MySQL uses managed instances where you don't access the file system directly.

transaction_alloc_block_size

Yes

None

transaction_isolation

Yes

This parameter applies to Aurora MySQL version 3. It replaces tx_isolation.

transaction_prealloc_size

Yes

None

tx_isolation

Yes

Removed from Aurora MySQL version 3. It is replaced by transaction_isolation.

updatable_views_with_limit

Yes

None

validate-password

None

validate_password_dictionary_file

None

validate_password_length

None

validate_password_mixed_case_count

None

validate_password_number_count

None

validate_password_policy

None

validate_password_special_char_count

None

wait_timeout

Yes

Aurora evaluates the minimum value of interactive_timeout and wait_timeout. It then uses that minimum as the timeout to end all idle sessions, both interactive and noninteractive.