1 00:00:00,120 --> 00:00:02,520 ‫So now let's talk about Amazon EventBridge, 2 00:00:02,520 --> 00:00:04,920 ‫and it used to be called CloudWatch Events. 3 00:00:04,920 --> 00:00:06,180 ‫So if online, you see CloudWatch Events, 4 00:00:06,180 --> 00:00:08,820 ‫think about Amazon EventBridge and vice versa, 5 00:00:08,820 --> 00:00:10,680 ‫but EventBridge is the new name. 6 00:00:10,680 --> 00:00:12,540 ‫So with EventBridge, you can react to events 7 00:00:12,540 --> 00:00:15,600 ‫happening within your AWS accounts. 8 00:00:15,600 --> 00:00:18,600 ‫And one use case for them is to schedule cron jobs. 9 00:00:18,600 --> 00:00:22,350 ‫So you want to have a script scheduled on a regular basis. 10 00:00:22,350 --> 00:00:26,280 ‫For example, in EventBridge, you can create a rule that says 11 00:00:26,280 --> 00:00:29,700 ‫that every one hour you should have an event created 12 00:00:29,700 --> 00:00:32,190 ‫and that event will trigger a script 13 00:00:32,190 --> 00:00:34,080 ‫running on a Lambda function. 14 00:00:34,080 --> 00:00:37,740 ‫Effectively, you've done a serverless cron job. 15 00:00:37,740 --> 00:00:39,420 ‫But you can also not just react 16 00:00:39,420 --> 00:00:41,790 ‫to events happening every hour, 17 00:00:41,790 --> 00:00:44,910 ‫we can react to a service doing something. 18 00:00:44,910 --> 00:00:48,360 ‫For example, say you wanted to give alerts 19 00:00:48,360 --> 00:00:51,150 ‫to your security team whenever someone 20 00:00:51,150 --> 00:00:53,640 ‫is going to log in using the root user 21 00:00:53,640 --> 00:00:56,130 ‫because, well, the rule is that you should not reuse 22 00:00:56,130 --> 00:00:58,950 ‫the root user or only very rarely. 23 00:00:58,950 --> 00:01:00,870 ‫So maybe we want to react 24 00:01:00,870 --> 00:01:03,630 ‫to the IAM root user sign-in events 25 00:01:03,630 --> 00:01:06,690 ‫and then send this into an SNS topic 26 00:01:06,690 --> 00:01:09,480 ‫that is combined with email notifications. 27 00:01:09,480 --> 00:01:11,310 ‫In that case, whenever someone signs in, 28 00:01:11,310 --> 00:01:12,600 ‫we will receive an email. 29 00:01:12,600 --> 00:01:15,360 ‫So you can create a lot of these different integrations 30 00:01:15,360 --> 00:01:17,550 ‫all using Amazon EventBridge. 31 00:01:17,550 --> 00:01:21,420 ‫And you can, as the destination, trigger Lambda functions, 32 00:01:21,420 --> 00:01:24,120 ‫send SNS and SQS messages, and so on. 33 00:01:24,120 --> 00:01:25,890 ‫Actually, you can do all these things. 34 00:01:25,890 --> 00:01:27,720 ‫I just wanted to give you a quick example. 35 00:01:27,720 --> 00:01:29,850 ‫You don't need to linger on this slide, okay. 36 00:01:29,850 --> 00:01:32,460 ‫But the sources can be anything you want. 37 00:01:32,460 --> 00:01:34,890 ‫Could be EC2 Instances, CodeBuild, S3 Event, 38 00:01:34,890 --> 00:01:36,570 ‫Trusted Advisor, and so on. 39 00:01:36,570 --> 00:01:38,850 ‫There's a lot and, of course, a schedule. 40 00:01:38,850 --> 00:01:42,210 ‫It goes into EventBridge, and from EventBridge, you can send 41 00:01:42,210 --> 00:01:44,760 ‫and trigger many different kinds of destinations. 42 00:01:44,760 --> 00:01:47,250 ‫Would it be for compute, for integration, 43 00:01:47,250 --> 00:01:49,260 ‫orchestration, maintenance, and so on? 44 00:01:49,260 --> 00:01:52,623 ‫And what I've shown you here is just a little sample. 45 00:01:53,640 --> 00:01:56,610 ‫Finally, EventBridge has more capability. 46 00:01:56,610 --> 00:01:59,820 ‫So what I've shown you is called the default event bus. 47 00:01:59,820 --> 00:02:03,450 ‫And these are events happening from within AWS Services, 48 00:02:03,450 --> 00:02:06,180 ‫or, for example, your schedules. 49 00:02:06,180 --> 00:02:08,850 ‫But it is possible for you to receive events 50 00:02:08,850 --> 00:02:10,650 ‫from partners of AWS. 51 00:02:10,650 --> 00:02:12,960 ‫For example, if you're using Zendesk, or Datadog, 52 00:02:12,960 --> 00:02:15,870 ‫or others that are partnered with AWS, 53 00:02:15,870 --> 00:02:17,940 ‫then they can send their own events 54 00:02:17,940 --> 00:02:21,510 ‫into your account through a partner event bus, 55 00:02:21,510 --> 00:02:23,670 ‫and, therefore, you can react to events 56 00:02:23,670 --> 00:02:26,190 ‫happening outside of AWS as well. 57 00:02:26,190 --> 00:02:29,910 ‫And finally, you could plug in your own custom applications 58 00:02:29,910 --> 00:02:33,660 ‫that would send their own event to your own custom event bus 59 00:02:33,660 --> 00:02:35,790 ‫to write any kind of integration you want 60 00:02:35,790 --> 00:02:38,103 ‫and be really able to customize everything. 61 00:02:38,940 --> 00:02:40,860 ‫EventBridge also has more capability. 62 00:02:40,860 --> 00:02:43,800 ‫There is the Schema Registry to model the events schema 63 00:02:43,800 --> 00:02:46,290 ‫to see what it looks like, the data types and so on. 64 00:02:46,290 --> 00:02:49,980 ‫You can also archive all the events sent to an event bus 65 00:02:49,980 --> 00:02:52,080 ‫indefinitely or for a set period, 66 00:02:52,080 --> 00:02:54,930 ‫and then you can replay these archived events. 67 00:02:54,930 --> 00:02:57,540 ‫But I think that for the cloud practitioner exam 68 00:02:57,540 --> 00:02:58,373 ‫you know more than enough. 69 00:02:58,373 --> 00:02:59,460 ‫Again, you need to remember, 70 00:02:59,460 --> 00:03:01,710 ‫conceptually, what is Amazon EventBridge? 71 00:03:01,710 --> 00:03:02,970 ‫And now, I think you do. 72 00:03:02,970 --> 00:03:04,740 ‫Okay, that's it for this lecture. 73 00:03:04,740 --> 00:03:07,740 ‫I hope you liked it, and I will see you in the next lecture.