Managed MySQL

Managed MySQL: AceMQ Runs MySQL and the Move Off 8.0, in Your Cloud or Ours

Last reviewed by Tyler Eastridge

AceMQ runs your MySQL servers for you: monitoring, replication and failover, backups with point-in-time recovery, minor releases and the pager. We work inside your cloud account, data centre or Kubernetes clusters (Tier 3), or on infrastructure AceMQ runs (Tier 4). MySQL 8.0 has been in Oracle Sustaining Support since 21 April 2026, so the move to 8.4 LTS runs as a project inside the service. If Amazon RDS, Aurora or HeatWave suits you better, this page says so.

Support quotes answered within 1 hour, by a senior engineer.

min fastest response target, by plan
15
across Americas, EMEA, APAC
24/7
hour quote response
1
managed tiers: your infrastructure or ours
2

Planning a build, upgrade or migration instead? See AceMQ MySQL consulting and services.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

What's Included

Everything in your MySQL managed services contract

MySQL services under one contract: incident response, query and index tuning, replication and high availability review, schema changes, and consulting on upgrades and migrations between self-managed and managed MySQL database services.

  • 01

    Monitoring and On-Call

    We manage monitoring of what predicts MySQL incidents: replica lag against your batch window, errant GTIDs, binary log retention and disk, Threads_connected against Threads_running, long transactions and deadlocks. Then we take the pager, so an alert reaches an engineer who knows your topology.

  • 02

    Replication, Failover and High Availability

    High availability starts with the topology: source and replica topologies, GTID settings, replica parallelism and semi-synchronous options where you use them, with a failover rehearsal on a schedule and a check for errant transactions that would stop a replica starting after promotion. Group Replication and InnoDB Cluster are in scope where you run them.

  • 03

    Backups and Point-in-Time Recovery

    Full backups with the tool that fits your edition, plus binary logs retained so a restore can stop at a chosen moment. Each is restored into a scratch environment on a schedule and timed against your recovery objectives, because an untested backup is a hope.

  • 04

    Releases and Upgrades

    Minor releases applied on an agreed cadence after a test on a copy, with rollback steps written down. Major upgrades, such as 5.7 to 8.0 to 8.4 LTS, run as projects inside the service, with authentication and replication checks before the window.

  • 05

    Schema Changes and Performance

    Online DDL checked for the algorithm it will really use before it runs, large changes moved to gh-ost or pt-online-schema-change, slow query log and index review, and buffer pool sizing against the working set.

  • 06

    Access and Security Baseline

    Accounts, grants and roles reviewed against least privilege, TLS settings checked, and the build you run tracked against Oracle's quarterly security updates. Access to your environment follows your change process and is logged.

Why AceMQ

Why MySQL teams call AceMQ

  • Your Cloud, Your Kubernetes or Ours

    Run managed MySQL in your own account, data centre or Kubernetes clusters (Tier 3) when residency and compliance keep the data in your boundary, or have AceMQ host it (Tier 4) when you want endpoints and no infrastructure to run. The operator is a MySQL specialist under an AceMQ contract, not a generic hosting provider.

  • One Accountable Partner

    AceMQ holds the contract, the SLA and the escalation path, and brings partner MySQL specialists in as the work needs them. Incidents start with an engineer who has your topology and runbooks in front of them. Response targets from 15 minutes, by plan, are response times, not resolution times.

  • The Application Is in Scope

    Many MySQL incidents start in what the application does: one huge transaction that serialises replica apply, a pool with no maximum, an ALTER that waits behind a long SELECT. We manage the server and also work on queries, transactions and connection behaviour.

  • Runbooks Stay Yours

    Failover, restore and upgrade runbooks, topology documentation and monitoring configuration are maintained as yours. If you bring operations back in-house, or move a server between your infrastructure and ours, there is a current handover pack.

MySQL platforms we cover

Self-managed servers, Percona builds, RDS, Aurora, Azure and Cloud SQL instances, and InnoDB Cluster topologies.

  • Your AWS or Azure account, on virtual machines
  • Virtual machines and bare metal
  • VMware vSphere
  • Kubernetes clusters you run
  • On-premises and air-gapped data centres
  • MySQL Community, Percona Server and MySQL Enterprise Edition builds
  • Source and replica topologies with GTIDs
  • Group Replication and InnoDB Cluster, where you run them
  • Dedicated MySQL hosts operated by AceMQ

Managed MySQL compared

Managed MySQL from AceMQ, Amazon RDS for MySQL, Aurora MySQL or MySQL HeatWave

People who search for a managed MySQL database are often comparing cloud products. They are platforms: the vendor runs the engine and you work inside its limits. AceMQ's managed service is people, who run MySQL on infrastructure you own or on ours. Each row answers one question.

Managed MySQL from AceMQ, Amazon RDS for MySQL, Aurora MySQL or MySQL HeatWave
QuestionAceMQ managed MySQL (Tier 3 or 4)Amazon RDS for MySQLAmazon Aurora MySQLMySQL HeatWave
Who runs itAceMQ engineers with partner MySQL specialists, under a contract with response targets from 15 minutes, by plan.AWS runs the managed instance. You decide when to take a major version upgrade: AWS never makes one automatically.AWS. A MySQL-compatible engine that reuses MySQL code, with its own version numbers, release cycles and deprecation timelines.Oracle's managed MySQL service, with analytics, lakehouse, machine learning and generative AI features.
Where it runsYour cloud account, data centre or Kubernetes (Tier 3), or infrastructure AceMQ runs (Tier 4).AWS.AWS.Oracle Cloud Infrastructure, AWS and Azure, each with its own service guide.
Which engine and versionsMySQL 8.4 LTS, and 8.0 while you move off it. 9.7 LTS is scoped case by case.MySQL Community 8.4 and 8.0, with 8.0 under paid Extended Support since 1 August 2026.Aurora's own version line: check AWS for the dates that apply to yours.Oracle's MySQL, with HeatWave's added features.
Staying on MySQL 8.0We can operate it, but Oracle ships no new fixes for it, so the service plans the move to 8.4 LTS.A fee: Extended Support pricing starts 1 August 2026, steps up on 1 August 2028 and ends 31 July 2029.Follows Aurora's own timelines, not MySQL's.Follows Oracle's terms for the service.
Best whenYou have an existing estate, want data inside your own boundary, run on Kubernetes or on premises, or want one contract across databases and messaging.You are on AWS and want AWS to run a standard MySQL instance.You are on AWS and want Aurora's engine and accept that it is not stock MySQL.You want analytics and machine learning next to your MySQL data in Oracle's service.

Sources: AWS documentation, MySQL on Amazon RDS versions and Amazon Aurora versions; Oracle MySQL HeatWave User Guide; mysql.com EOL notice; all checked 31 October 2026. Vendor terms change, so check them before you commit.

MySQL 8.0 to 8.4 LTS

MySQL 8.0 is in Sustaining Support: what managed MySQL does about it

Oracle's mysql.com notice says that as of 21 April 2026 MySQL 8.0 is covered under Oracle Sustaining Support and encourages users to move to 8.4 LTS or 9.7 LTS. A managed service has to turn that into a plan.

  • The dates

    MySQL 8.4 LTS: Premier Support to April 2029 and Extended Support to April 2032. MySQL 9.7 LTS, released in April 2026: Premier to April 2031 and Extended to April 2034. Oracle's release model gives LTS series five years of Premier and three of Extended Support.

  • The route

    Oracle's release model does not support skipping an LTS series on upgrade, so 5.7 goes through 8.0 and 8.0 goes to 8.4 LTS. From 8.4 the next LTS is 9.7. We plan one hop at a time, each with its own rollback.

  • What breaks at 8.4

    8.4 disables the mysql_native_password plugin by default, so older clients and connectors fail at login, not at startup. It also removes binlog_transaction_dependency_tracking and uses writesets only, which changes how a busy replica applies a large transaction. Both are checked before the window.

  • The upgrade runs inside the service

    Inventory of clients and authentication plugins, a rehearsal on a restored copy, replication checks, a rollback plan and a cutover window agreed with you. The old server stays available until the new one has run a full business cycle.

The dates and your options for 5.7 and 8.0 are set out on the MySQL end-of-life article. MySQL end of life: 5.7, 8.0 and 8.4 dates

Tier 3 and Tier 4

What Tier 3 and Tier 4 mean for MySQL

Tiers 1 and 2 are AceMQ's MySQL support: you hold the pager and we respond and review. Tiers 3 and 4 are managed services: we hold it. The two managed tiers run the same operations. What differs is where MySQL runs and who owns the infrastructure.

  • Tier 3: managed on your infrastructure

    AceMQ operates MySQL in your cloud account, data centre or Kubernetes clusters, with system access and your change process. You keep the account, the data and the infrastructure bill.

  • Tier 4: managed on AceMQ infrastructure

    AceMQ hosts and operates MySQL on infrastructure it runs, with backups, replication and upgrades included. You get connection endpoints, not a server or an on-call rota.

  • Oracle's own support stays separate

    If you hold MySQL Enterprise Edition, Oracle's support entitlement remains yours and remains the source of Oracle fixes for a supported release. AceMQ operates the servers and prepares the Oracle case with the diagnosis done.

  • Starting at Tier 1 or 2 is fine

    Many estates start with support and a review of replication, backups and the 8.0 position, then hand over operations. Nothing about Tier 3 or 4 requires a big-bang handover.

Tiers 1 and 2 are set out on the MySQL support page. MySQL support: 24/7, response targets from 15 minutes, by plan

Choosing honestly

When RDS, Aurora or HeatWave is the better buy

A managed cloud database is the right answer for some workloads. These are the differences that decide it.

  • Choose RDS for MySQL when

    You are on AWS, you run a standard open-source MySQL workload, and you want AWS to run the instance. Plan for the version calendar: 8.0 is now only under paid Extended Support there.

  • Choose Aurora when

    You want Aurora's storage and failover design and accept that it is MySQL-compatible, not MySQL, with its own versions and deprecation dates.

  • Choose HeatWave when

    Analytics, a lakehouse or machine learning over the same data matters as much as the transactional side, and you are comfortable inside Oracle's service.

  • Choose managed MySQL from AceMQ when

    You already run MySQL on virtual machines, on premises or on Kubernetes, need data to stay in your boundary, want to avoid a cloud vendor's version calendar, or want one contract for MySQL, PostgreSQL, Kafka and the rest.

What none of them removes: schema design, query plans and application behaviour still belong to whoever owns the workload.

Price drivers

What drives the price of managed MySQL

AceMQ does not publish a price list for managed services. A managed MySQL quote is built from these inputs, and the written quote returns within 1 hour of your request.

  • Servers, size and write volume

    How many servers and clusters you run, how large they are, how write-heavy, and which are production.

  • Topology and recovery targets

    Single primary, replicas, Group Replication or InnoDB Cluster, and the recovery point and recovery time objectives that set the backup, binary log and failover work.

  • Cover hours

    From business hours to 24/7 on-call with response targets from 15 minutes, by plan.

  • Tier, and a version upgrade

    At Tier 3 you pay your provider for infrastructure and AceMQ for operations. At Tier 4 the infrastructure is in the AceMQ quote. A move from 8.0 to 8.4 LTS, if one is due, is scoped in the quote.

Not a fit for

When managed MySQL from AceMQ is the wrong tool

We would rather say so up front.

  • A pay-as-you-go database console

    AceMQ is a specialist service with a contract and senior engineers. If you want a database you provision by clicking, with no contract, buy it from RDS, Aurora or HeatWave.

  • Moving off MySQL

    A migration to PostgreSQL is a separate AceMQ project, scoped on its own, not part of this service. Once the database is on PostgreSQL we can operate it.

  • Consulting questions

    Architecture reviews, topology assessments and tuning engagements are consulting, not operations. They sit on the MySQL page and can lead into a managed contract.

  • One small, non-critical database

    A scratch database with no uptime target needs a current version and a backup, not a managed service.

Running several engines? One contract can also cover PostgreSQL, SQL Server and more. Managed PostgreSQL services

Escalation Path

Your first hour of a MySQL outage

A primary that stopped accepting writes gets an engineer who has read plenty of InnoDB status output, so diagnosis starts at once.

  1. From 15 min (by plan)first responseEmergencyProduction outage: the primary will not accept writes, replication is broken, or the data volume has filled
  2. 1 hourfirst responseCriticalSerious degradation: replica lag measured in minutes, a Group Replication member lost, connection exhaustion after failover
  3. 4 hoursfirst responseHighGrowing history list length, queries regressing after a load, temporary tables spilling to disk
  4. Next Dayfirst responseStandardIndex and query review, ALTER planning, upgrade steps, backup and restore timing, parameter group advice

Targets depend on plan, so a primary that cannot commit is not treated like an index question.

Prefer a named MySQL engineer who knows your topology? Get a quote or contact us.

Contact Us

Typical engagements

MySQL replication and schema work

MySQL support work from AceMQ. Each card links to the full write-up: the database estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

  • Remediation

    MySQL Replication Lag Remediation

    E-Commerce Marketplace Operator

    Resolving replica lag that grew to hours during batch windows because single-threaded apply could not keep pace with large multi-row transactions.

    MySQLProxySQLPrometheusLinux
  • Support

    MySQL InnoDB Lock Contention Support

    Travel Booking Platform

    Ongoing support for deadlocks and lock wait timeouts under booking concurrency, including history list growth from long-running transactions.

    MySQLProxySQLPrometheusKubernetes
  • Assessment

    CloudStack LTS Upgrade Assessment: Java 17, System VMs and Hypervisor Agents

    Private Cloud Operations Team

    A typical engagement to plan an Apache CloudStack upgrade onto the current LTS line: read every upgrade guide between the running version and the target, check Java 17 on the management servers and KVM agents, and write the order of management servers, hosts and system VMs.

    Apache CloudStackKVMMySQLJava
All use cases

Support options

Four tiers of MySQL support.

AceMQ offers MySQL support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for servers your DBAs run, proactive monitoring that finds replica lag, errant GTIDs and backup gaps first, managed MySQL on your own infrastructure, and fully managed MySQL on AceMQ infrastructure. MySQL 5.7 to 8.4 is supported, and 5.7 and 8.0 can be kept patched through OSSeva.

  • Tier 1

    MySQL 24/7 Support & Incident Management

    Your DBAs run mysqld, we take the hard calls

    Best for: Teams with in-house DBAs who want a senior MySQL engineer for replication failures and unexplained slowdowns.

  • Tier 2

    MySQL 24/7 Support with Proactive Monitoring

    Regular reviews of queries, replicas and backups

    Best for: Teams that want lag, purge backlog and restore time checked on a schedule before they cause an outage.

  • Tier 3

    Managed MySQL on Your Infrastructure

    We administer MySQL on servers you control

    Best for: Businesses that must keep MySQL in their own data center or cloud account but want daily upkeep handled.

  • Tier 4

    Fully Managed MySQL on AceMQ Infrastructure

    AceMQ operates MySQL for you as a service

    Best for: Teams that need a reliable relational backend without hiring and rostering their own DBAs.

FAQ

MySQL managed services questions

Still have questions about MySQL? Email an Expert

Can you manage MySQL in our own cloud account or on Kubernetes?

Yes. Tier 3 runs in your AWS or Azure account, on virtual machines, on VMware, on Kubernetes you run, or on premises including air-gapped sites, using your access controls and change process. AceMQ works with system access and database administrative access, inside that change process and logged. Tier 4 is the alternative when you would rather run no infrastructure. RDS, Aurora and HeatWave are run by their vendors, so Tiers 3 and 4 do not apply to them; ask us about support for the workload around them.

What happens to our MySQL 8.0 servers?

Oracle moved MySQL 8.0 to Sustaining Support on 21 April 2026, so it ships no new fixes for it. AceMQ can operate 8.0 in the meantime, and plans the move to 8.4 LTS as a project inside the service, one hop at a time with a rollback at each step. Oracle's release model does not support skipping an LTS series, so a 5.7 server goes to 8.0 and then 8.4.

Can we engage AceMQ for one MySQL task?

Yes. A major version upgrade, a replication rebuild or a large online schema change can be quoted as its own piece of work. Teams often add an annual agreement afterward, so the engineers who ran the project stay available around the clock for incidents.

How does AceMQ price MySQL support?

Yearly MySQL contracts typically fall between $24,000 and $72,000 (USD). We scope by servers and replicas, cluster style (single primary, InnoDB Cluster or Aurora), how many schema changes and upgrades you expect, and your response plan. Describe the estate in a request and a quote follows within 1 hour.

Let's talk

Hand Over the MySQL Pager. Choose Where MySQL Lives.

Reactive cover, proactive reviews, or AceMQ running MySQL for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.

A senior MySQL engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a MySQL Architect