Amazon AWS Certified SysOps Administrator Associate – Monitoring, Auditing and Performance Part 5

9. [DVA] EventBridge Overview

Now, let’s talk about Amazon event bridge. So what is EventBridge? Very simply, it is the next evolution of your Cloud Watch events. So by default when you use CloudWatch events, you’re using the default Event bus and that’s the bus generated by AWS services within your account. So this is your Cloud Watch events. But in EventBridge we have added multiple buses.

So the first one is called the Partner Event bus and this is to receive events not from AWS but from software as a service providers or applications. And so for example, this could be Zen desk data dog segment of zero and so on. So that means that other parties, not yourself, not your services, other parties can send events into your AIDS account and that means you can react to these events in real time.

You can also define your own custom Event bus. And that means that your own applications can publish their own events and have other applications react to these events. So that extends the power of CloudWatch events to not just the default Event bus, but now partner Event buses and custom events buses. So these Event buses can be accessed by other illness accounts as well.

So it’s possible to do cross account Event buses and then you create rules which are very similar to CloudWatch Event rules. You can rules to how do you want to process these events. So the next thing about Event Bridge that’s really cool is the Schema Registry. So EventBridge has the capability to actually analyze the events in your buses and then infer the Schema from it. Schema means how the data is structured. And so the Schema registry allows you then to generate code for your application. And these applications will know in advance how the data will be structured in the Event bus. And this will save you a lot of time and add safety.

So this is what the Schema registry will look like. And we’ll see this in the hands on as well. And as we can see from the script shot on the right hand side, we have versions. So these Schemas can be versions. So you can make your events evolve over time and then your Schemas will also evolve over time. So one question that you may have right now, and I know you may have it, is what is really the difference between Event Bridge and Cloud Watch events?

So EventBridge builds upon and extends Cloud Watch events and the documentation says that it actually uses the exact same service API and endpoint and it’s the exact same underlying service infrastructure. But they wanted to create a new service and a new name because there are some more extensions. So we have Event buses from your custom applications and also from your third party software as a service applications. And on top of it they have created this functionality of this keyma registry.

So EventBridge was created to mark the new capabilities. So a different name to mark the new capabilities and over time, that is a list vision. CloudWatch Events is not going to go away and it will still be supported, but the name will be phased out and replaced with EventBridge. So going into your exam, if you see CloudWatch Events or EventBridge, it’s sort of the same thing, except Event Bridge will have some added capability, such as third party software, service applications and custom event buses, as well as Schema registry. So that’s it for the overview of Amazon event bridge. Let’s go ahead, Indian, to see how we can practice it.

10. [DVA] EventBridge Hands On

Okay, so we are in Cloud Watch events and in here I have two roles already created. But let’s go into the Event Bridge service. So we’ll go into Event Bridge to see what EventBridge is all about. So I’m going with this UI, but on the left hand side I can just go click on Event buses and I can see that already have a default event bus and that’s the one we’ve been using so far. But I can go ahead also and create my custom event bus bus. So if I create my custom event bus, I’ll call it Custom Bus. I can see I can create my own custom event bus and also give access to it if I wanted to for other alias accounts, which I won’t do. I will just click on Create and here we go. I have my custom Event bus and this is where my own application can publish events too. Okay, so I’m going to go ahead and delete it because I will need it. But this is great. Next we have partner event sources. So this is the partners of Amazon event bridge.

Currently there’s 26, there are 26, but they can be a lot more very soon. And so for each partner you can have set up instruction, for example, semantic. So we need to copy the elastic account information, create the event bus for semantic and the instructions are on the semantic website and finally finish and we should see a new event bus in our account. So this is amazing. And so let’s go and have a look at the default event bus. So if I click on it, I can see my Event bus in here and I can look at its rules. So if I go on the left hand side and click on rules, I can see that for my Event Bus default, I have two rules and these are the exact same rules that we saw into Cloud Watch events.

As I said, EventBridge and Cloud Watch events are built on the same infrastructure. So we can look at this rule, for example, this code pipeline rule that we had created to detect changes that happen in code pipeline. We can look at the event pattern and then we can look at the targets and the tags. So let’s go ahead and try to recreate this. So we’ll go and create a rule and I will say demo code pipeline and then I will delete it afterwards. Then the pattern.

So do we want to be on the schedule? And we can say how many hours or every how many hours, every many days or a cron expression. So this is if you want to have a schedule for your Cloud Watch sorry, for your Amazon Event Bridge rules or an event pattern. And then we can define either a custom pattern or a predefined by service. And so I can look at the service provider, for example AWS. And then I can look at could pipeline and then I can look at event type all events or pipeline execution state change something like this. So as we can see in the service provider, not only we had AWS but we also had service partners so we can react to events from our partner event sources, which is I think great improvement over Amazon over Cloud Watch events.

So here this event pattern is written in JSON form and I can look at a sample of events which is exactly the same as what we had in Cloud Watch events. Finally I can select the event bus. So for this I will choose the illness default event bus and then I can look at the targets. So the target can be anything I want. I can have multiple targets and for example, we have a list of all the targets here. So it could be an SNS topic, an Sqsq, it could be a lambda function and so on. So it could be an SNS topic. Then I need to select the topic. I want to create tags and then click on Create and that’s it, it’s the exact same setup. But I want to show you once how this works so you can have a good idea of how Cloud Event Bridge is similar to Cloud Watch events.

And then finally, one difference though is that we have now the Schema registry. So in this Schema registry we can get started with the schemas and we can see we have so many schemas in here, so we can search among all the schemas or we can get information for the schemas by AWS or Schemas that we discover. So if we have our own event buses, we can discover schema in it or create our own custom schema registry. So I’m going to go to all schema’s and I’m going to look for the code pipeline one. So I’ll type code, pipeline, and hopefully that works. No, it does not work because I have to type AWS code pipeline. The search is not optimal right now.

And so here I have a code pipeline that I’m going to click on. So this one called Code Pipeline. Action. Execution. State change. The number of version is one. So I’m version one, the schema I type is open API 3. 0 and here I have access to the entire version one of the schema. So as you can see, it’s quite detailed and it explains what every field I can expect out of an event coming from code pipeline for this event type, which is very handy, but this would be even more handy if I had code.

So I can download code bindings and I can say okay, I want to download the code binding for Java, Python or TypeScript and this will help me speed up my code when I start programming against the events in CloudWatch Events or Amazon Event Bridge. Okay, so they’re very cool. I hope you liked this this was just a quick overview of Event bridge, but as we can see, it’s just an improvement over cloud watch events. And that should be all you need to know going into your exam. So that’s it. I will see you in the next lecture. It’s.

• Category: Uncategorized