- Newest
- Most votes
- Most comments
The error message you're seeing suggests that AWS DMS (Database Migration Service) in account A isn't recognizing the Redshift cluster in account B. This is generally due to the fact that DMS, by default, is looking for resources within its own account. In account B (where the Redshift cluster resides), create an IAM role that has the necessary permissions to access the Redshift cluster. Modify the trust relationship of the IAM role in account B to allow the DMS service in account A to assume it. When using the aws dms create-endpoint command, you might need to use the --extra-connection-attributes flag to specify additional connection attributes.
Regards, Andrii
But how can I, in the account A DMS, tell the service that it should use a different role to describe the cluster?
Relevant content
- asked 5 months ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
According to the documentation, this is not possible: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.Redshift.html