content_image/765064.jpg
A Component_status  value of Active  indicates that the component initialized successfully. 

If the component cannot be loaded, server startup fails. Check the server error log for diagnostic messages. If the component loads but fails to initialize due to configuration problems, the server starts but the Component_status  value is Disabled . Check the server error log, correct the configuration issues, and use the ALTER INSTANCE RELOAD KEYRING  statement to reload the configuration. 

Keyring components should be loaded only by using a manifest file, not by using the INSTALL COMPONENT  statement. Keyring components loaded using that statement may be available too late in the server startup sequence for certain components that use the keyring, such as InnoDB , because they are registered in the mysql.component  system table and loaded automatically for subsequent server restarts. But mysql.component  is an InnoDB  table, so any components named in it can be loaded during startup only after InnoDB  initialization. 

If no keyring component or plugin is available when a component tries to access the keyring service, the service cannot be used by that component. As a result, the component may fail to initialize or may initialize with limited functionality. For example, if InnoDB  finds that there are encrypted tablespaces when it initializes, it attempts to access the keyring. If the keyring is unavailable, InnoDB  can access only unencrypted tablespaces. 

## 6.4.4.3 Keyring Plugin Installation 

Keyring service consumers require that a keyring component or plugin be installed: 

•To use a keyring plugin, begin with the instructions here. (Also, for general information about installing plugins, see Section 5.6.1, “Installing and Uninstalling Plugins” .) 

•To use a keyring component instead, begin with Section 6.4.4.2, “Keyring Component Installation” . 

•If you intend to use keyring functions in conjunction with the chosen keyring component or plugin, install the functions after installing that component or plugin, using the instructions in Section 6.4.4.14, “General-Purpose Keyring Key-Management Functions” . 

<img src='content_image/765064.jpg'>

MySQL provides these keyring plugin choices: 

## Note 

Only one keyring component or plugin should be enabled at a time. Enabling multiple keyring components or plugins is unsupported and results may not be as anticipated. 

• keyring_file : Stores keyring data in a file local to the server host. Available in MySQL Community Edition and MySQL Enterprise Edition distributions. 

• keyring_encrypted_file : Stores keyring data in an encrypted, password-protected file local to the server host. Available in MySQL Enterprise Edition distributions. 

• keyring_okv : A KMIP 1.1 plugin for use with KMIP-compatible back end keyring storage products such as Oracle Key Vault and Gemalto SafeNet KeySecure Appliance. Available in MySQL Enterprise Edition distributions. 

• keyring_aws : Communicates with the Amazon Web Services Key Management Service as a back end for key generation and uses a local file for key storage. Available in MySQL Enterprise Edition distributions. 

• keyring_hashicorp : Communicates with HashiCorp Vault for back end storage. Available in MySQL Enterprise Edition distributions. 

