Menu
Amazon Kinesis Streams
Developer Guide

Amazon Kinesis Streams Limits

Kinesis Streams has following limits.

  • The default shard limit is 500 shards for the following regions: US East (N. Virginia), US West (Oregon), and EU (Ireland). For all other regions, the default shard limit is 200 shards. There is no upper limit to the number of shards in a stream or account. To view your limits and the number of shards in use, use the DescribeLimits API or the describe-limits command. To request an increase in your shard limit, use the Kinesis Streams Limits form.

  • Changing the Data Retention Period

  • The maximum size of a data blob (the data payload before base64-encoding) is up to 1 MB.

  • AddTagsToStream, ListTagsForStream, and RemoveTagsFromStream can provide up to 5 transactions per second per account.

  • CreateStream, DeleteStream, and ListStreams can provide up to 5 transactions per second.

  • DescribeStream can provide up to 10 transactions per second.

  • DescribeStreamSummary can provide up to 20 transactions per second.

  • GetRecords can retrieve 10 MB of data.

  • DescribeLimits can provide up to 1 transaction per second.

  • GetShardIterator can provide up to 5 transactions per second per open shard.

  • MergeShards and SplitShard can provide up to 5 transactions per second.

  • UpdateShardCount provides up to 2 calls per rolling 24-hour period per region. By default, the API can scale up to either your shard limit or 500 shards, whichever is lower. To request an increase in the call rate limit, the shard limit for this API, or your overall shard limit, use the Kinesis Streams Limits form.

  • Each shard can support up to 5 transactions per second for reads, up to a maximum total data read rate of 2 MB per second.

  • Each shard can support up to 1,000 records per second for writes, up to a maximum total data write rate of 1 MB per second (including partition keys). This write limit applies to operations such as PutRecord and PutRecords.

  • A shard iterator returned by GetShardIterator times out after 5 minutes if you haven't used it.

Read limits are based on the number of open shards. For more information about shard states, see Data Routing, Data Persistence, and Shard State after a Reshard.

Many of these limits are directly related to API operations. For more information, see the Amazon Kinesis API Reference.