EventBridge

Event buses, pattern matching, scheduled rules, archives, replay, API destinations.

fakecloud implements 57 of 57 EventBridge operations at 100% Smithy conformance.

Supported features

  • Event buses — default, custom, partner event sources
  • Rules — pattern matching on events, scheduled rules (cron and rate)
  • Targets — SNS, SQS, Lambda, CloudWatch Logs, Kinesis, Step Functions, HTTP, API Destinations
  • Archives — event archiving with retention
  • Replay — re-send archived events to targets
  • Connections — API connection management for HTTP targets
  • API destinations — outbound HTTP integrations
  • Pattern matching: full EventBridge pattern language including prefix, suffix, equals-ignore-case, wildcard, cidr (IPv4 and IPv6), numeric comparisons, exists, anything-but and $or, with AWS array semantics (an array of objects matches when any element matches; every matcher except exists: false requires the field to be present)

Protocol

JSON protocol. X-Amz-Target header, JSON body, JSON responses.

Introspection

  • GET /_fakecloud/events/history — list all events and deliveries
  • POST /_fakecloud/events/fire-rule — fire a specific rule manually. Body: {"busName": "...", "ruleName": "..."}

Cross-service delivery

  • EventBridge -> SNS / SQS / Lambda / Logs / Kinesis / Step Functions / HTTP — Rules deliver to targets on schedule or event match
  • EventBridge Scheduler — Cron and rate-based rules fire on schedule
  • Service events (S3, ECS, RDS, SES, Lambda destinations, Step Functions, Pipes, Scheduler): each event lands on a bus in the account that owns the emitting resource (or the account of a target bus ARN), carries that resource's account and region, and is matched by rules and captured by archives exactly like a PutEvents entry. A bus in another account takes the event only when its resource policy allows the source's role (or account) to events:PutEvents, the same rule PutEvents applies to cross-account callers (a bus without a policy accepts only its own account); a refused event is not stored and the source records a delivery failure (Step Functions fails the task with EventBridge.FailedEntry, Scheduler and Pipes retry / dead-letter).

Source