Truly well presented! ❤ Huge thanks, Nick! I hope you are making an updated version including recent development features/updates. 🙏🤞
@amazonwebservices Жыл бұрын
That's AWSome to hear! 🤝 ☁️ 😀
@melvinrmc20024 жыл бұрын
This rule example saved my day, i wasted two days to determine the Json structure when a lambda function has an eventbridge destination: It was a headache! The CatchAll-Rule rules! 🤭 Bad joke! 🙄, Great vídeo, thankyu
@Bill01029 ай бұрын
I'm completely absorbed in this. I had the privilege of reading something similar, and I was completely absorbed. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
@Tuscani2005GT4 жыл бұрын
This video POP does a really POP great POP job POP of explaining POP EventBridge POP. But seriously thanks for a great video.
@alexdorand3 жыл бұрын
I absolutely loved this.
@joepage30652 жыл бұрын
Great demo, thanks for sharing.
@sanjay47434 жыл бұрын
Is it possible to have a containerized web service as a subscriber for the event that are being filtered by Event Bridge ?
@nyxzbg3 жыл бұрын
Very well presented. Thank you!
@AsadShaikh-qc9ev5 жыл бұрын
Super awesome demo, loved it and love the service even more :)
@tristanjustice10713 жыл бұрын
Sorry to be so offtopic but does someone know of a way to log back into an Instagram account..? I somehow forgot my login password. I love any assistance you can give me.
@saiganeshmedide58494 жыл бұрын
Can I assume this to be the great replica of service bus in oracle??
@chychywoohoo3 жыл бұрын
partner event sources is cool, but there are very few
@orrlevinger3 жыл бұрын
i need to trigger a lambda in 24 hours after an event.. so i create a rule with cron expression per event. now i see this wont work if i have more than 100 events since this will break the 100 rules limit.. should migrate to step functions and use wait? or can i still use event bridge in some other way?
@KonstantinVlasenko5 жыл бұрын
Question. There is an architecture proposed: API->EventBridge->fork to [1. Kinesis-> S3][2. lambda A]..[N. lambda Z] In our case we don't anticipate a lot of events. But still want to keep audit in S3 bucket. Would the next architecture be more appropriate if we don't have to much events per second: API->S3->EventBridge-> fork to [1. lambda A]..[N. lambda Z]
@KonstantinVlasenko5 жыл бұрын
Have an answer: In latter case (w/o Kinesis, when event goes to EventBridge from S3) we wouldn't get an actual content of event. We'll get an S3 object information instead. Which is, obviously, not what we need. So the architecture proposed in the video is the only correct :) Hence feature request to EventBridge (expand S3 object content in case of S3 events as a source)
@focusotter3 жыл бұрын
@@KonstantinVlasenko Thanks for sharing! I was wondering why there was the need for firehose too!
@ramakrishnab83484 жыл бұрын
How do we monitor the events those doesn't match any rule or failed to process? Can we replay the failed events?
@jjbb70105 жыл бұрын
Is Jira or ServiceNow supported by chance?
@SreenathV3 жыл бұрын
Awesome tutorial...
@nikunj2044 жыл бұрын
Is it possible to send S3 upload events to EventBridge bus ? i.e. Client uploads file to S3 -> Event comes into EventBridge bus on its own. ?
@tracy_gao4 жыл бұрын
Seems need firehose to send event in middle
@mr.condoriano4 жыл бұрын
you should be able to do this with cloudwatch events and then send trigger to event bus with metadata of s3 object affected
@tracy_gao4 жыл бұрын
Hey, nice talk, can you provide the slides for downloading?
@arnold56214 жыл бұрын
Super Awesome
@hardikvasa64452 жыл бұрын
nice!
@rajsuresh96503 жыл бұрын
@23:51
@AniketKapse2 жыл бұрын
Ruined the entire video by breathing into the mic. Keep some distance ffs. So annoying
@nicksmit9592 жыл бұрын
Sorry!
@iflux8821 Жыл бұрын
Well, Nick did such a nice job in presenting the information that I quickly stopped to notice it. I would rather have Nick breathing heavily in the mic and keeping presenting that well than having clean sound and not providing such a clear and concise info 😂