IT Operations · Integration
Amazon CloudFront
Add Amazon CloudFront to your product for your customers, and give your AI agents governed access to it.
Embed an Amazon CloudFront integration so your customers can manage distributions and cache invalidations from inside your product, with access scoped per tenant and every call audited. fastn handles each customer's credentials and API upkeep, so CDN operations are configuration rather than bespoke code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read distribution configuration and status from your product.
Create cache invalidations from your product when content changes.
Read distribution metrics so users can see delivery health in your product.
Trigger your product when a distribution deployment or invalidation completes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks distribution status before reporting on an incident.
An agent issues an invalidation within governed permissions.
An agent reacts to an error-rate change and gathers the relevant metrics.
Example prompt
List distributions with a 5xx error rate above 1 percent in the last hour.
Set up Amazon CloudFront in 4 steps
- 01Open the Amazon CloudFront connector from your fastn dashboard.
- 02Have each customer authenticate their AWS account with least-privilege scopes.
- 03Map the distributions your product manages, then enable the actions you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Amazon CloudFront integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Amazon CloudFront integration without building it. Your customers connect their own Amazon CloudFront account inside your product and work their incidents, alerts and on-call schedules there, with no per-customer code on your side.
- Handle the part that actually costs time: alerting is latency-critical and noisy, so filtering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Amazon CloudFront update is not your on-call problem.
- One integration serves your product and your agents. The same governed Amazon CloudFront connection powers in-product features and gives AI agents scoped, audited access, so you route operational signal to the people and systems that act on it without wiring it twice.
Used by these teams
Compare with
AWS CloudWatchWorks well with
Often used alongside
Tools the same teams tend to run next to Amazon CloudFront, across other categories.
AppViewX
Azure Key VaultAmazon CloudFront integration FAQ
How do I add an Amazon CloudFront integration to my product?
Enable the Amazon CloudFront connector in your fastn dashboard, then let each customer authenticate their own Amazon CloudFront account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Amazon CloudFront 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 CloudFront account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Amazon CloudFront account and only ever sees their own incidents, alerts and on-call schedules. 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 CloudFront 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 distribution status before reporting on an incident.
Who maintains the Amazon CloudFront integration?
fastn does. When Amazon CloudFront 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.
How fast does an Amazon CloudFront alert reach my product?
Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.
Can duplicate or flapping alerts be suppressed?
Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.
What can I build with the Amazon CloudFront integration?
A common starting point: read distribution configuration and status from 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 Amazon CloudFront integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Amazon CloudFront does not change your per-connector cost. You can start free with 3 connected accounts.
Add Amazon CloudFront to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.