Amazon EventBridge is a serverless event bus that makes it easier to build event-driven applications at scale by leveraging events generated by your applications, integrated SaaS applications, and AWS services. EventBridge streams real-time data from event sources like Zendesk or Shopify to destinations like AWS Lambda and other SaaS applications.
In this blog, we will be discussing Amazon Event Bridge
- What is Amazon EventBridge?
- How does it work?
- Features
- Benefits
- Use cases
- Amazon EventBridge rules
- Security
- Frequently Asked Questions
What is Amazon EventBridge?
Amazon EventBridge can also be thought of as a rule-driven event router. It enables you to define event patterns based on event content to determine which targets (subscribers) receive each event passing through the bus. Lambda functions, Kinesis streams, SQS queues, and even other Event Buses in different AWS accounts can all be used as event targets. This opens the door to compelling patterns for multi-service, even multi-departmental decoupled communications.
This pub/sub-event pattern can be used with a variety of other AWS services, each with its own set of features and tradeoffs. Kinesis has ordering guarantees, but it isn’t entirely usage-based pricing and doesn’t scale to demand automatically. SNS can scale almost infinitely, but filtering is limited to attributes rather than event content, and order is not guaranteed.
How does Amazon EventBridge work?
Amazon EventBridge connects applications by using events. An event is a signal that the state of a system has changed, such as a change in the status of a customer support ticket. Customers can integrate their own AWS applications with microservices, SaaS applications, and custom applications as event sources that publish events to an event bus. You can define a filtering rule to filter events and route them to AWS service targets and API destinations (via HTTP endpoints).
The Amazon EventBridge schema registry stores schema generated by your company’s applications, AWS services, or SaaS applications. A schema contains information about event data such as the title, format, and validation rules. You can use your IDE to download code bindings for any schema in the registry and use the strongly-typed object representing the event directly in your code.
You can archive, or save, events and then replay them from the archive at a later time. Because you have a store of events to use instead of having to wait for new events, archiving is useful for testing an application.
Features-
- Global endpoints- Global endpoint is a new feature that enables customers to build more robust and reliable applications by automatically switching event ingestion to a secondary region during service disruptions without the need for manual intervention.
- API Destinations- API Destinations is a new EventBridge feature that allows developers to send events back to a variety of on-premises or software-as-a-service (SaaS) applications while controlling throughput and authentication.
- Schema Registry- The registry also enables you to generate code bindings for programming languages like Java, Python, or TypeScript directly in your IDE, allowing you to use the event as an object in your code.
- Fully managed and scalable event bus- Amazon EventBridge is a serverless, fully managed, and scalable event bus that enables applications to communicate with each other via events. There is no infrastructure to manage or capacity to provide.
- SaaS Integration- Your AWS applications can react to events generated by SaaS applications. Amazon EventBridge is natively integrated with many SaaS applications, including Datadog, OneLogin, PagerDuty, Savyint, Segment, SignalFx, SugarCRM, Symantec, Whispir, and Zendesk, with more integrations on the way.
- Over 100 built-in event sources and targets- Amazon EventBridge is directly integrated with over 130 event sources and 35 targets, including AWS Lambda, Amazon SQS, Amazon SNS, AWS Step Functions, Amazon Kinesis Data Streams, and Amazon Kinesis Data Firehose, with additional sources and targets planned.
- Event filtering- Events can be filtered using rules. Rules enable various application components to search for and process events of interest to them.
- Automatic response to operational changes in AWS services- It enables you to respond to operational changes and take corrective action quickly.
- Monitoring and auditing- Amazon CloudWatch metrics, such as the number of times an event matches a rule or the number of times a target is invoked, can be used to monitor your event bus.
- Pay per event- AWS services generate free events. Only events generated by your own applications or SaaS applications are charged for.
Benefits-
- Build event-driven architectures- Your event targets do not need to be aware of event sources when using EventBridge because you can filter and publish directly to EventBridge. Loosely coupled event-driven architectures improve developer agility as well as application resiliency.
-
Connect SaaS apps- Without the need for custom integration code, EventBridge ingests data from supported SaaS applications and routes it to AWS services and SaaS targets.
-
Write less custom code- EventBridge facilitates the connection of applications. The EventBridge schema registry stores a collection of easily accessible event schemas and allows you to download code bindings for those schemas in your IDE to represent events as strongly typed objects in your code.
-
Reduce operational overhead- There are no servers to install, patch, or manage with EventBridge. No additional software is required to install, maintain, or operate. EventBridge scale automatically based on the number of events consumed, and you only pay for events published by your AWS or SaaS applications.
Use Cases of Amazon EventBridge
1. Re-architect for speed- Amazon EventBridge can help you speed up the modernization and re-orchestration of your architecture with decoupled services and applications. EventBridge eliminates the need for extensive coordination between event producers and consumer applications or services.
2. Monitoring and Auditing- When cross-accounts or public accounts access your resources, you can use EventBridge to configure an Amazon Access Analyzer event to be generated and sent to an AWS Lambda Function to remove the unintended permissions.
3. Extend functionality via SaaS integrations- You can easily connect your applications to other SaaS applications via EventBridge to extend their functionality. When a new user is created in a free tier, you can send a custom event to EventBridge and then send that event to Zendesk CRM using API Destinations.
4. Customize SaaS with AI/ML- You can gain valuable insights by enriching your SaaS application events with AWS Artificial Intelligence/Machine Learning services. You can import data from Shopify into EventBridge to trigger a workflow, and then use AI services like Amazon Comprehend to tag images of new retail products.
5. Build event-driven architectures- Amazon EventBridge makes it easier to create event-driven architectures. Applications or microservices can publish events to the event bus without the publisher’s knowledge, and applications or microservices can subscribe to events without the publisher’s knowledge.
Amazon EventBridge rules-
1. Incoming events are matched by a rule and routed to targets for processing. A single rule can dispatch an event to multiple targets, which will then execute in parallel. An event pattern specifies the structure of an event as well as the fields that a rule must match. Scheduled rules perform an action at regular intervals.
2. Amazon EventBridge rules that are required for certain functions in AWS services can be created and managed in your AWS account. This is referred to as managed rules.
3. When a service creates a managed rule, it can also create an IAM policy granting that service permission to create the rule. IAM policies created in this manner are narrowly scoped with resource-level permissions to allow only the necessary rules to be created.
4. You can delete managed rules by using the Force delete option, but only if you are certain that the other service no longer requires the rule.
Amazon EventBridge Security
Amazon EventBridge controls access to other AWS services and resources using AWS Identity and Access Management. AWS is in charge of safeguarding the global infrastructure that underpins the AWS Cloud. You are in charge of maintaining control over the content hosted on this infrastructure. This section contains security configuration and management tasks for the AWS services you use.
You can secure your data in the following ways:
- With each account, enable multi-factor authentication (MFA).
- Use SSL/TLS to communicate with AWS resources. We recommend TLS 1.2 or later.
- Configure AWS CloudTrail to log API and user activity.
- Use AWS encryption solutions in conjunction with all AWS service default security controls.
- Utilize advanced managed security services, such as Amazon Macie, which aids in the discovery and protection of personal data stored in Amazon S3.
- Use a FIPS endpoint if you need FIPS 140-2 validated cryptographic modules when accessing AWS via a command line interface or an API.
Frequently Asked Questions
Q1. How does Amazon EventBridge relate to CloudWatch Events?
Ans. CloudWatch Events are built upon and extended by Amazon EventBridge. It makes use of the same service API and endpoints, as well as the same service infrastructure. Nothing changes for existing CloudWatch Events customers; you can continue to use the same API, CloudFormation templates, and console.
Q2. Which AWS services are integrated as event sources for Amazon EventBridge?
Ans. AWS Lambda, Amazon Kinesis, AWS Fargate, and Amazon Simple Storage Service are among the over 90 AWS services available as event sources for EventBridge (S3).
Q3.What are EventBridge Archive and Replay Events?
Ans. Event Replay is a new Amazon EventBridge feature that allows customers to reprocess previous events back to an event bus or an EventBridge rule. Developers can use this feature to easily debug their applications, extend them by hydrating targets with historic events, and recover from errors. Event Replay ensures that developers will always have access to any event published to EventBridge.
Q4. Can I publish my own events to Amazon EventBridge?
Ans. Yes. Customers can use the service’s APIs to generate custom application-level events and publish them to Amazon EventBridge. Customers can also configure scheduled events to be generated on a regular basis, and these events can be processed in any of the Amazon EventBridge supported targets.
Related Links/References
- AWS Free Tier Limits
- AWS Free Tier Account Details
- How to create a free tier account in AWS
- AWS Free Tier Account Services
Next Task For You
Begin your journey towards becoming a Certified AWS Solution Architect Associate by joining our FREE Informative Class on Amazon AWS Solution Architect Certification For Beginners & Q/A by clicking on the below image.
The post Amazon Event Bridge : Overview, Use Cases, Benefits, Security appeared first on Cloud Training Program.