EventBridge
I am an aspiring DevOps Engineer proficient with containers and container orchestration tools like Docker, Kubernetes along with experienced in Infrastructure as code tools and Configuration as code tools, Terraform, Ansible. Well-versed in CICD tool - Jenkins. Have hands-on experience with various AWS and Azure services. I really enjoy learning new things and connecting with people across a range of industries, so don't hesitate to reach out if you'd like to get in touch.
EventBridge
Formerly known as CloudWatch Events
Schedule: Cron jobs (scheduled scripts)
Event Pattern: Event rules to react to a service doing something
Trigger Lambda functions, send SQS/SNS messages…
EventBridge – Event Bus
An event bus receives events from sources, evaluates them using rules, and routes them to the appropriate targets.
Types of event buses:
Default event bus: Receives events from AWS services
Custom event bus: Receives events from custom applications and services
Partner event bus: Receives events from an event source created by a SaaS partner
Event buses support cross-account access
Cron Jobs: when creating an EB rule, we can select “Schedule” instead of event pattern to trigger an event based on a cron expression.
Can archive events (all or based on a filter) sent to an event bus to replay later
EventBridge is recommended for decoupling applications that reacts to events from third-party SaaS applications.
EventBridge – Schema Registry
Defines how the data is structured in the event bus
Schema can be versioned
EventBridge – Resource-based Policy
Manage permissions for a specific Event Bus
Example: allow/deny events from another AWS account or AWS region
Use case: aggregate all events from your AWS Organization in a single AWS account or AWS region