MySQL to Amazon RDS Replication (And Vice Versa) Made Simple

In our two most recent posts on MySQL replication we looked at how to securely replicate from MySQL to Amazon Redshift and Amazon Aurora (and vice versa); and here we look at replication between any native MySQL or MariaDB and Amazon RDS (Relational Database Service). 

Why Replicate From MySQL to Amazon RDS (and Vice-Versa)

A typical scenario requiring replication from MySQL to RDS for instance could be an organization that is using RDS but wants to have a copy of their data stored in their onsite location to avoid vendor lock-in. With IT infrastructures, and database infrastructures, being rather polyglott nowadays, it’s almost a given that organisations would have several different databases running and handling different jobs. This is where replication comes into play.

Tungsten Replicator (AMI) for Amazon RDS

Tungsten replicator includes support for parallel replication, and advanced topologies such as fan-in and multi-primary, and can be used efficiently in cross-site deployments.

It is a great tool when it comes to replication of data with heterogeneous (or homogeneous) data sources as it’s easy to configure and operate.

Tungsten Replicator (AMI) In a Nutshell


  • Primary/Primary (MySQL <> MySQL Only)
  • Fan-in
  • Fan-out
  • See below for Fan-in / Fan-out brief


  • All variants of MySQL supported as either Source or Target (Percona, MariaDB, Community, Enterprise)
  • Also supports Cloud Services as Source or Target:
    • Amazon Aurora/RDS
    • Google Cloud SQL
    • Microsoft Azure

Fan Out

  • Extract once
  • Apply to many
  • Targets can be a mix of any supported target
  • Filtering can be used

Fan In

  • Many Sources into a single target
  • Write to single schema or multiple
  • Target can be any of the supported targets
  • Mix of fan in and fan out

Tungsten Replicator (AMI) lets you replicate your data in real time, filter on the tables and schemas you need, all without putting any extra load on your MySQL server. In addition, schema changes just flow through from MySQL to Amazon RDS, without intervention on your part.

It provides high-performance and improved replication functionality over the native MySQL replication solution and into a range of targets / databases, such as AWS RDS of course… and including all MySQL variants, as well as Amazon Redshift, Amazon Aurora, Oracle, Vertica, Hadoop, ClickHouse, Kafka, MongoDB & PostgreSQL.

In short, it is the most advanced heterogeneous replication solution for MySQL, MariaDB & Percona Server, including Amazon RDS MySQL and Amazon Aurora. It’s available as an AMI and can be accessed via AWS.

First off…

How Replication to Amazon RDS Works

Option 1: Local Install

The extractor reads directly from the MySQL binary logs to extract transactions, even when the DBMS is down. This is the default.

Option 2: Remote Install

The extractor gets MySQL transactional log data remotely via the MySQL Remote Replication protocols, which require the database to be online and available. This is also how we extract from RDS/Aurora in Amazon (as well as for remote databases where direct OS access isn’t available).

Offboard Extract & Apply

How to Get Started With the Tungsten Replicator AMI

Getting started with the 14-Day free trial

Users can try one instance of each type of the AMI for free for 14 days to get them started (AWS infrastructure charges still apply).

Please note that free trials will automatically convert to a paid hourly subscription upon expiration and the following then applies in the case of Aurora targets.

Replicate from AWS Redshift, AWS Aurora, MySQL, MariaDB & Percona Server to Amazon RDS from as little as $0.40/hour

With Tungsten Replicator (AMI) on AWS, users can replicate GB's of data from as little as $60c/hour:

  1. Go to the AWS Marketplace, and search for Tungsten, or click here.
  2. Choose and Subscribe to the Tungsten Replicator for MySQL Source Extraction.
  3. Choose and Subscribe to the target Tungsten Replicator AMI of your choice.
  4. Pay by the hour.
  5. When launched, the host will have all the prerequisites in place and a simple "wizard" runs on first launch and asks the user questions about the source and/or target and then configures it all for them.

Watch the Getting Started Walkthrough

Our colleague Chris Parker recorded this handy walk-through on how to get started with the Tungsten Replicator AMI if you need some tips & tricks.

Extraction and Appliers

Below you’ll find the full listing of extractors and appliers that are available with Tungsten Replicator.

Replication Extraction from Operational Databases

  • MySQL (all versions, on-premises and in the cloud)
  • MariaDB (all versions, on-premises and in the cloud)
  • Percona Server (all versions, on-premises and in the cloud)
  • AWS Aurora
  • Azure MySQL
  • Google Cloud SQL

Available Replication Target Databases

Operational Databases
Popular Analytics Solutions
Other Database Targets
  Incl. MongoDB Atlas  

Do give Tungsten Replicator AMI a try and let us know how you get on or if you have any questions by commenting below!

Related Blogs

Check out our related blogs if you’re (also) working with these databases / platforms:

About the Author

Continuent Team

Continuent, the MySQL Availability Company, since 2004 has provided solutions for continuous operations enabling business-critical MySQL applications to run on a global scale with zero downtime. Continuent provides geo-distributed MySQL high availability on-premises, in hybrid-cloud, and in multi-cloud environments.

Continuent customers are leading SaaS, e-commerce, financial services, gaming and telco companies who rely on MySQL and Continuent to cost-effectively safeguard billions of dollars in annual revenue.

Continuent’s database experts offer the industry's best 24/7 MySQL support services to ensure continuous client operations.

Add new comment