The MySQL Keyring • --keyring-migration-to-component • --keyring-migration-user= user_name • keyring_aws_cmk_id • keyring_aws_conf_file 1449 Command-Line Format --keyring-aws-conf-file=file_name System Variable keyring_aws_conf_file Scope Global Dynamic No Command-Line Format --keyring-aws-cmk-id=value System Variable keyring_aws_cmk_id Scope Global Dynamic Yes SET_VAR  Hint Applies No Type String Command-Line Format --keyring-migration-user=user_name Type String 6.4.4.18 Keyring System Variables The user name of the MySQL account used for connecting to the running server that is currently using one of the key migration keystores. See Section 6.4.4.13, “Migrating Keys Between Keyring Keystores” . For key migration from one keyring component to another, use the  mysql_migrate_keyring utility. Migration from a keyring component to a keyring plugin is not supported. See Section 6.4.4.13, “Migrating Keys Between Keyring Keystores” . Indicates that a key migration is from a keyring plugin to a keyring component. This option makes it possible to migrate keys from any keyring plugin to any keyring component, which facilitates transitioning a MySQL installation from keyring plugins to keyring components. Command-Line Format --keyring-migration-to- component[={OFF|ON}] Introduced 8.0.24 Type Boolean Default Value OFF MySQL Keyring plugins support the following system variables. Use them to configure keyring plugin operation. These variables are unavailable unless the appropriate keyring plugin is installed (see Section 6.4.4.3, “Keyring Plugin Installation” ). The customer master key (CMK) ID obtained from the AWS KMS server and used by the  keyring_aws plugin. This variable is unavailable unless that plugin is installed. This variable is mandatory. If not specified,  keyring_aws  initialization fails.