AWS Security ChangesHomeSearch

AWS AmazonCloudWatch: CloudWatch Omni agent can now delete alerts with confirmation

Service: AmazonCloudWatch · 2026-11-20 · Documentation medium

File: AmazonCloudWatch/latest/monitoring/omni-ask-the-omni-agent.md · Type: authz

Summary

Updates the Omni agent capability description: the agent can now delete an existing alert (previously it never deleted alerts), but only after the user confirms which alert to delete. The bullet describing agent limits is rewritten to say it creates, changes, and deletes alerts only with confirmation.

Security assessment

The change expands the agent's destructive-action scope to include alert deletion, but explicitly ties it to an explicit user confirmation step ('deletes an alert only after you confirm which one'), which is an authorization/guardrail statement for a destructive operation rather than a fix for a specific vulnerability.

Evidence

+  * It creates, changes, and deletes alerts only with your confirmation, and it cannot rename an alert.

Diff

diff --git a/AmazonCloudWatch/latest/monitoring/omni-ask-the-omni-agent.md b/AmazonCloudWatch/latest/monitoring/omni-ask-the-omni-agent.md
index 17205b8..08715ee 100644
--- a//AmazonCloudWatch/latest/monitoring/omni-ask-the-omni-agent.md
+++ b//AmazonCloudWatch/latest/monitoring/omni-ask-the-omni-agent.md
@@ -44 +44 @@ Run commands | "/settings" opens the Settings page. Type "/" to see available co
-**Alerts.** The agent creates Omni alerts, not CloudWatch alarms. It can create an alert from a plain-language condition, change an existing one, and answer questions about the alerts you have. Creating and changing are deliberate: the agent grounds the threshold in your data, shows you the specific alert it intends to create or change, and acts only after you confirm. It does not delete alerts. Manage them on the Alerts page. See [Alerts](./omni-alerts.html).
+**Alerts.** The agent creates Omni alerts, not CloudWatch alarms. It can create an alert from a plain-language condition, change or delete an existing one, and answer questions about the alerts you have. Creating and changing are deliberate: the agent grounds the threshold in your data, shows you the specific alert it intends to create or change, and acts only after you confirm. It deletes an alert only after you confirm which one. You can also manage alerts on the Alerts page. See [Alerts](./omni-alerts.html).
@@ -60 +60 @@ The agent is scoped to observability. It declines unrelated work, such as genera
-  * It creates and changes alerts with your confirmation, but never deletes them, and it cannot rename an alert. You delete an alert yourself on the **Alerts** page.
+  * It creates, changes, and deletes alerts only with your confirmation, and it cannot rename an alert.