- Newest
- Most votes
- Most comments
If you tried opening to all traffic, then ports are not the issue. I would anyway try to verify network connectivity between the replication agent/source server and the replication server in AWS. Run commands like telnet replication_server_dns_name 443 to test connectivity on port 443.
-Check if there are any security groups or firewall rules blocking outbound access from the source on port 443. The replication agent needs to connect to replication server endpoints over HTTPS. -Review logs on the source server for errors connecting to the replication server endpoints. Locate the exact failure point from logs. -Ensure the IAM role used by the replication agent has the necessary permissions to access replication server resources. -Try using a smaller test dataset initially to validate if it's able to connect and replicate properly.
Relevant content
- asked 7 days ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago