Learn about running secure, Managed MySQL Databases on Aptible
Version | Status | End-Of-Life Date | Deprecation Date |
---|---|---|---|
8.0 | Available | April 2026 | August 2026 |
8.4 | Available | April 2029 | August 2029 |
DEPRECATED
on the deprecation date listed above. While existing databases will not be affected, we recommend end-of-life databases to be upgraded. The latest version offered on Aptible will always be available for provisioning, regardless of end-of-life date.mysql
command line client, add this option: --ssl-cipher=DHE-RSA-AES256-SHA
.aptible db:tunnel
), you’ll need to set useSSL
to true
and verifyServerCertificate
to false
in the Advanced settings tab for the data source.verify-identity
, or your client’s equivalent option. The relevant documentation for the MySQL command line utility is here.
By default, MySQL Databases on Aptible use a server certificate signed by Aptible for SSL / TLS termination. Databases that have been running since prior to Jan 15th, 2021, will only have a self-signed certificate. See Database Encryption in Transit for more details.
aptible-nossl
user. As the name implies, this user does not require SSL to connect.
root
root
to your MySQL database. The password for root
is the same as that of the aptible
user.
root
, then using SQL to create the database:
aptible db:replicate
command.
STOP REPLICA IO_THREAD
SHOW PROCESSLIST
until you see Has read all relay log
in the output.STOP REPLICA
RESET MASTER
sync-binlog = 1
). Committed transactions are therefore guaranteed to be written to disk.
SET GLOBAL
with Aptible MySQL Databases.
Any configuration parameters added using SET GLOBAL
will be discarded if your Database is restarted (e.g. as a result of exceeding Memory Limits, the underlying hardware crashing, or simply as a result of a Database Scaling operation). In this scenario, unless your App automatically detects this condition and uses SET GLOBAL
again, your custom configuration will no longer be present.
However, Aptible Support can accommodate reasonable configuration changes so that they can be persisted across restarts (by adding them to a configuration file). If you’re contemplating using SET GLOBAL
(for enabling the General Query Log as an example), please get in touch with Aptible Support to apply the setting persistently.
MySQL Databases on Aptible autotune their buffer pool and chunk size based on the size of their container to improve performance. The innodb_buffer_pool_size
setting will be set to half of the container memory, and innodb_buffer_pool_chunk_size
and innodb_buffer_pool_instances
will be set to approriate values. You can view all buffer pool settings, including these autotuned values, with the following query: SHOW VARIABLES LIKE 'innodb_buffer_pool_%'
.
TLSv1.2
, TLSv1.3