Data & Storage · Integration
AWS DynamoDB
Add AWS DynamoDB to your product for your customers, and give your AI agents governed access to it.
Embed an AWS DynamoDB integration so your customers can read and write their own tables from inside your product, with access scoped per tenant and every call audited. Table schemas differ per customer, so attribute mapping is configuration rather than code, and pagination is handled for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read items from their own tables into your product.
Create or update items from your product without writing a client per customer.
Read table and index metadata at runtime so your product adapts per customer.
Trigger your product when items change, using streams where enabled.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads items to answer a question with current data.
An agent writes or updates an item within governed permissions.
An agent reacts to a change event and runs the next workflow step.
Example prompt
Read the orders table for this account and list any item with a status of pending older than two days.
Set up AWS DynamoDB in 4 steps
- 01Enable the Amazon DynamoDB connector from your fastn dashboard.
- 02Have each customer authorise their own AWS account, so reads and writes run under their credentials rather than a shared role.
- 03Map the tables, partition and sort keys and any secondary indexes your product queries, since DynamoDB reads follow the key design rather than arbitrary fields.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AWS DynamoDB integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AWS DynamoDB integration without building it. Your customers connect their own AWS DynamoDB account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AWS DynamoDB update is not your on-call problem.
- One integration serves your product and your agents. The same governed AWS DynamoDB connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
MongoDBWorks well with
AWS LambdaOften used alongside
Tools the same teams tend to run next to AWS DynamoDB, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceAWS DynamoDB integration FAQ
How do I add an AWS DynamoDB integration to my product?
Enable the AWS DynamoDB connector in your fastn dashboard, then let each customer authenticate their own AWS DynamoDB account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS DynamoDB 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 DynamoDB account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AWS DynamoDB account and only ever sees their own records, datasets and fields. 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 DynamoDB 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 reads items to answer a question with current data.
Who maintains the AWS DynamoDB integration?
fastn does. When AWS DynamoDB 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.
Does the AWS DynamoDB integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large AWS DynamoDB reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the AWS DynamoDB integration?
A common starting point: read items from their own tables into your product. 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 DynamoDB integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS DynamoDB does not change your per-connector cost. You can start free with 3 connected accounts.
Add AWS DynamoDB to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.