Deep Dive on Amazon EventBridge - AWS Online Tech Talks
HTML-код
- Опубликовано: 1 окт 2019
- Amazon EventBridge is a serverless event bus service that launched in July 2019. EventBridge makes it easy to build event-driven architectures by using data from your own applications, Software-as-a-Service (SaaS) applications, and AWS services. This tech talk will provide a deep dive on how events flow from internal and external applications through EventBridge, and how you can use rules and policies to route, transform, and control access to these events. We'll talk about how EventBridge integrates with other AWS services, like Amazon SQS and AWS Lambda, and help you get started building resilient, scalable, event-driven architectures in the cloud.
Learning Objectives:
- Learn how to build event-driven architectures with data from 3rd party SaaS apps
- Optimize event-driven applications for performance and availability
- Learn how to use rules to route and transform events Subscribe to AWS Online Tech Talks On AWS:
www.youtube.com/@AWSOnlineTec...
Follow Amazon Web Services:
Official Website: aws.amazon.com/what-is-aws
Twitch: / aws
Twitter: / awsdevelopers
Facebook: / amazonwebservices
Instagram: / amazonwebservices
☁️ AWS Online Tech Talks cover a wide range of topics and expertise levels through technical deep dives, demos, customer examples, and live Q&A with AWS experts. Builders can choose from bite-sized 15-minute sessions, insightful fireside chats, immersive virtual workshops, interactive office hours, or watch on-demand tech talks at your own pace. Join us to fuel your learning journey with AWS.
#AWS 
Наука
![AWS re:Invent 2022 - [NEW] EventBridge Pipes simplifies connecting event-driven services (API206)](http://i.ytimg.com/vi/xXGXCOc3cBs/mqdefault.jpg)
![AWS re:Invent 2022 - [NEW] EventBridge Pipes simplifies connecting event-driven services (API206)](/img/tr.png)
Truly well presented! ❤ Huge thanks, Nick! I hope you are making an updated version including recent development features/updates. 🙏🤞
That's AWSome to hear! 🤝 ☁️ 😀
I absolutely loved this.
Very well presented. Thank you!
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
Super awesome demo, loved it and love the service even more :)
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.
Great demo, thanks for sharing.
Awesome tutorial...
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
This video POP does a really POP great POP job POP of explaining POP EventBridge POP. But seriously thanks for a great video.
Super Awesome
Is it possible to have a containerized web service as a subscriber for the event that are being filtered by Event Bridge ?
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?
How do we monitor the events those doesn't match any rule or failed to process?
Can we replay the failed events?
Can I assume this to be the great replica of service bus in oracle??
Is Jira or ServiceNow supported by chance?
partner event sources is cool, but there are very few
nice!
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]
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)
@@KonstantinVlasenko Thanks for sharing! I was wondering why there was the need for firehose too!
Hey, nice talk, can you provide the slides for downloading?
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. ?
Seems need firehose to send event in middle
you should be able to do this with cloudwatch events and then send trigger to event bus with metadata of s3 object affected
@23:51
Ruined the entire video by breathing into the mic. Keep some distance ffs. So annoying
Sorry!
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 😂