> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/workshops/duplocloud-101-for-aws/create-your-infrastructure-and-application/9.-create-an-alarm.md).
# 10. Create an Alarm
Creating an alarm in the DuploCloud Portal
## Prerequisites
### Enable automatic alerting
Navigate to **Administrator** → **Tenants**, and select the Tenant you created from the list.
Select the **Alerting** tab, click **Enable Alerting**, and click **Update** to save the alert configuration.
## Create an Alert
Navigate to **Observability** → **Alerts**, and click **Add**. The **Create Alert** pane displays. Complete the fields with the following values:
* **Resource Type**: `EC2`
* **Resource**: \[*select a previously created* [*EC2 instance*](/docs/automation-platform/workshops/duplocloud-101-for-aws/create-your-infrastructure-and-application/4.-create-an-eks-worker-node.md)]
{% hint style="info" %}
In the example below, the Friendly Name in the **Resource** field is `host02`.
{% endhint %}
Click **Next** to proceed with defining metrics data.
## Set the Alarm with a Third-Party Integration
Navigate to **Observability** → **Faults** → **Update Notifications Config**. The **Set Alert Notifications** **Config** pane displays.
If instructed, enter additional data and click **Update** to set the alarm.
The Set Alert NotificationsConfig pane
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.duplocloud.com/docs/automation-platform/workshops/duplocloud-101-for-aws/create-your-infrastructure-and-application/9.-create-an-alarm.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
