The Amazon Eventbridge is a serverless service that has become extremely popular recently. It allows users to route incoming events in real-time. Using this service, it is also possible to direct centralized even streams to SaaS tools and employ cross-account notifications within AWS.
Read on to discover how you can use EventBridge to centralize all AWS events.
What is EventBridge?
Before we proceed to learn about the centralization of AWS events, let’s first understand what EventBridge is.
A simple explanation would be that Amazon EventBridge is the updated version of the AWS CloudWatch Events service. However, in this case, the service is serverless. You can use the event bus to carry out multiple tasks that are based on incoming events with the account. The best part is that everything is performed in real-time.
But there is more. With EventBridge, all implementations can be customized, which is one of the most redeeming features of all.
In the case of CloudWatch, only the default event buses could be leveraged. Moreover, it also came with very few integration options.
Some of the most highlighted features of EventBridge include:
- Customization of multiple event buses for different end-use applications
- Parallel processing of several events on a single bus by the configuration of a range of rules
- Ability to send events between different AWS regions and accounts
Integration with SaaS
One of the most impressive things about Amazon EventBridge is that it allows users to integrate numerous third-party SaaS vendors. What’s amazing is the fact that it has nearly 34 verified vendors.
So, how can you use EventBridge to centralize all AWS events?
Well, for starters, all event buses can be connected to a SaaS vendor with the help of the supported integrations. Some of the most popular SaaS vendors include:
When working with these supported platforms, users can carry out customized actions that are based on sent data to and from EventBridge.
Let’s take PagerDuty as an example. In this case, monitoring for a particular event pattern within an account is possible. Once a suitable match is found, a rule that uses a connection to PagerDuty can be leveraged. As a result, the operational team receives an immediate alert, allowing them to take necessary action.
Use of Default AWS Services with EventBridge
Another excellent quality of EventBridge is that it allows you to use countless default AWS services, including AppFlow, Auto Scaling, Bracket, Chime, CloudFormation, CodeDeploy, DevOps Guru, and EC2 Fleets, to name a few.
Let’s look at an example to understand better the working of EventBridge.
Suppose you have a basic internal application hosted on EC2. The compute runs on customized software housed within an S3 bucket.
In the past, it would take hours to update the software. But with EventBridge, it only takes several minutes. S3 PutObject API calls are leveraged from particular private buckets. These buckets are responsible for hosting customized software.
When you use EventBridge, you can create rules on the event bus to match patterns in a single place. After successfully generating the PutObject event, the EventBridge rule can be utilized. The rule looks out for the particular event on the S3 bucket.
Consequently, a target for the custom systems manager automation document is set. It uses the RunCommand to carry out updates on the targeted instances. In other words, all redundant and tedious tasks can be fully automated, allowing users to save plenty of time.
You could say that Amazon EventBridge allows you to deploy a serverless solution that results in automated updates of custom software.
AWS Organizations and EventBridge
As mentioned earlier, EventBridge leverages services using cross-region and cross-account models. Since this is such a powerful feature, it allows users to use EventBridge to take action. The best part is that the actions are taken based on the events occurring within their AWS Organization.
For instance, if you implement a resource policy in the security account on SecOps Event Bus, the relevant team will permit the accounts within the organization to send events to a centralized event bus.
Once the events have been sent, a pattern match can be placed using a rule. The rule then looks for particular events that may have been generated from organizational accounts. The accounts must be reviewed and addressed.
Let’s learn more about this feature with a detailed example. Suppose a junior engineer accidentally deletes an image from the Amazon Elastic Container Registry. The image is deleted from the development account.
Now SecOps wants only senior engineers to purge images instead of junior engineers.
In this case, they share the Event Bus with the organization to identify similar issues. After that, they generate a resource policy that allows organizations to transfer cross-account and cross-region events. Additionally, a rule is also implemented on all default event buses on child AWS accounts.
The default rule is a pattern match in the incoming ECR events for any DELETE action-type fields. After a match has been found, the event would be sent to the event bus of the SecOps accounts. Consequently, they can handle the event in any way they want.
The Bottom Line
Now you know how to use EventBridge to centralize all AWS events. The Amazon EventBridge is an upgraded and evolved version of the AWS CloudWatch Events. It offers countless advantages, such as automation and customization, that reduce the need for performing tedious tasks.
The best part is that it is compatible with countless SaaS vendors and allows you to use default AWS services.
Further blogs within this How You Can Use EventBridge to Centralize all AWS Events category.