- Newest
- Most votes
- Most comments
Hi,
Please confirm if the table being migrated has a primary key in the source database. Currently, AWS DMS has the below limitation[1]:
- A captured table must have a primary key. If a table doesn't have a primary key, AWS DMS ignores DELETE and UPDATE record operations for that table. As a workaround, see Enabling change data capture (CDC) using logical replication.
Please confirm that the role that you use for the migration to DynamoDB has the following permission [2]:
"dynamodb:DeleteItem",
Are there any errors or warnings noted in the AWS DMS task logs. In the Cloudwatch logs, search for "]E:" for errors and "]W:" for warnings.
References:
[1] Using a PostgreSQL database as an AWS DMS source - Limitations on using a PostgreSQL database as a DMS source - https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html#CHAP_Source.PostgreSQL.Limitations [2] Using an Amazon DynamoDB database as a target for AWS Database Migration Service - Prerequisites for using DynamoDB as a target for AWS Database Migration Service - https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.DynamoDB.html#CHAP_Target.DynamoDB.Prerequisites
Relevant content
- asked 20 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
If you're using pglogical, are you sure you're not using insert only i-replication: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html#CHAP_Source.PostgreSQL.v10