Study guide

2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting

AWS Certified CloudOps Engineer – Associate SOA-C03

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Monitoring & Observability Infrastructure

1.1 Configuring Workload Observability 1.2 CloudWatch Agent Architecture & Deployment 1.3 Metric Alarms, Anomaly Detection & Composite Alarms

2 Chapter 2: Alarms, Dashboards & Event-Driven Remediation

2.1 CloudWatch Dashboards & Multi-Account Visibility 2.2 Notification Architecture & Alarm Invocation 2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting 2.4 Automated Remediation with Systems Manager & Lambda

3 Chapter 3: Performance Optimization for Compute, Storage & Databases

3.1 EC2 & Compute Performance Optimization 3.2 Amazon EBS Performance Metrics & Volume Tuning 3.3 S3 Performance Strategies & Data Transfer 3.4 Shared Storage (EFS/FSx) & Database Performance

4 Chapter 4: Compute & Database Scalability and Elasticity

4.1 EC2 Auto Scaling Policies & Elasticity 4.2 Auto Scaling Advanced Operations: Warm Pools & Lifecycle Hooks 4.3 Dynamic Scalability Through Caching 4.4 Managed Database Scaling: RDS, Aurora & DynamoDB

5 Chapter 5: High Availability, Fault Tolerance & Load Balancing

5.1 Elastic Load Balancing (ALB/NLB) Configuration & Troubleshooting 5.2 Route 53 Health Checks & DNS Failover 5.3 Multi-AZ Architecture & Fault-Tolerant Deployments

6 Chapter 6: Backup, Data Protection & Disaster Recovery

6.1 Centralized Backup Automation & AWS Backup 6.2 Database Restore Strategies & RTO/RPO Management 6.3 Storage Versioning, Replication & Immutability 6.4 Disaster Recovery Patterns & Multi-Region Resilience

7 Chapter 7: Infrastructure as Code with CloudFormation & AWS CDK

7.1 CloudFormation Foundations & Resource Modeling 7.2 Managing Stacks, Drift Detection & Change Sets 7.3 Infrastructure as Code with AWS CDK 7.4 Identifying & Remediating Deployment Failures

8 Chapter 8: Multi-Account Provisioning, Containers & Third-Party IaC

8.1 Golden Images with EC2 Image Builder & Amazon ECR 8.2 Multi-Account & Multi-Region Resource Sharing 8.3 Deployment Strategies & Container Deployments 8.4 Third-Party Automation with Terraform & Git Workflows

9 Chapter 9: Systems Manager & Event-Driven Operations Automation

9.1 AWS Systems Manager Core Management & Run Command 9.2 Systems Manager Patch Manager & Session Manager 9.3 Event-Driven Operations Automation

10 Chapter 10: Identity, Access Management & Governance

10.1 Advanced IAM Policies, Roles & Policy Conditions 10.2 Auditing Access with CloudTrail Lake & IAM Access Analyzer 10.3 Multi-Account Security: Organizations, SCPs & Identity Center 10.4 Compliance Enforcement with AWS Config & Conformance Packs

11 Chapter 11: Data Security, Encryption & Vulnerability Management

11.1 Data Classification & Amazon S3 Security 11.2 Encryption at Rest with AWS Key Management Service (KMS) 11.3 Encryption in Transit with AWS Certificate Manager (ACM) 11.4 Secrets Management & Centralized Security Findings

12 Chapter 12: VPC Architecture, Endpoints & Network Protection

12.1 VPC Core Architecture, Subnetting & High Availability NAT 12.2 Private Network Connectivity: VPC Endpoints & Peering 12.3 Network Protection & Edge Security Auditing

13 Chapter 13: DNS, Route 53 Routing & Content Delivery

13.1 DNS Architecture & Route 53 Resolver for Hybrid Clouds 13.2 Route 53 Advanced Routing Policies & Query Logging 13.3 Global Content & Service Distribution: CloudFront & Global Accelerator

14 Chapter 14: Network Troubleshooting, Traffic Analysis & Hybrid Connectivity

14.1 VPC Configuration Troubleshooting & Analysis Tools 14.2 Network Traffic Analysis: VPC Flow Logs & Log Analytics 14.3 CloudFront Caching & Hybrid Connectivity Troubleshooting

2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting

Key Takeaways Explain This Topic AI

Amazon EventBridge routes real-time events across three bus types: Default (AWS services), Custom (internal microservices), and Partner (third-party SaaS platforms like Datadog and PagerDuty).

Event patterns match incoming JSON event envelopes using content-filtering operators including exact match, prefix match, numeric range, exists, and anything-but negation.

Input Transformers format payloads at the target using inputPathsMap to extract JSON attributes and inputTemplate to assemble human-readable alerts or API payloads without intermediate Lambda functions.

Target reliability is guaranteed through configurable retry policies (maximum event age up to 24 hours and retry attempts up to 185) paired with target-level Amazon SQS dead-letter queues (DLQs).

EventBridge rule troubleshooting relies on CloudWatch metrics (MatchedEvents, TriggeredRules, FailedInvocations), target IAM permissions, and event bus archiving and replaying for post-incident recovery.

Last updated: October 2026

2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting

Amazon EventBridge is the central serverless event bus service for modern cloud architectures. While CloudWatch alarms evaluate time-series metric thresholds, EventBridge reacts in real time to asynchronous state changes across AWS resources, custom applications, and SaaS partner platforms. For CloudOps engineers taking the SOA-C03 exam, mastering EventBridge requires a comprehensive understanding of event bus topologies, JSON event envelopes, complex event pattern filtering, payload transformations via Input Transformers, target retry policies, dead-letter queues (DLQs), and systematic event bus troubleshooting techniques.

Event Buses & The JSON Event Envelope

An EventBridge event bus is a pipeline that receives events, evaluates them against configured rules, and routes matching events to targets. EventBridge supports three types of event buses:

Event Bus Type Source of Ingress Events Typical Operational Purpose

Default Event Bus AWS services emitting state changes, AWS API call events via CloudTrail Standard system monitoring (e.g., EC2 state changes, Auto Scaling lifecycle hooks, GuardDuty findings).

Custom Event Bus Custom internal applications, microservices, container workloads Isolating line-of-business domain events (e.g., order processing, payment events, CI/CD telemetry).

Partner Event Bus Third-party SaaS providers (e.g., Datadog, PagerDuty, MongoDB Atlas, Auth0) Ingesting external SaaS operational alerts directly into AWS architectures without custom webhooks.

  • All events flowing through EventBridge follow a standardized JSON envelope structure: {
  • "version": "0",
  • "id": "fe8d8442-1234-5678-abcd-1234567890ab",
  • "detail-type": "EC2 Instance State-change Notification",
  • "source": "aws.ec2",
  • "account": "123456789012",
  • "time": "2026-09-04T18:00:00Z",
  • "region": "us-east-1",
  • "resources": ["arn:aws:ec2:us-east-1:123456789012:instance/i-0123456789abcdef0"],
  • "detail": {
  • "instance-id": "i-0123456789abcdef0",
  • "state": "shutting-down"
  • }
  • }

The top-level fields ( source , detail-type , time , account , region , resources ) provide standard routing metadata, while the detail object contains the payload generated by the emitting service.

Rule Pattern Matching & Content Filtering

EventBridge rules use JSON event patterns to evaluate whether an incoming event should trigger configured targets. An event pattern has the same structure as the event it matches; an event matches a pattern if all fields present in the pattern exist in the event with matching values.

EventBridge provides sophisticated content-filtering syntax:

Exact String Matching : Matches exact string values in an array: {"detail": {"state": ["running", "stopped"]}}

Prefix Matching : Matches values starting with a specified prefix: {"detail": {"bucket": {"name": [{"prefix": "prod-data-"}]}}}

Numeric Matching : Evaluates numbers using relational operators ( = , > , >= , < , <= , or range intervals): {"detail": {"memoryUsage": [{"numeric": [">=", 85]}]}}

Exists Matching : Checks whether a JSON key is present regardless of its value: {"detail": {"compromisedCredentials": [{"exists": true}]}}

Anything-But Matching : Negates values, matching anything except the specified list, prefix, or suffix: {"detail": {"state": [{"anything-but": ["running", "pending"]}]}}

Suffix Matching : Matches the trailing characters of a string (e.g., matching file extensions like .tar.gz ).

IP Address Matching : Matches IPv4 or IPv6 CIDR blocks (e.g., {"cidr": "10.0.0.0/24"} ).

When designing patterns, engineers must remember that arrays inside an event pattern indicate an OR relationship (matching any element), whereas distinct top-level keys enforce an AND relationship.

Event Payload Transformation: Input Transformers

By default, EventBridge delivers the entire raw JSON event envelope to targets. When sending alerts to human-facing channels (such as Amazon SNS topics subscribed to email or Slack webhooks), raw JSON is difficult to read. Furthermore, API targets (like AWS Systems Manager Automation or Step Functions) often require payloads formatted in a specific schema.

The Input Transformer solves this problem without requiring an intermediate AWS Lambda function. It operates in two declarative steps:

Input Paths Map ( inputPathsMap ) : Extracts values from the incoming event JSON using JSONPath expressions and assigns them to local variables.

Input Template ( inputTemplate ) : Constructs a customized string or JSON output, referencing the variables enclosed in <variable> tags.

  • For example, to transform an EC2 state-change event into a readable alert: {
  • "InputTransformer": {
  • "InputPathsMap": {
  • "instance": "$.detail.instance-id",
  • "state": "$.detail.state",
  • "time": "$.time",
  • "account": "$.account"
  • },
  • "InputTemplate": "\"ALERT: EC2 Instance <instance> in account <account> changed state to <state> at <time>.\""
  • }
  • }

The resulting string is delivered cleanly to the SNS topic or webhook, improving readability and eliminating extra compute costs.

Target Retry Policies & Dead-Letter Queues (DLQs)

When EventBridge triggers a target (such as an AWS Lambda function, SQS queue, Kinesis stream, or SSM Automation runbook), invocation can fail due to target throttling, network failures, or misconfigured permissions.

Engineers configure two critical resilience parameters on each target:

Maximum Age of Event : Defines how long EventBridge will retain and retry an unhandled event (from 1 minute up to 24 hours; default is 24 hours).

Maximum Retry Attempts : Sets the number of retry attempts before discarding the event (from 0 to 185 attempts; default is 185).

To guarantee zero data loss, engineers attach an Amazon SQS Dead-Letter Queue (DLQ) to the target. If an event cannot be delivered within the configured retry attempts or age limit, EventBridge sends the event to the target's DLQ along with error attributes ( ErrorCode , ErrorMessage ). Note that in EventBridge, DLQs are configured per target , allowing different targets on the same rule to have independent error handling.

Troubleshooting EventBridge Rules

When an expected event does not trigger a target, CloudOps engineers analyze key CloudWatch metrics for the AWS/Events namespace:

Metric Meaning & Troubleshooting Guidance

MatchedEvents Number of events matching the rule's event pattern. If zero, verify the event pattern syntax or check CloudTrail to confirm the event was emitted.

TriggeredRules Number of rules triggered. If MatchedEvents is positive but TriggeredRules is zero, check whether the rule is currently disabled.

Invocations Number of times targets were invoked by the rule.

FailedInvocations Number of times target invocations failed. Indicates target permissions issues, throttling, or invalid target parameters.

DeadLetterInvocations Number of failed events successfully forwarded to the target's DLQ.

Permissions & Security Policies

A common failure mode is missing target permissions. EventBridge interacts with targets using two distinct permission models:

Resource-based policies : Used when invoking AWS Lambda, Amazon SNS, Amazon SQS, or Amazon CloudWatch Logs. The target resource's policy must grant events.amazonaws.com permission to invoke it.

IAM Service Roles : Required when triggering targets that do not support resource-based policies, such as AWS Systems Manager Automation, AWS Step Functions, or AWS CodeBuild. The IAM role must trust events.amazonaws.com and possess permissions to execute the target API (e.g., ssm:StartAutomationExecution ).

Event Archiving & Replaying

EventBridge includes native Event Archiving and Replaying . CloudOps engineers create an event archive on an event bus with a specified retention period (or indefinite retention). If a bug in a downstream consumer or an outage causes events to be processed incorrectly, engineers can fix the consumer logic and initiate an Event Replay , specifying a historical time window. EventBridge replays all archived events matching the bus or rule, enabling seamless disaster recovery and historical backfills.