AWS DMS from account A RDS source endpoint to account B Redshift target endpoint

0

I'm trying to setup a DMS target endpoint in account A. This endpoint is pointing to a Redshift cluster in account B.

Is this possible? How?

I already have a peering connection and I can connect to Redshift in account B from account A using pgcli.

When I try to create the endpoint in account A, I get the following error: Cluster 'CLUSTER_NAME' does not exist..

When I try to use aws dms create-endpoint, I get the following error: An error occurred (InvalidResourceStateFault) when calling the CreateEndpoint operation: Cluster 'CLUSTER_NAME' does not exist..

1 個回答
-1

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

profile picture
專家
已回答 7 個月前
  • But how can I, in the account A DMS, tell the service that it should use a different role to describe the cluster?

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南