AWS eventbridge: Clarify numeric matching precision limits in EventBridge patterns
Summary
Replaces the old numeric matching range description with an explanation that values are compared as IEEE 754 binary64 doubles, exact integer matching is limited to ±2^53, and out-of-range values cause rule rejection or non-matching.
Security assessment
The change only corrects the documented numeric matching semantics and precision limits; it describes rule validation behavior but does not address any vulnerability, credential, or access control concern.
Evidence
+Numeric matching compares values as 64-bit double-precision floating-point numbers (IEEE 754 binary64), which limits the integers that can be matched exactly. Integers are matched exactly from -9,007,199,254,740,992 to 9,007,199,254,740,992 (-253 to +253). If a value falls outside this range or otherwise cannot be represented exactly as a double, EventBridge rejects the rule at creation time when the value is used in a numeric comparison, and an event carrying such a value is not treated as a number and will not match a numeric comparison.
Diff
diff --git a/eventbridge/latest/userguide/eb-create-pattern-operators.md b/eventbridge/latest/userguide/eb-create-pattern-operators.md index c13fcb8be..5ec3e2926 100644 --- a//eventbridge/latest/userguide/eb-create-pattern-operators.md +++ b//eventbridge/latest/userguide/eb-create-pattern-operators.md @@ -212 +212 @@ For more information, see Matching using wildcards. -Numeric matching works with values that are JSON numbers. It is limited to values between -5.0e9 and +5.0e9 inclusive, with 15 digits of precision, or six digits to the right of the decimal point. +Numeric matching compares values as 64-bit double-precision floating-point numbers (IEEE 754 binary64), which limits the integers that can be matched exactly. Integers are matched exactly from -9,007,199,254,740,992 to 9,007,199,254,740,992 (-253 to +253). If a value falls outside this range or otherwise cannot be represented exactly as a double, EventBridge rejects the rule at creation time when the value is used in a numeric comparison, and an event carrying such a value is not treated as a number and will not match a numeric comparison.