Practise the core AWS EventBridge vocabulary — event buses, event pattern matching with content filtering, schema registry, EventBridge Pipes for point-to-point integrations, and target routing.
0 / 5 completed
1 / 5
What is an event bus in AWS EventBridge?
An event bus is the central routing component in EventBridge. The default bus receives events from AWS services; custom buses handle application events; partner buses receive events from SaaS providers. Rules on the bus match incoming events and fan them out to one or more targets.
2 / 5
What does an event pattern in an EventBridge rule do?
Event patterns use partial JSON matching — a pattern like {"source":["aws.s3"],"detail-type":["Object Created"]} matches any event where those fields have those values. Patterns support prefix matching, numeric ranges, exists checks, and anything-but negation.
3 / 5
What is the EventBridge Schema Registry?
The Schema Registry automatically discovers event schemas from activity on an event bus and stores them as OpenAPI 3 or JSONSchema Draft4 documents. Developers can download generated code bindings (Java, Python, TypeScript) so their applications use typed event objects rather than raw JSON maps.
4 / 5
What do EventBridge Pipes provide that standard EventBridge rules do not?
EventBridge Pipes connect a source (SQS, Kinesis, DynamoDB Streams, etc.) to a target with optional filtering and an enrichment step, all configured declaratively. Unlike rules on an event bus, Pipes are point-to-point and handle polling, batching, and partial failure retries for streaming sources.
5 / 5
What is content filtering in an EventBridge event pattern?
Content filtering refers to the rich matching operators available in EventBridge event patterns. Beyond exact string equality, you can match with {"prefix": "order-"}, {"numeric": [">", 100]}, {"exists": false}, and {"anything-but": ["ERROR"]}, enabling fine-grained routing logic without Lambda enrichment.