Streaming & Messaging · Integration
Amazon SNS
Add Amazon SNS to your product for your customers, and give your AI agents governed access to it.
Embed an Amazon SNS integration so your customers can publish notifications to their own topics and manage subscriptions from inside your product, with agent access scoped per tenant and every call audited. Publishes are deduplicated per event so a retry after a network failure does not fan the same notification out twice. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers publish messages from your product to topics in their own AWS account.
Create topics and manage subscriptions and their endpoints from inside your product.
Read subscription attributes and filter policies so users can see who receives what.
Trigger your product from messages delivered to a subscribed endpoint.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists a topic's subscriptions before proposing a notification change.
An agent publishes a message to a topic within governed permissions.
An agent reacts to an incoming notification and runs the next workflow step.
Example prompt
List topics with no confirmed subscriptions and show when each was last published to.
Set up Amazon SNS in 4 steps
- 01Open the Amazon SNS connector from your fastn dashboard.
- 02Have each customer authenticate their AWS account with least-privilege SNS permissions.
- 03Map the topics your product publishes to, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Amazon SNS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Amazon SNS integration without building it. Your customers connect their own Amazon SNS 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 Amazon SNS update is not your on-call problem.
- One integration serves your product and your agents. The same governed Amazon SNS 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
Works well with
Amazon SES
SlackOften used alongside
Tools the same teams tend to run next to Amazon SNS, across other categories.
Snowflake
Airtable
PostgreSQL
Anthropic ClaudeAmazon SNS integration FAQ
How do I add an Amazon SNS integration to my product?
Enable the Amazon SNS connector in your fastn dashboard, then let each customer authenticate their own Amazon SNS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Amazon SNS 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 SNS account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Amazon SNS 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 Amazon SNS 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 lists a topic's subscriptions before proposing a notification change.
Who maintains the Amazon SNS integration?
fastn does. When Amazon SNS 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 Amazon SNS messages after an outage?
Yes, within the retention the customer's own Amazon SNS 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 Amazon SNS 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 Amazon SNS integration?
A common starting point: publish messages from your product to topics in their own AWS account. 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 SNS integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Amazon SNS does not change your per-connector cost. You can start free with 3 connected accounts.
Add Amazon SNS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.