2 回答
- 最新
- 投票最多
- 评论最多
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
已回答 8 个月前
相关内容
- AWS 官方已更新 8 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
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.