Home icon

Tune replication performance with AWS DMS for an Amazon Kinesis Data Streams target endpoint – Part 3

Database Blog

This article discusses key considerations and best practices when replicating data using AWS DMS to Amazon Kinesis Data Streams. It covers the following topics:

  • Keeping end-to-end communication private using a VPC interface endpoint for Kinesis
  • Choosing an appropriate candidate on the source as the partition key to distribute data across shards efficiently
  • Provisioning a sufficient number of shards in Kinesis based on the expected throughput
  • Ensuring that the payload message size does not exceed 1 MB, which is the maximum allowed by Kinesis
  • Understanding that records may be out of order when using the PutRecords API with multi-threading, and data deduplication considerations
  • Handling nullable columns in the partition key appropriately
Go to article

The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.

Related articles

May 3
2024
Tune replication performance with AWS DMS for an Amazon Kinesis Data Streams target endpoint – Part 2
May 3
2024
Tune replication performance with AWS DMS for an Amazon Kinesis Data Streams target endpoint – Part 1
Apr 22
2024
Troubleshoot and minimize AWS DMS replication latency with Amazon S3 as a target
Jun 3
2024
Optimize write throughput for Amazon Kinesis Data Streams

The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.