Encrypting the System Tablespace

Percona Server for MySQL supports system tablespace encryption. The InnoDB system tablespace may be encrypted with the master key encryption or the keyring encryption with advanced encryption key rotation.

Keyring encryption is a tech preview feature.

The limitation is the following:

  • You cannot convert the system tablespace from the encrypted state to the unencrypted state, or the unencrypted state to the encrypted state. If a conversion is needed, create a new instance with the system tablespace in the required state and transfer the user tables to that instance.


A server instance initialized with the encrypted InnoDB system tablespace cannot be downgraded. It is not possible to parse encrypted InnoDB system tablespace pages in a version of Percona Server for MySQL lower than the version where the InnoDB system tablespace has been encrypted.

To enable system tablespace encryption, edit the my.cnf file with the following:

System tablespace encryption can only be enabled with the --initialize option

You can create an encrypted table as follows:

mysql> CREATE TABLE table_name TABLESPACE=innodb_system ENCRYPTION='Y';

System Variables

variable innodb_sys_tablespace_encrypt
Command Line:--innodb-sys-tablespace-encrypt
Variable Type:Boolean
Default Value:OFF

Enables the encryption of the InnoDB system tablespace.

Re-Encrypt the System Tablespace

You can re-encrypt the system tablespace key with master key rotation. When the master key is rotated, the tablespace key is decrypted and re-encrypt with the new master key. Only the first page of the tablespace (.ibd) file is read and written during the key rotation. The tables in the tablespace are not re-encrypted.

The command is as follows:


Contact Us

For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or professional services, contact Percona Sales.