Stuck with binary logging error with AWS DMS while using Aurora MySQL? We can help you!

Here, at Bobcares, we often receive similar requests from our customers as a part of our AWS Support Services.

Today, let’s see how our Support engineers resolve these binary logging errors with AWS DMS.

 

Binary logging error with AWS DMS

 
We will receive the following error message if binary logging is not enabled on the source Aurora MySQL DB writer instance while running an AWS DMS task with Aurora MySQL:

Error Code [10001]: Binary logging must be enabled for the MySQL server

I: System var 'log_bin' = 'OFF'

We must enable binary logging on the source Aurora MySQL DB writer instance to use CDC with an AWS DMS task.

Also, make sure to use the writer instance because reader instances are not supported as a source for CDC operations.
 

How to fix binary logging errors

 
Now let’s see how our Support Engineers fix these binary logging errors.

At first, we have to identify the writer instance and then connect the writer instance with AWS DMS.

Then to confirm that binary logging is enabled, connect to the source Aurora cluster writer instance by using the cluster endpoint.

The command will return as follows:

mysql> show global variables like "log_bin";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| log_bin | OFF |
+---------------+-------+

Here, the parameter log_bin is set to OFF. That means binary logging is disabled. Then we have to check and confirm the Aurora cluster’s binlog_format parameter is set to ROW. If it isn’t set to ROW, then set this parameter to enable binary logging.

Also, make sure to reboot the instance after the changes come into effect.

After setting the parameter binlog_format, we have to confirm that binary logging is enabled by connecting to the Aurora instance:

mysql> show global variables like "log_bin";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| log_bin | ON |
+---------------+-------+

After that, make sure that we are using the cluster writer endpoint with AWS DMS, then restart the task.

[Need help to resolve AWS-related errors? We’d be happy to assist]
 

Conclusion

 
To conclude, today we saw how our Support Techs resolve binary logging errors with AWS DMS while using Aurora MySQL.