Content & Documents · Integration
Amazon S3
Add Amazon S3 to your product for your customers, and give your AI agents governed access to it.
S3 is object storage rather than a document system, but files, documents and versions are literally true of it while records and fields are not, so this is the honest fit. Every request is signed with AWS Signature Version 4, which binds the signature to the region and the exact host, so a bucket in eu-west-1 addressed through s3.amazonaws.com gets a 301 with the correct endpoint rather than data, and clients that do not follow the region redirect appear to fail for no reason. Listing is paged with a continuation token and returns keys in lexicographic order with no notion of real directories, so a prefix and delimiter is the only way to emulate folders and a listing of a large bucket is an expensive traversal, not a lookup. Versioning is per bucket and off by default; once enabled, a delete writes a delete marker instead of removing data, so a customer can see an object vanish from listings while continuing to pay for every prior version. Cross-account access usually arrives as an assumed role with an external id rather than a long-lived key. fastn holds each customer's role or key on their own connection, handles the signing and region routing, and keeps access scoped to the buckets they granted.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own S3 bucket so exports from your product land in storage they control
Read customer-supplied files from a prefix they nominate and process them without ever copying them into your account
Give users a browse view of a bucket using prefix and delimiter listing so it feels like folders
Show prior versions of an object so a customer can recover a file your workflow overwrote
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which objects under a given prefix changed in the last day and how large they are
Have an agent write a generated report to a customer's bucket at an agreed key, with the write audited per tenant
Let an agent check whether versioning is enabled on a tenant's bucket before a destructive workflow runs
Example prompt
What files landed under the exports/2026-07 prefix in our bucket this week?
Set up Amazon S3 in 4 steps
- 01Enable the Amazon S3 connector from your fastn dashboard.
- 02Have each customer authorise their own Amazon S3 account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Amazon S3 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Amazon S3 integration without building it. Your customers connect their own Amazon S3 account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Amazon S3 update is not your on-call problem.
- One integration serves your product and your agents. The same governed Amazon S3 connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Amazon S3, across other categories.
Shopify
Stripe
Jira
AsanaAmazon S3 integration FAQ
How do I add an Amazon S3 integration to my product?
Enable the Amazon S3 connector in your fastn dashboard, then let each customer authenticate their own Amazon S3 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Amazon S3 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Amazon S3 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Amazon S3 account and only ever sees their own files, documents and versions. 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 Amazon S3 integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which objects under a given prefix changed in the last day and how large they are
Who maintains the Amazon S3 integration?
fastn does. When Amazon S3 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.
Whose permissions does the Amazon S3 integration run under?
Each customer's own Amazon S3 grant. Where Amazon S3 holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Amazon S3 automatically?
Where Amazon S3 supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Amazon S3 integration?
A common starting point: let a customer connect their own S3 bucket so exports from your product land in storage they control. 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 Amazon S3 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Amazon S3 does not change your per-connector cost. You can start free with 3 connected accounts.
Add Amazon S3 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.