# Amazon EventBridge

Amazon EventBridge is an event-driven integration service for building event-driven applications across AWS, existing systems, and SaaS applications.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Hijacking Amazon EventBridge for launching Cross-Account attacks

DevFeed: [Hijacking Amazon EventBridge for launching Cross-Account attacks](<https://devfeed.tech/articles/hijacking-amazon-eventbridge-for-launching-cross-account-attacks-15674.md>)

Original publisher: [Read original article](<https://developer.squareup.com/blog/hijacking-amazon-eventbridge-for-launching-cross-account-attacks>)

Author: Ramesh Ramani

Published: 2025-06-25T07:00:00Z

Content type: article

Language: en

Sources: [Square Corner Blog RSS Feed](<https://devfeed.tech/sources/square-corner-blog-rss-feed.md>)

Topics: [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Security](<https://devfeed.tech/topics/security.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>)

Tags: [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-eventbridge](<https://devfeed.tech/tags/aws-eventbridge.md>), [communication](<https://devfeed.tech/tags/communication.md>), [data-governance](<https://devfeed.tech/tags/data-governance.md>), [data-loss-prevention](<https://devfeed.tech/tags/data-loss-prevention.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [iam](<https://devfeed.tech/tags/iam.md>), [security](<https://devfeed.tech/tags/security.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

This article examines how misconfigured cross-account Amazon EventBridge flows can create inbound and outbound security risks. It describes possible event injection, triggering of vulnerable processing logic, and data exfiltration, and provides guidance for securing these configurations.

### Source excerpt

Securing the invisible paths: How cross-account event flows can become security blind spots

## Should we consider migrate to Amazon EventBridge from Amazon SNS + SQS ?

DevFeed: [Should we consider migrate to Amazon EventBridge from Amazon SNS + SQS ?](<https://devfeed.tech/articles/should-we-consider-migrate-to-amazon-eventbridge-from-amazon-sns-sqs-23692.md>)

Original publisher: [Read original article](<https://medium.com/betclic-tech/should-we-consider-migrate-to-amazon-eventbridge-from-amazon-sns-sqs-4adc8950eca?source=rss----7e406d68d94b---4>)

Author: Guillaume Lannebere

Published: 2022-02-01T14:45:47Z

Content type: article

Language: en

Sources: [betclic-tech - Medium](<https://devfeed.tech/sources/betclic-tech-medium.md>)

Topics: [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [eventbridge](<https://devfeed.tech/tags/eventbridge.md>), [latency](<https://devfeed.tech/tags/latency.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [net](<https://devfeed.tech/tags/net.md>), [sns](<https://devfeed.tech/tags/sns.md>), [sqs](<https://devfeed.tech/tags/sqs.md>)

### AI overview

The article examines Betclic's event-driven architecture requirements and its early-2019 decision to combine Amazon SNS with Amazon SQS. It presents the decision in the context of unpredictable traffic, multiple consumers, event replay, monitoring, schema management, language interoperability, analytics, autoscaling, low latency, high availability, AWS integration, and cost.

### Source excerpt

Should we consider migrating to Amazon EventBridge from Amazon SNS + SQS? In early 2019, Betclic was in a corner, and we decided to migrate to microservices approach and migrate to the cloud. The first step of this change was the implementation of an Event Driven Architecture (EDA). Betclic presentation Before speaking of architecture and EDA, it's essential to know what Betclic is doing to understand our choice quickly. Betclic is a French online gambling company. Betclic operates in Sports betting, horse race betting, and online poker. The specificity of gambling is that we don't have predictive traffic. We have high traffic peaks during significant events and weekends. We can see an example of traffic on a soccer event: Example of trafficEDA wishlist When beginning 2019, we did a workshop to identify the key features of our ideal EDA; we would like something: allowing multiple reads: the same message can be read by various services with error recovery: in case of error, we would like to replay events easy to monitor: particularly with Datadog, our centralized monitoring solution with schema registry language-agnostic: we use 3 main languages .net, Kotlin, and Typescript (for Lambda), and the chosen solution must work with all languages with analytics capabilities: we would like to integrate all our events of EDA in our data lake fully managed with auto scaling: essential feature for us; we have unpredictable traffic with big spikes at the end of matches, so we need to have an EDA to be able to absorb our spikes with low latency and high availability: also an essential feature, we would like our EDA to serve critical use cases for our final users, so we want something the most real-time and the most available possible well-integrated with AWS services: EDA is one of our first bricks in the cloud, but we want something to help us to migrate to AWS easy to use: we want all the time something easy to use :) but here it's particularly true because EDA is a centralized