2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
Is your DMS connected to a subnet in your VPC which
- doesn’t have a route to the internet via a NAT gateway
- is in a public subnet without a public IP
- Have a S3 gateway and can’t route via it.
The DMS if attaching to the VPC will need to be able resolve and connect to the S3 endpoint.
1
Make sure you have ephemeral ports open if a private subnet behind NAT!!
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html#nacl-ephemeral-ports
répondu il y a 8 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
Thank you for your response. We did discover that this problem started occurring after we upgraded to DMS 3.5.1 from DMS 3.4.6. I think we were able to resolve the issue by adding an S3 VPC gateway endpoint.