Streaming & Messaging · Integration
AWS Kinesis
Add AWS Kinesis to your product for your customers, and give your AI agents governed access to it.
Kinesis Data Streams is a pipe rather than a store, and an integration has to respect that. A stream is divided into shards, records are written with a partition key that decides which shard they land on, and ordering is guaranteed inside a shard and nowhere else, so choosing a partition key is really an ordering decision. Reading means opening a shard iterator and walking forward, and iterators expire, so a consumer that pauses too long loses its place unless it checkpoints. Resharding splits and merges shards while you are reading, which changes the set you are working through, and records age out of the retention window. fastn manages iterators, checkpoints, retries and reshards for each customer's stream.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Read from a stream the customer owns, so their events never leave the account that produced them.
Choose a partition key deliberately, because it decides whether related records are read back in order.
Consume without losing your place, since a stale iterator expires and a paused reader resumes from a checkpoint.
Keep reading through a reshard, so a split or a merge does not leave your consumer on shards that no longer exist.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent samples recent records from one customer's stream to explain what is flowing through it.
An agent publishes an approved record with the partition key it was told to use, and the write is logged.
An agent reports how far behind a consumer has fallen before its unread records age out of retention.
Example prompt
Read the most recent records from this stream and tell me which partition keys are busiest.
Set up AWS Kinesis in 4 steps
- 01Enable the Amazon Kinesis connector from your fastn dashboard.
- 02Have each customer authorise their own Amazon Kinesis account, so calls run under their credentials rather than a shared key.
- 03Decide which streams, shards and records your product needs, then choose the partition key, because it is what decides ordering.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AWS Kinesis integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AWS Kinesis integration without building it. Your customers connect their own AWS Kinesis account inside your product and work their topics, streams and messages there, with no per-customer code on your side.
- Handle the part that actually costs time: ordering and replay are the whole problem: a consumer that falls behind must be able to resume without losing or double-processing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AWS Kinesis update is not your on-call problem.
- One integration serves your product and your agents. The same governed AWS Kinesis connection powers in-product features and gives AI agents scoped, audited access, so you move events between your product and your customers' systems without either side polling without wiring it twice.
Used by these teams
Compare with
Apache Kafka
Confluent Cloud
Google Cloud Pub/SubOften used alongside
Tools the same teams tend to run next to AWS Kinesis, across other categories.
Snowflake
Airtable
PostgreSQL
Anthropic ClaudeAWS Kinesis integration FAQ
How do I add an AWS Kinesis integration to my product?
Enable the AWS Kinesis connector in your fastn dashboard, then let each customer authenticate their own AWS Kinesis account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS Kinesis client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own AWS Kinesis account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AWS Kinesis account and only ever sees their own topics, streams and messages. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this AWS Kinesis integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent samples recent records from one customer's stream to explain what is flowing through it.
Who maintains the AWS Kinesis integration?
fastn does. When AWS Kinesis changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product replay AWS Kinesis messages after an outage?
Yes, within the retention the customer's own AWS Kinesis setup keeps. Consumer position is tracked per tenant, so a consumer that falls behind resumes from where it stopped rather than skipping ahead or starting over, which is the difference between a gap in your data and a duplicate in it.
How is one customer's stream kept separate from another's?
Each customer authorises their own AWS Kinesis connection, so topics, credentials and consumer positions are theirs alone. That matters more here than in most integrations, because a misrouted message is delivered before anyone can review it.
What can I build with the AWS Kinesis integration?
A common starting point: read from a stream the customer owns, so their events never leave the account that produced them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the AWS Kinesis integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS Kinesis does not change your per-connector cost. You can start free with 3 connected accounts.
Add AWS Kinesis to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.