EventBridge Rules, Targets, and Schemas

In the previous lesson, we introduced Amazon EventBridge and its core concepts. Now we go deeper into the three pillars that make EventBridge a powerful event router: rules for matching events, targets for processing them, and schemas for documenting and validating event structure.

---

Advanced Rule Patterns

Combining Multiple Conditions

Event patterns support combining conditions with implicit AND logic. Every field in the pattern must match for the rule to fire.

{
  "source": ["order-service"],
  "detail-type": ["OrderPlaced"],
  "detail": {
    "country": ["UK"],
    "total": [{"numeric": [">=", 50]}],
    "paymentMethod": ["credit-card", "debit-card"]
  }
}

This matches events where:

• Source is order-service AND
• Detail type is OrderPlaced AND
• Country is UK AND
• Total is >= 50 AND
• Payment method is either credit-card or debit-card

OR Logic Within a Field

Within a single field, multiple values act as OR:

{
  "detail": {
    "status": ["shipped", "delivered"]
  }
}

This matches events where status is shipped OR delivered.

Negation with Anything-But

{
  "detail": {
    "environment": [{"anything-but": ["test", "staging"]}]
  }
}

This matches any environment except test and staging — useful for ensuring production-only rules.

Nested Field Matching