- Newest
- Most votes
- Most comments
same issue happend. i added "dms.ap-northaeast-1.amazonaws.com " , but not working too.
answered 8 months ago
Based on the error you're experiencing with creating a DMS Data Collector, it appears to be an IAM permissions issue. Several users have reported similar problems even when following the documentation correctly.
The issue might be related to the trust relationship in your IAM role. While the documentation suggests creating a role with the "DMS - Fleet Advisor" policy, some users have found that the trust policy needs to include not only the general DMS service but also the region-specific DMS endpoint.
Try modifying the trust relationship of your FleetAdvisorS3Role to include both:
- dms.amazonaws.com
- dms-fleet-advisor.amazonaws.com
- dms.[your-region].amazonaws.com (e.g., dms.us-east-1.amazonaws.com)
This additional principal in the trust policy has helped others resolve this specific issue. The documentation may not clearly indicate this requirement, which is why you're encountering the error despite following the official guidance.
Also, ensure that:
- The Windows Management Instrumentation service is running (if applicable)
- Your S3 bucket permissions are correctly configured
- The service-linked role for DMS Fleet Advisor has been properly created
Sources
DMS can't create the data collector (IAM correclty created) | AWS re:Post
Troubleshooting data collection issues related to Windows Management Instrumentation in AWS DMS - AWS Database Migration Service
answered 9 months ago
Relevant content
asked 2 years ago
asked 3 years ago
asked 2 years ago
- AWS OFFICIALUpdated 6 months ago

Tried this approach. But not working