I have created a DB Cluster Parameter group.
Create a parameter group:
aws rds create-db-cluster-parameter-group
--db-cluster-parameter-group-name repl-clstr-param-group
--db-parameter-group-family aurora-mysql5.7
--description "Prod repl cluster parameter group by YA"
Modify binlog_format to ROW:
aws rds modify-db-cluster-parameter-group
--db-cluster-parameter-group-name repl-clstr-param-group
--parameters "ParameterName=binlog_format,ParameterValue=row,ApplyMethod=pending-reboot"
Then assign this DB cluster parameter group to the database cluster.
aws rds modify-db-cluster
--db-cluster-identifier my-db-cluster
--db-cluster-parameter-group-name repl-clstr-param-group --apply-immediately
Then I rebooted cluster, rebooted instances(both writer and reader).
I have tested it initially in a test DB where the replication is working perfectly but the same db cluster parameter group when I assigned and rebooter cluster it did not work for me.
In Production DB
SHOW VARIABLES LIKE 'binlog_format';
binlog_format = ROW
show variables like 'log_bin';
log_bin = OFF** (It is ON in the Test DB)**
repl-clstr-param-group(In Sync)
Anything can be done?
BTW: I have followed the following URL to setup Replication.
https://aws.amazon.com/blogs/database/perform-cross-account-amazon-aurora-mysql-migration-with-minimal-downtime/
As I said, this guideline works perfectly for test database.
And followed the following URL to reboot the clusters after enabling the db cluster parameter group.
https://repost.aws/knowledge-center/enable-binary-logging-aurora