Links: 101 AWS SAA Index

  • These were previously known as CloudWatch Events. We can say EventBridge is the next evolution of CloudWatch. CloudWatch events are still there in the console but it is advised to use EventBridge. Over the time CloudWatch events will be replaced by EventBridge.

  • Event Pattern: Intercept events from AWS services (Sources). Some example sources are EC2 Instance Start, CodeBuild Failure, S3, Trusted Advisor etc.

  • These events can also be generated based on schedule or CRON. For example create and event every 4 hours. Now this can be chained with a lambda function.
  • A JSON payload is created from the event and then passed onto the target.
  • When we are using EventBridge events we are using the default event bus generated by AWS services.
  • We have multiple event buses in EventBridge
    • Partner event bus → receive events from SaaS service or applications (Zendesk, DataDog, Segment, Auth0...). This means other services can send events to my AWS account.
    • Custom event bus → for our own applications.
  • Event buses can be accessed from other AWS accounts as well using resource based policies of EventBridge.
  • We create rules on how we want to process the events.
  • Schema Registry → know in advance how the data will look like and generate code in advance
  • The main difference between EventBridge and CloudWatch Events are the buses and schema registry.
Go for EventBridge over SQS when the question mentions 3rd SaaS party applications.

SQS works well for decoupling applications. It does not directly integrate with third-party SaaS services.

Last updated: 2022-05-19