* CreateStream has a limit of five transactions per second per * account.
+ *You can add tags to the stream when making a CreateStream request by
+ * setting the Tags parameter. If you pass Tags parameter, in
+ * addition to having kinesis:createStream permission, you must also have
+ * kinesis:addTagsToStream permission for the stream that will be created.
+ * Tags will take effect from the CREATING status of the stream.
The requested resource exceeds the maximum number allowed, or the number of concurrent * stream requests exceeds the maximum number allowed.
* + * @throws {@link ResourceInUseException} (client fault) + *The resource is not available for this operation. For successful operation, the
+ * resource must be in the ACTIVE state.
The requested resource could not be found. The stream might not be specified * correctly.
diff --git a/clients/client-kinesis/src/commands/RegisterStreamConsumerCommand.ts b/clients/client-kinesis/src/commands/RegisterStreamConsumerCommand.ts index d4ddc0c7be69..ebaaba2af050 100644 --- a/clients/client-kinesis/src/commands/RegisterStreamConsumerCommand.ts +++ b/clients/client-kinesis/src/commands/RegisterStreamConsumerCommand.ts @@ -35,7 +35,7 @@ export interface RegisterStreamConsumerCommandOutput extends RegisterStreamConsu * read from the same stream. *You can register up to 20 consumers per stream. A given consumer can only be * registered with one stream at a time.
- *For an example of how to use this operations, see Enhanced Fan-Out
+ * For an example of how to use this operation, see Enhanced Fan-Out
* Using the Kinesis Data Streams API. The use of this operation has a limit of five transactions per second per account.
* Also, only 5 consumers can be created simultaneously. In other words, you cannot have
diff --git a/clients/client-kinesis/src/commands/SubscribeToShardCommand.ts b/clients/client-kinesis/src/commands/SubscribeToShardCommand.ts
index 64350a45d976..d165e4f10edd 100644
--- a/clients/client-kinesis/src/commands/SubscribeToShardCommand.ts
+++ b/clients/client-kinesis/src/commands/SubscribeToShardCommand.ts
@@ -53,7 +53,7 @@ export interface SubscribeToShardCommandOutput extends SubscribeToShardOutput, _
* seconds or more after a successful call, the second call takes over the subscription and
* the previous connection expires or fails with a
* For an example of how to use this operations, see Enhanced Fan-Out
+ * For an example of how to use this operation, see Enhanced Fan-Out
* Using the Kinesis Data Streams API. A set of up to 10 key-value pairs to use to create the tags. Creates a Kinesis data stream. A stream captures and transports data records that are\n continuously emitted from different data sources or producers.\n Scale-out within a stream is explicitly supported by means of shards, which are uniquely\n identified groups of data records in a stream. You can create your data stream using either on-demand or provisioned capacity mode.\n Data streams with an on-demand mode require no capacity planning and automatically scale\n to handle gigabytes of write and read throughput per minute. With the on-demand mode,\n Kinesis Data Streams automatically manages the shards in order to provide the necessary\n throughput. For the data streams with a provisioned mode, you must specify the number of\n shards for the data stream. Each shard can support reads up to five transactions per\n second, up to a maximum data read total of 2 MiB per second. Each shard can support\n writes up to 1,000 records per second, up to a maximum data write total of 1 MiB per\n second. If the amount of data input increases or decreases, you can add or remove\n shards. The stream name identifies the stream. The name is scoped to the Amazon Web Services\n account used by the application. It is also scoped by Amazon Web Services Region. That\n is, two streams in two different accounts can have the same name, and two streams in the\n same account, but in two different Regions, can have the same name. \n You receive a Have more than five streams in the Create more shards than are authorized for your account. For the default shard limit for an Amazon Web Services account, see Amazon\n Kinesis Data Streams Limits in the Amazon Kinesis Data Streams\n Developer Guide. To increase this limit, contact Amazon Web Services\n Support. You can use DescribeStreamSummary to check the stream status, which\n is returned in \n CreateStream has a limit of five transactions per second per\n account. Creates a Kinesis data stream. A stream captures and transports data records that are\n continuously emitted from different data sources or producers.\n Scale-out within a stream is explicitly supported by means of shards, which are uniquely\n identified groups of data records in a stream. You can create your data stream using either on-demand or provisioned capacity mode.\n Data streams with an on-demand mode require no capacity planning and automatically scale\n to handle gigabytes of write and read throughput per minute. With the on-demand mode,\n Kinesis Data Streams automatically manages the shards in order to provide the necessary\n throughput. For the data streams with a provisioned mode, you must specify the number of\n shards for the data stream. Each shard can support reads up to five transactions per\n second, up to a maximum data read total of 2 MiB per second. Each shard can support\n writes up to 1,000 records per second, up to a maximum data write total of 1 MiB per\n second. If the amount of data input increases or decreases, you can add or remove\n shards. The stream name identifies the stream. The name is scoped to the Amazon Web Services\n account used by the application. It is also scoped by Amazon Web Services Region. That\n is, two streams in two different accounts can have the same name, and two streams in the\n same account, but in two different Regions, can have the same name. \n You receive a Have more than five streams in the Create more shards than are authorized for your account. For the default shard limit for an Amazon Web Services account, see Amazon\n Kinesis Data Streams Limits in the Amazon Kinesis Data Streams\n Developer Guide. To increase this limit, contact Amazon Web Services\n Support. You can use DescribeStreamSummary to check the stream status, which\n is returned in \n CreateStream has a limit of five transactions per second per\n account. You can add tags to the stream when making a Indicates the capacity mode of the data stream. Currently, in Kinesis Data Streams,\n you can choose between an on-demand capacity mode and a\n provisioned capacity mode for your data\n streams. A set of up to 10 key-value pairs to use to create the tags. Registers a consumer with a Kinesis data stream. When you use this operation, the\n consumer you register can then call SubscribeToShard to receive data\n from the stream using enhanced fan-out, at a rate of up to 2 MiB per second for every\n shard you subscribe to. This rate is unaffected by the total number of consumers that\n read from the same stream. You can register up to 20 consumers per stream. A given consumer can only be\n registered with one stream at a time. For an example of how to use this operations, see Enhanced Fan-Out\n Using the Kinesis Data Streams API. The use of this operation has a limit of five transactions per second per account.\n Also, only 5 consumers can be created simultaneously. In other words, you cannot have\n more than 5 consumers in a Registers a consumer with a Kinesis data stream. When you use this operation, the\n consumer you register can then call SubscribeToShard to receive data\n from the stream using enhanced fan-out, at a rate of up to 2 MiB per second for every\n shard you subscribe to. This rate is unaffected by the total number of consumers that\n read from the same stream. You can register up to 20 consumers per stream. A given consumer can only be\n registered with one stream at a time. For an example of how to use this operation, see Enhanced Fan-Out\n Using the Kinesis Data Streams API. The use of this operation has a limit of five transactions per second per account.\n Also, only 5 consumers can be created simultaneously. In other words, you cannot have\n more than 5 consumers in a This operation establishes an HTTP/2 connection between the consumer you specify in\n the When the You can make one call to If you call For an example of how to use this operations, see Enhanced Fan-Out\n Using the Kinesis Data Streams API. This operation establishes an HTTP/2 connection between the consumer you specify in\n the When the You can make one call to If you call For an example of how to use this operation, see Enhanced Fan-Out\n Using the Kinesis Data Streams API.ResourceInUseException.CreateStream is an asynchronous operation. Upon receiving a\n CreateStream request, Kinesis Data Streams immediately returns and sets\n the stream status to CREATING. After the stream is created, Kinesis Data\n Streams sets the stream status to ACTIVE. You should perform read and write\n operations only on an ACTIVE stream. LimitExceededException when making a\n CreateStream request when you try to do one of the following:\n
\n CREATING state at any point in\n time.StreamStatus.CreateStream is an asynchronous operation. Upon receiving a\n CreateStream request, Kinesis Data Streams immediately returns and sets\n the stream status to CREATING. After the stream is created, Kinesis Data\n Streams sets the stream status to ACTIVE. You should perform read and write\n operations only on an ACTIVE stream. LimitExceededException when making a\n CreateStream request when you try to do one of the following:\n
\n CREATING state at any point in\n time.StreamStatus.CreateStream request by\n setting the Tags parameter. If you pass Tags parameter, in\n addition to having kinesis:createStream permission, you must also have\n kinesis:addTagsToStream permission for the stream that will be created.\n Tags will take effect from the CREATING status of the stream. CREATING status at the same time. Registering a\n 6th consumer while there are 5 in a CREATING status results in a\n LimitExceededException.CREATING status at the same time. Registering a\n 6th consumer while there are 5 in a CREATING status results in a\n LimitExceededException.ConsumerARN parameter and the shard you specify in the\n ShardId parameter. After the connection is successfully established,\n Kinesis Data Streams pushes records from the shard to the consumer over this connection.\n Before you call this operation, call RegisterStreamConsumer to\n register the consumer with Kinesis Data Streams.SubscribeToShard call succeeds, your consumer starts receiving\n events of type SubscribeToShardEvent over the HTTP/2 connection for up\n to 5 minutes, after which time you need to call SubscribeToShard again to\n renew the subscription if you want to continue to receive records.SubscribeToShard per second per registered\n consumer per shard. For example, if you have a 4000 shard stream and two registered\n stream consumers, you can make one SubscribeToShard request per second for\n each combination of shard and registered consumer, allowing you to subscribe both\n consumers to all 4000 shards in one second. SubscribeToShard again with the same ConsumerARN\n and ShardId within 5 seconds of a successful call, you'll get a\n ResourceInUseException. If you call SubscribeToShard 5\n seconds or more after a successful call, the second call takes over the subscription and\n the previous connection expires or fails with a\n ResourceInUseException.ConsumerARN parameter and the shard you specify in the\n ShardId parameter. After the connection is successfully established,\n Kinesis Data Streams pushes records from the shard to the consumer over this connection.\n Before you call this operation, call RegisterStreamConsumer to\n register the consumer with Kinesis Data Streams.SubscribeToShard call succeeds, your consumer starts receiving\n events of type SubscribeToShardEvent over the HTTP/2 connection for up\n to 5 minutes, after which time you need to call SubscribeToShard again to\n renew the subscription if you want to continue to receive records.SubscribeToShard per second per registered\n consumer per shard. For example, if you have a 4000 shard stream and two registered\n stream consumers, you can make one SubscribeToShard request per second for\n each combination of shard and registered consumer, allowing you to subscribe both\n consumers to all 4000 shards in one second. SubscribeToShard again with the same ConsumerARN\n and ShardId within 5 seconds of a successful call, you'll get a\n ResourceInUseException. If you call SubscribeToShard 5\n seconds or more after a successful call, the second call takes over the subscription and\n the previous connection expires or fails with a\n ResourceInUseException.