Managed MySQL is generally available

Managed MySQL entered beta on 22 October, enabled one organisation at a time. From today it is available to every organisation on Bahriya. There is no ticket to open and nothing to request: open your organisation in the console, choose MySQL, and create an instance.

What you get

It is MySQL 8.4 LTS, unmodified, running next to your containers. Containers in the same project reach an instance at its handle on port 3306, so your ORM, your migration tool and your client library connect the way they always have.

• Databases and users are configuration. Declare the databases you want and the user that owns each one. The platform creates them, generates every password, keeps them in your vault and keeps the instance matching the list. Databases and users
• A tier for every failure tolerance. Single, replicated with read replicas, or highly available with Group Replication across three or five members. Plans run from 0.5 vCPU / 1 GB to 8 vCPU / 32 GB per node, with 5 to 250 GB of storage that can grow at any time. Tiers and replication
• Backups that cannot be switched off. Daily dumps on a schedule you choose, the binary log shipped every 15 minutes, and point-in-time restore to a new instance, so the original keeps serving traffic while you recover. Backups and point-in-time recovery
• Encryption at rest, with an optional volume encryption add-on and master key rotation that does not disconnect your applications. Encryption at rest
• TLS without certificate chores. Certificates are issued, renewed and applied without a restart, always signed by the same certificate authority, so the CA file your clients saved keeps working. Connecting to MySQL
• Private by default. External access requires TLS and an IP allowlist, and phpMyAdmin runs only for the hours you ask for. External access

New since the beta

Reis and Terraform. Since 31 October, MySQL can be managed from the Reis CLI (1.2.0 and later) and the Terraform provider (0.4.0 and later) as well as the console, so an instance can live in version control beside the containers that use it. MySQL in Reis and Terraform

Every character set and collation. character_set_server and collation_server now accept any character set and collation that MySQL 8.4 supports, not just a short list. The collation must belong to the character set, and the platform checks the pair before anything is deployed, so a mismatch is refused with the setting you need instead of reaching the server:

config:
  character_set_server: latin1
  collation_server: latin1_swedish_ci

Tuning

If you joined the beta

Nothing changes for your instances. They keep running as they are, on the same plans and at the same prices, and you do not need to redeploy anything.

Pricing

MySQL is billed per node for the plan and storage you choose, with backups and the volume encryption add-on billed separately. The passwords and keys the platform keeps in your vault are billed like any vault item. See pricing for the current rates.

Start here

Read the MySQL overview, then create your first instance from the console, with reis mysql:create, or with a bahriya_mysql resource in Terraform. If anything surprises you, open a ticket under Support → Tickets and tell us.