AWS eventbridge documentation change

Service: eventbridge · 2025-06-07 · Documentation low

File: eventbridge/latest/ref/events-ref-ce.md

Summary

Added documentation for direct event delivery from Cost Explorer and 'Anomaly Detected' event patterns

Security assessment

While the change improves event monitoring capabilities, there is no explicit security vulnerability addressed or security feature documented. The anomaly detection is a general operational feature.

Diff

diff --git a/eventbridge/latest/ref/events-ref-ce.md b/eventbridge/latest/ref/events-ref-ce.md
index b8bbb72bc..a7e7cc913 100644
--- a//eventbridge/latest/ref/events-ref-ce.md
+++ b//eventbridge/latest/ref/events-ref-ce.md
@@ -5 +5 @@
-Events via CloudTrail
+Service eventsEvents via CloudTrail
@@ -9 +9,34 @@ Events via CloudTrail
-Cost Explorer sends service events to EventBridge via AWS CloudTrail.
+Cost Explorer sends service events directly to EventBridge, as well as via AWS CloudTrail.
+
+## Cost Explorer service events
+
+Cost Explorer sends the following events directly to EventBridge: 
+
+  * Anomaly Detected
+
+
+
+
+_Delivery type_ : [ Best effort ](./event-delivery-level.html)
+
+To match against all events from this service, create an event pattern that matches against the following event attribute:
+
+  * `source`: aws.ce
+
+
+
+    
+    
+    {
+      "source": ["aws.ce"]
+    }
+
+To match against specific events, include a `detail-type` attribute specifying an array of event names to match. For example:
+    
+    
+    {
+      "source": ["aws.ce"],
+      "detail-type": ["Anomaly Detected"]
+    }
+
+For more information, see [Creating event patterns](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-patterns.html#eb-create-pattern) in the _Amazon EventBridge User Guide_.