DynamoDB Streams

AWS docs: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Operations_Amazon_DynamoDB_Streams.html

DynamoDB Streams accepts the AWS JSON 1.0 API over the shared root endpoint with X-Amz-Target: DynamoDBStreams_20120810.<Operation>. It also accepts Smithy RPC v2 CBOR at /service/DynamoDBStreams/operation/<Operation> with Smithy-Protocol: rpc-v2-cbor and Content-Type: application/cbor.

Streams are region-scoped

A table’s stream belongs to the table’s region, and DynamoDB tables are region-scoped. Two same-named tables in different regions therefore have two distinct stream ARNs and two entirely separate record sets, with independent TRIM_HORIZON and LATEST positions — a write in one region never appears in, or advances, the other’s stream.

Consequences, all matching AWS’s regional endpoints:

ListStreams reports only streams for tables in the request’s region.
DescribeStream and GetShardIterator answer ResourceNotFoundException for a stream ARN belonging to another region.
A shard iterator names the region it was issued for, so GetRecords always pages the stream it was handed rather than resolving the table name afresh. An iterator issued before this behaviour existed still works, resolving against the request’s region as it used to.
Every record carries awsRegion, as AWS’s do.

Stream consumers match on region too: a Lambda event source mapping or an EventBridge pipe whose source ARN names one region’s stream is not triggered by writes to a same-named table in another region.

Summary

Category	✅ Supported
General	4

Endpoints

General

Operation	Status	Notes	AWS Docs
`DescribeStream`	✅ Supported	A stream ARN from another region is a `ResourceNotFoundException`, as on AWS’s regional endpoints	docs
`GetRecords`	✅ Supported	Reads the stream in the region its shard iterator names; each record carries `awsRegion`	docs
`GetShardIterator`	✅ Supported		docs
`ListStreams`	✅ Supported	Region-scoped — reports only streams for tables in the request’s region	docs