Inbound replication to MySQL HeatWave Service does not support some of the configurations that are possible for MySQL replication.

• Only row-based replication is supported. This binary log format is the default in MySQL version 5.7 and higher. Statement-based replication and mixed replication are not supported.
• Only asynchronous replication is supported. Semi-synchronous replication is not supported.
• Only replication from a single source is supported. Multi-source replication is not supported.
• Changes to the mysql schema are not replicated and cause replication to stop.
• Using a root@localhost or administrator user in the DEFINER clause of CREATE PROCEDURE and CREATE FUNCTION statements is not supported. Instead, create a dedicated user with the privileges required to run the statements, and then edit the statements with the dedicated user in the DEFINER clause.
• When a high availability DB system is upgraded, the inbound replication channel is suspended. The channel is resumed when the upgrade process is complete.
• Only statements which the applier username has privilege to execute can be replicated. Replication fails if the applier username has insufficient privilege to execute any statement read from the binary logs of the source server. The list of privileges is restricted to the privileges granted to the administrator of the DB system. See Default MySQL Privileges.
• Using GTID tags (introduced in MySQL version 8.3.0) on the source server is not supported. Replicating a transaction with GTID tag breaks inbound replication because DB systems do not support GTID tags.