Study Guides/AWS Cybersecurity Notes/AWS EventBridge

AWS Eventbridge

Eventbridge enables imlementation of loose coupling.

Services have little dependnece on each other.

Changes to one component does not have a massive impact on the other.

Provides greater flexability.

Eventbridge is serverless.

Allows you to connect aws services and components with 3rd party systems.

• Events are pushed to an event bus.

• Rules trigger the forwarding of events to targets.

Event Driven Architecture

The sysem responds asynconiosly.

In an event driven system there are three main components:

• Producers - generate events.

⬇️

• Event bus - communcation channel

⬇️

• Consumers - resond to events.

Why EDA

• Scaleable

• Flexible

• Responsive

• Resilient

Event Buses

The event bus is a pipeline that recives messages.

• The default event bus is the one that recives messages from AWS services.

• Custom event buses can be created - these can recive messages from AWS accounts other than the one of the event bus.

• Partner event busses can send / recive messages from SaaS partners.

• Up to 300 rules can be on an event bus.

• If you need more than 300 rules then add a custom event bus.

Events on a scedule

Tasks can be run on a scedule in event bridge.

This can be used to do things such as send weekly reminders.