> For the complete documentation index, see [llms.txt](https://docs.natoma.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.natoma.ai/apps/aws-cloudwatch.md).

# AWS CloudWatch

**Type:** Official

**Source Type:** Repository

**Source:** [GitHub](https://github.com/awslabs/mcp/tree/main/src/cloudwatch-mcp-server)

**Description:** AWS CloudWatch MCP server enables AI assistants to query metrics, analyze alarms, and search logs using CloudWatch Logs Insights. It is useful for incident investigation, observability workflows, and on-call triage directly from your AI assistant.

**Configuration Parameters:**

* **AwsAccessKey ID** \* - AWS access key ID for authentication
* **AwsRegion** \* - AWS region for API requests (e.g., `us-east-1`)
* **AwsSecretAccessKey** \* - AWS secret access key for authentication
* **AwsSessionToken** \* - Session token for temporary AWS credentials
* **FastmcpLogLevel** - Logging level for the server (optional). Default: `ERROR`

**Setup Steps:**

1. Log in to the AWS Console and navigate to IAM.
2. Create a new IAM user (or select an existing one) for the MCP server.
3. Attach a policy that grants the following CloudWatch and Logs permissions:
   * `cloudwatch:DescribeAlarms`
   * `cloudwatch:DescribeAlarmHistory`
   * `cloudwatch:GetMetricData`
   * `cloudwatch:ListMetrics`
   * `logs:DescribeLogGroups`
   * `logs:DescribeQueryDefinitions`
   * `logs:ListLogAnomalyDetectors`
   * `logs:ListAnomalies`
   * `logs:StartQuery`
   * `logs:GetQueryResults`
   * `logs:StopQuery`
4. Generate an Access Key ID and Secret Access Key for the user. For short-lived credentials, also generate a Session Token via AWS STS.
5. Note the AWS region you want to query (e.g., `us-east-1`).
6. Copy the credentials into the Natoma connector configuration.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.natoma.ai/apps/aws-cloudwatch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.