- Newest
- Most votes
- Most comments
I assume that this is dms connectivity issue to s3 on private network.
Starting DMS version 3.4.7 DMS must access the source bucket through a VPC endpoint or a public route.
https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html#CHAP_Target.S3.Prerequisites
Unlike replication instances, AWS DMS Serverless replications do not have a public IP address for management tasks https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Serverless.Limitations.html
thus having VPC endpoint is a must.
https://docs.aws.amazon.com/dms/latest/userguide/CHAP_VPC_Endpoints.html
this link should give insight on how to create a vpc endpoint to access s3 bucket on private network.
Once you have a VPC endpoint setup, make a note of subnets which would be using this vpc endpoint.
say you 3 VPC subnets. Next is create a AWS DMS replication subnet group with this 3 subnets.
Now while setting up DMS serverless replication config use this DMS replication subnet group.
this should resolve the endpoint connection issue.
for reference you can check the blog https://aws.amazon.com/blogs/database/orchestrate-an-aws-dms-serverless-replication-task-using-aws-cli/
Relevant content
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago