MySQL HeatWave on AWS  /  Inbound Replication  /  About Inbound Replication

7.1 About Inbound Replication

Inbound replication enables asynchronous replication from a MySQL-based source (an on-premises or other cloud MySQL database instance, or other MySQL HeatWave on AWS DB System) to a MySQL HeatWave on AWS DB System. It uses a replication channel configured in MySQL HeatWave on AWS to copy transactions from the source to a MySQL HeatWave on AWS DB System (replica). The channel connects the source to the replica, and copies data from the source to the replica.

Asynchronous replication means that the replica does not need to be running and connected to the source all the time. It can pick up new updates whenever it is online and reconnects.

A replica DB System can connect to only one MySQL source. The source server does not control the DB System replica and does not need to have permission to write to it. The replica uses the configured replication channel to connect to the source, providing a set of replication user credentials. Over the connection formed by the channel, the replica retrieves committed transactions from the source. Then the replica writes those transactions to its own copy of the databases.


Inbound replication is not a managed functionality. You are responsible for configuring and maintaining the channel, and for ensuring that the traffic between source and replica is properly configured.

Impact of the DB System Operations on the Replication Channel

The DB System operations affect the replication channel:

  • If you stop the DB System, it stops any enabled Channels and changes its state to Needs Attention.
  • If you delete the DB System, it deletes any Channels attached to the DB System.
  • If you restart, upgrade, or update a DB System, it temporarily suspends the Channel while the operation is ongoing. When the operation is complete, replication is resumed. The Channel state changes to Resuming while the channel is being resumed.