AWS RDS

RDS and Aurora Postgres or MySQL, connected over a network path you control.

Postgres on RDS

• Set rds.logical_replication = 1 in the parameter group and reboot the instance.
• Grant the connecting role rds_replication — preflight checks this as can replicate.
• The schema-tracking event trigger needs superuser; on RDS that is rds_superuser. Without it, use reconcile after migrations.
• The roles dump (pg_dumpall --roles-only) is not permitted on RDS and is skipped automatically.

MySQL on RDS

• Set gtid-mode = ON, enforce_gtid_consistency = ON, and binlog_format = ROW in the parameter group, then reboot.
• Enable automated backups so binary logging is on.
• Grant the user REPLICATION SLAVE plus read access.

Network

RDS instances are usually not publicly reachable. Run the anybranch server where it can reach the instance (same VPC, or via a bastion / tunnel), and point preflight/clone at the instance endpoint. Preflight is read-only, so it is safe to run first to confirm the path and settings.