Sovereign migration — support on quote

Migrate AWS RDS to sovereign MariaDB in France

Progressive exit from AWS RDS to a MariaDB hosted in France by RDEM Systems. Full support: inventory, target sizing, real-time replication, short cutover, controlled RDS decommissioning. End of CLOUD Act exposure, end of à-la-carte billing.

Request a quote 15-min scoping

Why leave AWS RDS

RDS is a great service to start fast. At scale, it becomes a cost trap and a sovereignty blind spot. Fragmented billing (CPU + RAM + storage + IOPS + snapshots + egress), unpredictable bill month after month, and data subject to US law regardless of the datacenter location.

For sensitive databases (healthcare, finance, public sector, personal data), hosting in France with a French operator is no longer a preference — it's a compliance and continuity question.

RDEM Systems operates your MariaDB databases on its own network infrastructure (AS206014), in Equinix datacenters in the Paris region. No American intermediary, no transatlantic transfer, no standard contractual clauses to justify.

Example as of October 6, 2026, Paris region: our Standard M plan (16 GB RAM, 4 vCPU, 100 GB, replication across 2 datacenters and backup) costs €275/month excl. VAT. The AWS RDS equivalent (db.m6g.xlarge Multi-AZ, 100 GB gp3) costs about $540/month on demand, $383 with a 1-year reservation and $258 with a 3-year reservation paid upfront (AWS pricing as of October 6, 2026, excluding taxes and outbound traffic). With a long commitment, the prices converge. The difference then lies in what these figures leave out: no 3-year prepaid commitment with us, no separate billing for outbound traffic (fair use) or IOPS, and a French operator.

The 4 most frequent reasons

Beyond sovereignty, here's what makes RDS → MariaDB migration pay off.

Exit CLOUD Act and FISA 702

RDS instances are operated by AWS, an American company subject to US extraterritorial laws — even when hosted in eu-west-3 (Paris). Moving to a French operator removes that exposure.

Predictable, all-inclusive cost

RDS bills CPU, RAM, storage, IOPS, snapshots, backups, cross-AZ traffic and data egress separately. A managed MariaDB at RDEM is billed monthly, all-inclusive (outbound traffic under fair use).

No more vendor lock-in

RDS hides the engine: no SUPER privilege, limited configuration, proprietary backup format. MariaDB on RDEM gives you root-level operations and standard SQL backups.

Real French hosting

Equinix datacenters in the Paris region, on our own BGP network AS206014. Backups stored in France too. Direct contact with the team in France.

Compatibility by source RDS engine

All "MySQL-like" RDS engines can be migrated to MariaDB. The details matter.

RDS MySQL 5.7 / 8.0

Direct migration via logical replication. Schema and queries transferred without modification in 95% of cases.

RDS MariaDB

Simplest migration — same engine, just a change of operator and network.

Aurora MySQL

Migration through binlog replication from Aurora (binary log to enable in the cluster parameter group), or through a dump.

Aurora Serverless

Migratable. We move to a capacity-sized MariaDB matched to your real observed load profile (often a downward surprise on cost).

How the migration unfolds

RDS inventory & audit

Engines (MySQL, MariaDB, Aurora), versions, sizing, parameter groups, automated backups, read replicas, security groups, KMS keys.

Target sizing

We translate your RDS instance class into MariaDB on RDEM (Standard 2 DC or Galera 3 DC), including realistic IOPS sizing and replication topology.

Replication-based migration

We replicate RDS → MariaDB in real time over a secure tunnel. Cutover happens during a short window once the replication lag is zero.

Cleanup & decommission

Post-cutover validation, RDS billing freeze, automated snapshot export to your cold storage, then RDS instance deletion under your control.

Risks and how we neutralize them

Risk #1: replication bandwidth. Getting data out of RDS to an external site consumes paid AWS egress. On databases > 1 TB, we plan during off-peak hours and size the window. Egress cost estimated upfront, no surprises.

Risk #2: inherited RDS parameters. Many teams don't know exactly what's in their parameter group. We audit it and reproduce the useful parameters on the MariaDB side — without duplicating RDS-specific workarounds.

Risk #3: rollback. For 7 to 14 days post-cutover, a standby MySQL instance is kept (on our side, not on AWS). The rollback scenario (reverse replication when the versions allow it, otherwise replaying the writes) is defined during the audit. Some cases rule it out: the audit then flags it before cutover.

Pricing

The migration is a fixed-price engagement on quote. Price depends on the source engine (MySQL, MariaDB, Aurora), data volume, number of databases, and target cutover window.

The initial 15-min scoping call is free. For complex architectures (multi-AZ, read replicas, Aurora cluster), an upfront audit (1 to 3 days at €1,200 excl. VAT/day, see audit page) accurately scopes the migration and surfaces RDS-specific pitfalls.

The audit cost is deductible from the migration. Total cost is typically amortized in 6 to 18 months through AWS bill savings.

Ready to exit AWS RDS?

Let's scope your migration in 15 minutes. RDS inventory and quote within 48h.