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 may use keyring encryption with encryption threads.
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, you should 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:
- Add the
- Edit the innodb_sys_tablespace_encrypt value to “ON”
System tablespace encryption can only be enabled with the
You can create an encrypted table as follows:
mysql> CREATE TABLE table_name TABLESPACE=innodb_system ENCRYPTION='Y';
Dynamic: No Scope: Global Variable Type: Boolean Default Value:
Enables the encryption of the InnoDB system tablespace.
MySQL Documentation: mysql system Tablespace Encryption https://dev.mysql.com/doc/refman/8.0/en/innodb-data-encryption.html#innodb-mysql-tablespace-encryption-enabling-disabling
- MySQL Documentation:
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-encrypte 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:
mysql> ALTER INSTANCE ROTATE INNODB MASTER KEY;