Reduces Complexity and Costs of Event-Driven Architectures with AWS EventBridge Direct Delivery

Amazon EventBridge has a new feature called Direct Delivery for Cross-Account Targets, which makes event-driven designs across AWS accounts easier. It eliminates the need for more infrastructure, like EventBridge event buses in the target account, by sending events directly to cross-account AWS resources. We will explore how this affects AWS users and how businesses that use event-driven workflows could benefit from this.

Understanding Amazon EventBridge Direct Delivery for Cross-Account Targets

Before this update, triggering events between AWS accounts often entailed seeking permission for cross-account access and creating an event bus in the receiving account. This design was often slower, more complex, and required more setup and maintenance. EventBridge's Direct Delivery for Cross-Account Targets is a new feature that enables event producers to send events directly to compatible AWS services in another account without the need for an event bus. This improves the effectiveness of cross-account communication and reduces operational overhead significantly.

How to Enable Direct Delivery for Cross-Account Targets:

Here lets consider an example for AWS BedRock's event to be delivered to cross-account targets. Define the rules first:

• Define an Event Rule in the Source Account: Create an EventBridge rule that specifies the event pattern and target.

• Set the Cross-Account Target: Choose a supported AWS service as the destination (e.g., an SQS queue, Lambda function, or SNS topic in the target account).

You can do it in 2 ways. Either by giving cross-account event bus's ARN:

Or, by choosing supported AWS service which can help to sent the event to another account.

• Configure IAM Permissions: Create an AIM role granting the necessary permissions in the target account to allow cross-account event delivery.
• Test and Monitor: Use EventBridge metrics and AWS CloudWatch to monitor and troubleshoot event flows.

Key Benefits of Direct Delivery for Cross-Account Targets

1. Simplified Architecture: This is made possible by organizations not having to configure and manage the target account’s EventBridge event buses.

?2. Reduced Latency: There is less extra time needed for processing events than before since events are being sent directly to the cross-account destination.

3. Lower Costs: Customers can cut EventBridge usage costs by not having to use middle-man event buses.

4. Enhanced Security: Secure event transmission between accounts is ensured by AWS Resource Access Manager (RAM) and Identity and Access Management (IAM) policies.

5. Improved Scalability: Organizations can therefore grow event driven apps more effectively with out worrying about scaling the infrastructure.

Cost Calculation:

Remember: Though additional data transfer charges between regions billed, but there is no additional charge for global endpoints.

Final Thoughts:

For businesses that use event-driven architectures, Amazon EventBridge Direct Delivery for Cross-Account Targets is "revolutionary". It is an essential tool for AWS users who manage multi-account setups because it simplifies cross-account event processing, improves security, and lowers expenses.

This release is going to streamline the event-driven architectures by facilitating seamless interaction across AWS accounts as the company continues to improve EventBridge. The time has come to investigate and use this potent new feature if your business depends on cross-account event processing.

?

Does your AWS architecture intend to make use of this feature? Leave a comment with your ideas and experiences!

Sources:

AWS document

#AWS #FinOps #AmazonEventBridge #CloudComputing #Serverless #EventDrivenArchitecture #AWSLambda #SQS #SNS #CloudSecurity #FinOps #TechInnovation #CloudArchitecture #MultiAccountSetup