I'm running debezium-Mysql:v0.10.0.CR1 to pull changes from MySQL database hosted on ASW RDS. The RDS seem to have internal events which are being written to binlog files as statements even when binlog_format is set to ROW.
The binlog file contains RDS internal events which look like this

# at 11761
#190920 1:08:22 server id 876637055 end_log_pos 11891 CRC32 0x3e31fbb4 Query thread_id=2 exec_time=0 error_code=0
SET TIMESTAMP=1568921902/!/;
DELETE FROM mysql.rds_sysinfo where name = 'innodb_txn_key'
/*!*/;

# at 12109
#190920 1:08:23 server id 876637055 end_log_pos 12279 CRC32 0x30b05503 Query thread_id=2 exec_time=0 error_code=0
SET TIMESTAMP=1568921903/!/;
INSERT INTO mysql.rds_sysinfo(name, value) values ('innodb_txn_key','Thu Sep 19 19:38:23 UTC 2019')
/*!*/;

# at 12451
#190920 1:08:31 server id 876637055 end_log_pos 12636 CRC32 0x43dc80f4 Query thread_id=2 exec_time=0 error_code=0
SET TIMESTAMP=1568921911/!/;
INSERT INTO mysql.rds_heartbeat2(id, value) values (1,1568921911754) ON DUPLICATE KEY UPDATE value = 1568921911754
/*!*/;

These are DML statements which are appearing in binary log file with Query tags. Debezium should skip these statements while processing DDL statements. Attached stack trace logs.