The MySQL Keyring • keyring_oci : Communicates with Oracle Cloud Infrastructure Vault for back end storage. See Section 6.4.4.11, “Using the Oracle Cloud Infrastructure Vault Keyring Plugin” . To be usable by the server, the plugin library file must be located in the MySQL plugin directory (the directory named by the  plugin_dir  system variable). If necessary, configure the plugin directory location by setting the value of  plugin_dir  at server startup. A keyring component or plugin must be loaded early during the server startup sequence so that other components can access it as necessary during their own initialization. For example, the  InnoDB  storage engine uses the keyring for tablespace encryption, so a keyring component or plugin must be loaded and available prior to  InnoDB  initialization. Installation for each keyring plugin is similar. The following instructions describe how to install keyring_file . To use a different keyring plugin, substitute its name for  keyring_file . The  keyring_file  plugin library file base name is  keyring_file . The file name suffix differs per platform (for example,  .so  for Unix and Unix-like systems,  .dll  for Windows). To load the plugin, use the  --early-plugin-load  option to name the plugin library file that contains it. For example, on platforms where the plugin library file suffix is  .so , use these lines in the server  my.cnf file, adjusting the  .so  suffix for your platform as necessary: [mysqld] early-plugin-load=keyring_file.so Before starting the server, check the notes for your chosen keyring plugin for configuration instructions specific to that plugin: • keyring_file : Section 6.4.4.6, “Using the keyring_file File-Based Keyring Plugin” . • keyring_encrypted_file : Section 6.4.4.7, “Using the keyring_encrypted_file Encrypted File-Based Keyring Plugin” . • keyring_okv : Section 6.4.4.8, “Using the keyring_okv KMIP Plugin” . • keyring_aws : Section 6.4.4.9, “Using the keyring_aws Amazon Web Services Keyring Plugin” • keyring_hashicorp : Section 6.4.4.10, “Using the HashiCorp Vault Keyring Plugin” • keyring_oci : Section 6.4.4.11, “Using the Oracle Cloud Infrastructure Vault Keyring Plugin” After performing any plugin-specific configuration, start the server. Verify plugin installation by examining the  INFORMATION_SCHEMA.PLUGINS  table or use the  SHOW PLUGINS  statement (see Section 5.6.2, “Obtaining Server Plugin Information” ). For example: mysql>  SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE ’keyring%’; +--------------+---------------+ | PLUGIN_NAME | PLUGIN_STATUS | +--------------+---------------+ | keyring_file | ACTIVE | +--------------+---------------+ If the plugin fails to initialize, check the server error log for diagnostic messages. Plugins can be loaded by methods other than  --early-plugin-load , such as the  --plugin-load  or --plugin-load-add  option or the  INSTALL PLUGIN  statement. However, keyring plugins loaded using those methods may be available too late in the server startup sequence for certain components that use the keyring, such as  InnoDB : 1403