Amazon EventBridge Event Patterns Demo | Custom EventBus

In this demo video, we will learn how to invoke different targets from Amazon EventBridge custom EventBus based on different values on the fields of the message, using event pattern rules.
Discounted Link for my Udemy Kubernetes course
▶ www.udemy.com/...
Please Subscribe
▶ / @cloudwithraj
*Connect with me*
🤳 Instagram: / cloudwithraj
🐦Twitter: / cloudwithraj
🖼 Facebook: / cloudwithraj
🏢 LinkedIN: / rajdeep-sa-at-aws
👩🎓**My Courses - Message me at Twitter/FB for discount coupons**
Discounted Link for my Kubernetes course: www.udemy.com/...
Discounted Link for my Serverless Course: www.udemy.com/...
Discounted Link for my CloudFormation, CDK with Devops, Interview Guide Course: www.udemy.com/...
#AmazonEventBridge #CustomEventBusDemo #EventPatterns

[@SEASLU]

Nice tutorial, Raj. In python code, you have "Detail" with capital D, but the rule has "detail" with lower case d. Are events' keys converted to lower case or camel case? Is it specified somewhere? Also, looks like pattern matching is exact matching, and missing fields are matched using wildcard. But you can't match a field using wildcard, e.g. {detail: { name: "raj*" } }, right? Also, what happens when events are delivered to target but target failed to process events? How are errors handled there?

[@cloudwithraj]

Amazing eye Khanh. The field "detail" is NOT case sensitive but the actual rule is. So if you send in the actual message "Married":"True" or "MARRIED":"TRUE" it won't invoke the target. You can't do wildcard but you can do begins with (using prefix parameter) or exists. EventBridge delivers the messages asynchronously compare to SQS. So if EventBridge delivers to the Lambda and lambda fails to process, it'd go to Lambda DLQ (which is not true if SQS message triggered Lambda). If Lambda DLQ is not enabled then it'd get discarded. Hope this helps!)

[@SEASLU]

@@cloudwithraj Thank you. That makes sense. Btw, I never considered DLQ feature for lambda before. That can be handy

[@soumyadipchatterjee2267]

Awesome content Raj ! I found each content informative on each other ❤😊

[@cloudwithraj]

Happy to hear that!

[@HoussemYahiaoui]

That was really interesting, please make more of those

[@arunkumara9398]

Thanks..It is great for beginners..!

[@Aidanhyland]

Great stuff. Appreciate the Eventbridge demos.

[@vikaskoppineedi862]

Exactly what I was looking for. So a quick question, if the events cannot be delivered event after a rule match, like may be the destination lambda got deleted, can the events be delivered to an SQS or any other destination ?

[@soumyajeetnayak5584]

Thanks for the Video. Learned something new

[@nikolais9297]

Thanks for this example, Raj!

[@karan_1993]

Thanks Raj for the video. You said that sns, sqs cannot do message based filtering. But if I am not wrong, we can put subscribption filter policy for that subscriber ( written in JSON and it has to be in an array ). With the help of message attribute in SNS message, the filter policy can work on that

[@cloudwithraj]

Hey Karan, what I meant is SNS can’t read inside the message and can’t filter based on the field values inside the message. It can only do based on attributes attached to the message whereas eventbridge can filter based on the content of the nessage

[@iamnoob7593]

AMAZING!!!!!!!!!!!!!!

[@MatiasNovillo1]

Excellent!

[@marianek8092]

Great explanation

[@shahmirjadoon3587]

Thanks a lot Raj for this awesome content.
Will you kindly make another video where you can explain how to create custom rules in the event bridge with AWS-SDK or lambda function?

[@venkatagudala5172]

Nice video Raj, but I could achieve the same using lambda that put item in different topics (SNS) based on the fields in the details section, Right? I am curious.

[@cloudwithraj]

With SNS, you can only use metadata (attributes attached to the message) and NOT the actual values inside the message. Also EventBridge supports more rule validation (AND, OR, EXISTS, ANYTHING BUT etc.). Hope this helps.

[@iaroslavdavydiak6439]

Awesome👍. You are doing a great job 😍

[@cloudwithraj]

Thank you so much 😀

[@galeop]

8:15 Is this what sets EventBridge aside from SNS Filtering ? I.e. :
- EvenBridge can filter to which subscribers a topic message will be sent to, based on values *within the message body*;
- While SNS Filtering can only do that based on the value of attributes attached to the message (but not within the message body)
Correct?

[@cloudwithraj]

You are correct

[@galeop]

thanks!

[@jrodrig9212]

Really good stuff

[@cloudwithraj]

Appreciate it

[@avranilbasu8383]

Can we filter events based on the timestamp to run the target only on a specific day of week for an event which is published daily and ignore the event for other days

[@Quilz06]

Sir can event bridge do things like triggering a lambda function from s3 only when the 6th file of the day is uploaded to the bucket?

[@Vegetakhan]

Right now SNS supports MessageBody field based filters.

[@adityagolpalliwar1408]

How to trigger different target based on particular field value???

[@nathansu9454]

where is github link?

[@nnagaaddagarla9438]

Can you please make a video on how to invoke to api gateway from event bridge

[@cloudwithraj]

I will keep this in mind for future videos. For this you need to use API Destination from EventBridge