Docs/Connections/Cloud Databases

AWS Aurora MySQL Guide

Use this page when DBConvert Streams connects to an Aurora MySQL cluster.

This guide focuses on the Aurora-specific parts of the setup:

  • cluster endpoint and network access
  • parameter-group changes for binlog-based CDC
  • TLS certificate handling

For the core workflow split, use:

Base setup

  1. Open the AWS RDS console.
  2. Select the Aurora MySQL cluster and note the writer or reader endpoint you intend to use.
  3. Confirm the DBConvert Streams deployment can reach the cluster on port 3306.
  4. Confirm the connection user has the minimum privileges required for the workflow.

Network and TLS

Typical checks:

  • the Aurora security group allows inbound traffic from the DBConvert Streams host or VPC path
  • the selected endpoint is reachable from the deployment network
  • TLS certificate validation is configured if your environment requires it

To validate TLS with the public RDS CA bundle:

wget https://truststore.pki.rds.amazonaws.com/global/global-bundle.pem -O rds-ca.pem

Then use that CA in the DBConvert Streams connection if you run with certificate verification enabled.

CDC source preparation

Aurora MySQL CDC still uses the MySQL binlog model. The Aurora-specific difference is that the required settings live in a cluster parameter group.

Required values:

ParameterValue
binlog_formatROW
binlog_row_imageFULL
binlog_checksumNONE

Typical flow:

  1. Create or edit the Aurora cluster parameter group.
  2. Set the binlog parameters above.
  3. Attach the parameter group to the cluster if needed.
  4. Reboot the cluster when AWS marks the changes as pending reboot.

After reboot, verify:

SHOW VARIABLES LIKE 'binlog%';
SHOW BINARY LOGS;
SELECT @@binlog_format, @@binlog_row_image;

Then finish the DBConvert Streams side of the CDC setup with MySQL CDC Source Configuration.

Validation checklist

  1. Test the Aurora connection using the writer endpoint — right-click it in the Data Explorer sidebar and select Test connection, or use the Test Connection button in the connection editor.
  2. Open it in Data Explorer to confirm visible tables.
  3. If the workflow uses CDC, run SELECT @@binlog_format, @@binlog_row_image and confirm the cluster parameter group changes propagated after reboot.
  4. Verify SHOW BINARY LOGS returns results — empty output means binlog is not active on this cluster.
PreviousAmazon RDS for MySQLNextAWS Aurora PostgreSQL