The MySQL Keyring Local configuration files permit setting up multiple server instances to use component_keyring_encrypted_file , such that component configuration for each server instance is specific to a given data directory instance. This enables the same keyring component to be used with a distinct data file for each instance. component_keyring_encrypted_file  configuration files have these properties: If the  "read_local_config"  item is present in the global configuration file along with other items, the component checks the  "read_local_config"  item value first: Given the preceding configuration file properties, to configure  component_keyring_encrypted_file create a global configuration file named  component_keyring_encrypted_file.cnf  in the directory where the  component_keyring_encrypted_file  library file is installed, and optionally create a local configuration file, also named  component_keyring_encrypted_file.cnf , in the data directory. The following instructions assume that a keyring data file named  /usr/local/mysql/keyring/ component_keyring_encrypted_file  is to be used in read/write fashion. You must also choose a password. 1407 •Any configuration file that stores a password should have a restrictive mode and be accessible only to the account used to run the MySQL server. •The database administrator has the responsibility for creating any configuration files to be used, and for ensuring that their 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. • "read_only" : The item value indicates whether the keyring data file is read only. The item value is true  (read only) or  false  (read/write). This item is mandatory in the configuration. If not specified, component_keyring_encrypted_file  initialization fails. • "password" : The item value is a string that specifies the password for accessing the data file. This item is mandatory in the configuration. If not specified,  component_keyring_encrypted_file initialization fails. • "path" : The item value is a string that names the file to use for storing keyring data. The file should be named using an absolute path, not a relative path. This item is mandatory in the configuration. If not specified,  component_keyring_encrypted_file  initialization fails. •If the value is  true , the component ignores the other items in the global configuration file and attempts to read the local configuration file. •If the value is  false , the component processes the other items in the global configuration file and ignores the local configuration file. • "read_local_config" : This item is permitted only in the global configuration file. If the item is not present, the component uses only the global configuration file. If the item is present, its value is true  or  false , indicating whether the component should read configuration information from the local configuration file. •A configuration file permits these configuration items: •A configuration file must be in valid JSON format. •It is an error for no confguration file to exist.  component_keyring_encrypted_file  cannot initialize without a valid configuration. •Although global and local configuration files are located in different directories, the file name is component_keyring_encrypted_file.cnf  in both locations.