I am following the guide here to set up Logical Replication in Aurora MySQL[1]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.MySQL.html
After setting it up and starting the replication process, I run "show slave status" on the slave to verify it works. However, it's stuck "Connecting to master" with the IO error code 2003 and the follow error message: 'error connecting to master '{user}@{endpoint}:3306' - retry-time: 60 retries: 331'
I am stumped trying to get this connected. Both are in the same VPC security groups and are within the same Availability Zone...it's basically a straight copy in RDS. Ergo, I should not need to create an inbound rule for it since they are on the same network correct? If I do, what would I input for the inbound rule - the slave's endpoint as the IP?
I have tried setting a wildcard for the user instead of the slave endpoint, and have verified I am able to login to the master with the slave's user (on my computer via Workbench) so it shouldn't be an issue with the user account.
From googling, it seems that having a bind-address set is a common issue for 2003 connection error, which is set via the 'my.cnf' configuration file. From what I can understand, the Parameter Group in AWS is the equivalent of the my.cnf configuration file, and "bind-address" is not an option so therefore should not be set. Is that correct, or is there somewhere else the bind-address might be set?
Any help would be appreciated
[1] Which, to verify the steps are done correctly:
Created new Parameter group to include binlog_format = MIXED, both instances are set to that Parameter group
Created a Snapshot of Master, created a new DB instance off Snapshot for Slave; Wrote down Binlog name and position from event logging
Create user on Master with REPLICATION CLIENT, REPLICATION SLAVE privileges
Set the Master on the Slave using rds_set_external_master; Using the Master Endpoint, User from #3, and Binlog information from #2
Start replication...which gives a connection error 2003
