The MySQL Keyring the MySQL server. If the manifest file is found during startup to be read/write to that account, the server writes a warning to the error log suggesting that the file be made read only. Given the preceding manifest file properties, to configure the server to load  component_keyring_file , create a global manifest file named  mysqld.my  in the  mysqld  installation directory, and optionally create a local manifest file, also named  mysqld.my , in the data directory. The following instructions describe how to load  component_keyring_file . To load a different keyring component, substitute its name for component_keyring_file . Create this file in the directory where  mysqld  is installed. Create this file in the directory where  mysqld  is installed. The local file looks like this: Create this file in the data directory. With the manifest in place, proceed to configuring the keyring component. To do this, check the notes for your chosen keyring component for configuration instructions specific to that component: After performing any component-specific configuration, start the server. Verify component installation by examining the Performance Schema  keyring_component_status  table: 1401 mysql>  SELECT * FROM performance_schema.keyring_component_status; +---------------------+-------------------------------------------------+ | STATUS_KEY | STATUS_VALUE | +---------------------+-------------------------------------------------+ | Component_name | component_keyring_file | | Author | Oracle Corporation | | License | GPL | | Implementation_name | component_keyring_file | | Version | 1.0 | | Component_status | Active | | Data_file | /usr/local/mysql/keyring/component_keyring_file | | Read_only | No | +---------------------+-------------------------------------------------+ • component_keyring_encrypted_file : Section 6.4.4.5, “Using the component_keyring_encrypted_file Encrypted File-Based Keyring Component” . • component_keyring_file : Section 6.4.4.4, “Using the component_keyring_file File-Based Keyring Component” . { "read_local_manifest": true } { "components": "file://component_keyring_file" } { "components": "file://component_keyring_file" } •The database administrator has the responsibility for creating any manifest files to be used, and for ensuring that their access mode and contents are correct. If an error occurs, server startup fails and the administrator must correct any issues indicated by diagnostics in the server error log. •To use a global manifest file only, the file contents look like this: •Alternatively, to use a global and local manifest file pair, the global file looks like this: