Developer Tools · Integration
AWS
Add AWS to your product for your customers, and give your AI agents governed access to it.
An AWS integration at the account level is about reach and trust rather than a tidy object model. A customer creates an IAM role in their own account with a trust policy naming an external id, your calls assume that role, and the permissions are a policy document they can read and narrow rather than a checkbox list. Everything underneath is regional, so a resource in one region is invisible to a call made against another, and quotas are counted per account per region as well. That makes region and role scope the first things to get right. When a feature needs depth in one service, the streaming and monitoring connectors go further than this page does. fastn manages role assumption, credential rotation and SDK upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer create a role in their own account with an external id, so your product never holds their long-lived keys.
List and act on resources across the regions a customer actually uses, instead of assuming one default region.
Show a customer the exact policy your product needs, so they can narrow it before they approve it.
Send a customer to the streaming or monitoring connector when a feature needs more than account-level reach.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent inspects what exists in one customer's account before it recommends anything, and the role it assumed is recorded.
An agent performs an approved change under that role, with the region and the policy in force both logged.
An agent explains why a call was refused by naming the permission the policy did not grant.
Example prompt
Which regions does this account have running resources in, and what does the role we assume let us see?
Set up AWS in 4 steps
- 01Enable the AWS connector from your fastn dashboard.
- 02Have each customer authorise their own AWS account, so calls run under their credentials rather than a shared key.
- 03Decide which accounts, regions, roles and resources your product needs, then scope the assumed role's policy to only those.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AWS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AWS integration without building it. Your customers connect their own AWS account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AWS update is not your on-call problem.
- One integration serves your product and your agents. The same governed AWS connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
Azure
Google Cloud
AWS LambdaOften used alongside
Tools the same teams tend to run next to AWS, across other categories.
Slack
Snowflake
Airtable
PostgreSQLAWS integration FAQ
How do I add an AWS integration to my product?
Enable the AWS connector in your fastn dashboard, then let each customer authenticate their own AWS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS 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 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AWS account and only ever sees their own services, builds and deployments. 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 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 inspects what exists in one customer's account before it recommends anything, and the role it assumed is recorded.
Who maintains the AWS integration?
fastn does. When AWS 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 I react to AWS events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in AWS?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the AWS integration?
A common starting point: have each customer create a role in their own account with an external id, so your product never holds their long-lived keys. 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 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS does not change your per-connector cost. You can start free with 3 connected accounts.
Add AWS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.