Secrets & Key Management · Integration
AWS Secrets Manager
Add AWS Secrets Manager to your product for your customers, and give your AI agents governed access to it.
Embed an AWS Secrets Manager integration so your customers can review secret inventory and rotation posture from inside your product, with access scoped per tenant and every call recorded. Only the scopes needed for what you enable are requested, and secret values are never exposed unless you explicitly enable retrieval.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read secret inventory and metadata into your product.
Surface secrets whose rotation is overdue or disabled.
Read resource policies so your product can flag broad access.
Trigger your product when a secret is rotated or its policy changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks rotation recency before reporting on posture.
An agent reads a secret's policy to explain who can access it.
An agent reacts to a failed rotation and raises it to the owner.
Example prompt
List secrets with rotation disabled or last rotated more than 90 days ago.
Set up AWS Secrets Manager in 4 steps
- 01Open the AWS Secrets Manager connector from your fastn dashboard.
- 02Have each customer authenticate their AWS account with least-privilege read scopes.
- 03Decide whether value retrieval is enabled at all, then map the accounts your product covers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the AWS Secrets Manager integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AWS Secrets Manager integration without building it. Your customers connect their own AWS Secrets Manager account inside your product and work their secrets, keys and certificates there, with no per-customer code on your side.
- Handle the part that actually costs time: an expired certificate or an unrotated key is an outage rather than a warning, and it arrives without notice. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AWS Secrets Manager update is not your on-call problem.
- One integration serves your product and your agents. The same governed AWS Secrets Manager connection powers in-product features and gives AI agents scoped, audited access, so you fetch a credential at the point of use instead of storing it yourself without wiring it twice.
Used by these teams
Compare with
AWS Key Management Service
Azure Key VaultOften used alongside
Tools the same teams tend to run next to AWS Secrets Manager, across other categories.
ServiceNow
Datadog
PagerDutyAWS Secrets Manager integration FAQ
How do I add an AWS Secrets Manager integration to my product?
Enable the AWS Secrets Manager connector in your fastn dashboard, then let each customer authenticate their own AWS Secrets Manager account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS Secrets Manager 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 Secrets Manager account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AWS Secrets Manager account and only ever sees their own secrets, keys and certificates. 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 Secrets Manager 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 checks rotation recency before reporting on posture.
Who maintains the AWS Secrets Manager integration?
fastn does. When AWS Secrets Manager 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 my product ever hold the customer's AWS Secrets Manager secret?
No longer than the call needs it. Values are fetched under the customer's own credentials at the point of use and never written into your database, and every read is logged per tenant so an access can be traced to what asked for it.
Can rotation and expiry be handled automatically?
Yes, within the permissions the customer grants, and audited. This matters more here than almost anywhere else: an expired certificate or an unrotated key takes something down rather than raising a warning first.
What can I build with the AWS Secrets Manager integration?
A common starting point: read secret inventory and metadata 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 Secrets Manager integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS Secrets Manager does not change your per-connector cost. You can start free with 3 connected accounts.
Add AWS Secrets Manager to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.