AWS eventbridge documentation change
Summary
Added CloudFormation workaround for null values in event patterns
Security assessment
Technical documentation update about template syntax. No security implications identified.
Diff
diff --git a/eventbridge/latest/userguide/eb-event-patterns-null-values.md b/eventbridge/latest/userguide/eb-event-patterns-null-values.md index 885938394..a07620566 100644 --- a//eventbridge/latest/userguide/eb-event-patterns-null-values.md +++ b//eventbridge/latest/userguide/eb-event-patterns-null-values.md @@ -4,0 +5,2 @@ +Using null values in AWS CloudFormation templates + @@ -56,0 +59,12 @@ Null values and empty strings are not interchangeable in pattern matching. An ev +## Using null values in AWS CloudFormation templates + +AWS CloudFormation does not allow `null` values in templates. If you define an event pattern with a null value using YAML or JSON object syntax, the template validation fails with the error: `'null' values are not allowed in templates`. + +To work around this limitation, specify the `EventPattern` property as a JSON string instead of a YAML or JSON object. The following example shows how to match on null values in a AWS CloudFormation template: + + + MyRule: + Type: AWS::Events::Rule + Properties: + EventPattern: '{"detail":{"responseElements":[null]}}' +