IT Operations · Integration
AWS CloudWatch
Add AWS CloudWatch to your product for your customers, and give your AI agents governed access to it.
CloudWatch is where an AWS account keeps its evidence: metrics with their namespaces and dimensions, log groups and the log streams inside them, Logs Insights queries, and alarms with their current state. The dimension set is what catches people out. A metric is identified by its full set of dimensions, so querying with a partial set returns an empty series rather than an error, and empty looks exactly like nothing happened. Resolution matters too, because older points are rolled up into coarser periods, so a long window cannot answer a fine-grained question. Log retention is configured per log group. fastn holds the per-account access, batches metric queries and keeps pace with the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer grant read access to their own account so your product charts their metrics without a second console.
Query with the full dimension set, because a partial one comes back empty and reads as healthy silence.
Search log groups and their streams from inside your product, so an investigation does not start with a context switch.
React when an alarm changes state, so your product acts while the condition is still true.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which alarms are in alarm state and how long each has been there, for one account.
An agent runs a permitted Logs Insights query and cites the log group it searched.
An agent checks whether the resolution available over a window can actually answer the question asked.
Example prompt
Which CloudWatch alarms are firing in this account, and what do the log streams behind them show?
Set up AWS CloudWatch in 4 steps
- 01Enable the Amazon CloudWatch connector from your fastn dashboard.
- 02Have each customer authorise their own Amazon CloudWatch account, so calls run under their credentials rather than a shared key.
- 03Decide which metrics, log groups and alarms your product needs, and record the full dimension set for each metric, since a partial query returns an empty series.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AWS CloudWatch integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AWS CloudWatch integration without building it. Your customers connect their own AWS CloudWatch 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 AWS CloudWatch update is not your on-call problem.
- One integration serves your product and your agents. The same governed AWS CloudWatch 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
Azure Monitor
Datadog
New RelicOften used alongside
Tools the same teams tend to run next to AWS CloudWatch, across other categories.
AWS Secrets Manager
AppViewXAWS CloudWatch integration FAQ
How do I add an AWS CloudWatch integration to my product?
Enable the AWS CloudWatch connector in your fastn dashboard, then let each customer authenticate their own AWS CloudWatch account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS CloudWatch 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 CloudWatch account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AWS CloudWatch 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 AWS CloudWatch 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 reports which alarms are in alarm state and how long each has been there, for one account.
Who maintains the AWS CloudWatch integration?
fastn does. When AWS CloudWatch 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 AWS CloudWatch 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 AWS CloudWatch integration?
A common starting point: let a customer grant read access to their own account so your product charts their metrics without a second console. 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 CloudWatch integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS CloudWatch does not change your per-connector cost. You can start free with 3 connected accounts.
Add AWS CloudWatch to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.