AWS EventBridge Interview Questions and Answers

Without having to write any code, Amazon EventBridge offers real-time access to data changes in AWS services, your own applications, and software-as-a-service (SaaS) applications. AWS Lambda, Amazon Simple Notification Service (SNS), and Amazon Kinesis Data Firehose are just a few of the AWS services you can choose from as targets once you’ve chosen an event source on the Amazon EventBridge panel. The events will be automatically delivered via Amazon EventBridge in close to real-time. 

1. What is Amazon EventBridge?

Amazon EventBridge is a service that provides real-time access to changes in data in AWS services, your own applications, and software as a service (SaaS) applications without writing code. To get started, you can choose an event source on the EventBridge console. You can then select a target from AWS services including AWS Lambda, Amazon Simple Notification Service (SNS), and Amazon Kinesis Data Firehose. EventBridge will automatically deliver the events in near real-time.

 2. What are the steps for using Amazon EventBridge?

Choose an event source from a list of partner SaaS applications and AWS services by logging into your AWS account, going to the Amazon EventBridge dashboard, and selecting that source. Make sure your SaaS account is set up to emit events if you’re using a partner application, then accept the source in the provided event sources section of the Amazon EventBridge console. Your event bus will be immediately created by Amazon EventBridge and used to route events.

As an alternative, you can instrument your application with the AWS SDK to begin broadcasting events to your event bus. Add a target for your events and optionally configure a filtering rule; the target may be a Lambda function, for instance. The events will be automatically ingested, filtered, and sent to the specified target in a secure and highly available manner by Amazon EventBridge.

3. How can I get started using EventBridge?

Log in to your AWS account, navigate to the EventBridge console, and choose an event source from a list of partner SaaS applications and AWS services. If you are using a partner application, verify that you have configured your SaaS account to emit events and accept it in the offered event sources section of the EventBridge console. EventBridge will automatically create an event bus for you to which events will be routed.

Alternatively, you can use AWS SDK to instrument your application to start emitting events to your event bus. Optionally configure a filtering rule and attach a target for your events; for example, this can be a Lambda function. EventBridge will automatically ingest, filter, and send the events to the configured target in a secure and highly available way.

4. What are EventBridge API Destinations?

Developers may regulate throughput and authentication while sending events back to any on-premises or SaaS apps using API Destinations. EventBridge will handle security and delivery while customers set rules with input transformations that transfer the event format to the format of the receiving service.

When a rule is activated, Amazon EventBridge transforms the event in accordance with the parameters supplied and sends it to the defined web service along with the authentication data specified when the rule was created. Developers no longer have to create authentication components for the service they wish to utilize because security is already built in.

5. Can I publish my own events to EventBridge?

Yes. You can generate custom application-level events and publish them to EventBridge through the service’s API operations. You can also set up scheduled events that are generated on a periodic basis and can process these events in any of the EventBridge-supported targets.

6. How are CloudWatch Events related to Amazon EventBridge?

CloudWatch Events are improved and expanded upon by Amazon EventBridge. It makes use of the same service API, endpoint, and underpinning infrastructure. Nothing has changed for current CloudWatch Events users; you can continue to utilize the same API, CloudFormation templates, and console.

Customers told us that CloudWatch Events is the best service for creating event-driven architectures, so we created new features to let customers link data from their own SaaS apps and those of other companies. We have launched this feature under the moniker Amazon EventBridge rather than under the CloudWatch service to reflect its extension outside the monitoring use case for which it was designed.

7. How do I secure access to EventBridge?

EventBridge integrates with AWS Identity and Access Management (IAM) so that you can specify which actions a user in your AWS account can perform. For example, you can create an IAM policy that gives only certain users in your organization permission to create event buses or attach event targets.

8. How does EventBridge relate to Amazon CloudWatch Events?

EventBridge builds upon and extends Amazon CloudWatch Events. It uses the same service API and endpoint, and the same underlying service infrastructure. For existing CloudWatch Events customers, nothing changes. You can continue to use the same API, AWS CloudFormation templates, and console.

CloudWatch Events is the ideal service for building event-driven architectures, so we built new features that help you connect data from your own apps and third-party SaaS apps. Rather than keep this beneath the CloudWatch service, we released this functionality with a new name, Amazon EventBridge, to signify the expansion beyond the monitoring use case that CloudWatch Events was developed for.

9. I currently use CloudWatch Events and I want to try the features of EventBridge. Do I need to move my CloudWatch Events rules and permissions to EventBridge?

No. Existing CloudWatch Events users can access their existing default bus, rules, and events in the new EventBridge console and API or in the CloudWatch Events console and API.

10. Which AWS services are included with Amazon EventBridge as event sources?

Over 90 AWS services, including AWS Lambda, Amazon Kinesis, AWS Fargate, and Amazon Simple Storage Service, are available as event sources for EventBridge (S3).

Amazon EventBridge is a serverless event bus that makes it easy to connect application data to AWS services. Event sources for EventBridge include:

1. AWS services: Many AWS services can publish events to EventBridge, including Amazon SNS, Amazon S3, Amazon EC2, and AWS CodePipeline.
2. Custom events: You can use EventBridge to create custom events and trigger AWS Lambda functions or other targets based on those events.
3. Software-as-a-Service (SaaS) applications: EventBridge supports integration with popular SaaS applications, such as Salesforce, Zendesk, and Datadog, allowing you to use these applications to trigger AWS Lambda functions or other targets.
4. Partnered events: EventBridge also supports integration with partnered events, such as those from New Relic and PagerDuty, allowing you to trigger AWS Lambda functions or other targets based on events from these applications.

EventBridge allows you to connect a wide range of event sources to your applications and services, enabling you to build powerful event-driven architectures on AWS.

11. I’m already using CloudWatch Events and I don’t need the features of EventBridge. What will change for me?

Nothing. EventBridge uses the same CloudWatch Events API so all of your existing CloudWatch Events API usages will remain the same.

12. Are you going to phase out CloudWatch Events one day?

No, we are not going to deprecate the API or the service itself. EventBridge uses the same API and has additional features. Over time, the Amazon CloudWatch Events name will be replaced with Amazon EventBridge.

13. Which AWS services are integrated as event sources for Amazon EventBridge?

There are over 90 AWS services available as event sources for EventBridge, including AWS Lambda, Amazon Kinesis, AWS Fargate, and Amazon Simple Storage Service (S3). For a full list of AWS service integrations, see the EventBridge documentation.

Amazon EventBridge is a serverless event bus that makes it easy to connect application data to AWS services. The following AWS services are integrated as event sources for Amazon EventBridge:

1. Amazon SNS (Simple Notification Service)
2. Amazon S3 (Simple Storage Service)
3. Amazon EC2 (Elastic Compute Cloud)
4. AWS CodePipeline

In addition to these AWS services, EventBridge also supports integration with popular Software-as-a-Service (SaaS) applications, such as Salesforce and Zendesk, and partnered events from New Relic and PagerDuty. It also allows you to create custom events and trigger AWS Lambda functions or other targets based on those events.

14. Which AWS services are integrated as event targets for EventBridge?

There are over 15 AWS services available as event targets for EventBridge including Lambda, Amazon Simple Queue Service (SQS), Amazon SNS, Amazon Kinesis Streams, and Kinesis Data Firehose. For a full list of AWS service integrations, see the EventBridge documentation.

15. What are EventBridge Archive and Replay Events?

Event Replay is a new feature for EventBridge that helps you reprocess past events back to an event bus or a specific EventBridge rule. This feature helps developers debug their applications more easily, extend them by hydrating targets with historic events, and recover from errors. Event Replay gives developers peace of mind that they will always have access to any event published to EventBridge.

16. Is Serverless Application Model (AWS SAM) allow for the use of schema?

Yes, you may build new serverless apps on EventBridge for any schema as an event type using the interactive mode of the most recent AWS SAM CLI. Simply select the “EventBridge Starter App” template and the event’s schema, and AWS SAM will create an application with a Lambda function that is called by EventBridge and handling code for the event. This implies that you may utilize IDE tools like validation and auto-complete and treat an event trigger like a regular object in your code.

AWS Toolkit for Visual Studio Code and the AWS Toolkit for Jetbrains (Intellij, PyCharm, Webstorm, Rider) plugins both offer the ability to create serverless apps from this template with a schema acting as a trigger right inside of these IDEs.

17. How can writing less code using the schema registry benefit me?

In order to avoid having to manage your event schema manually, you can first utilize schema discovery to automatically identify schema for any events transmitted to your EventBridge event bus and save them in the registry. Second, you can develop and download code bindings for this schema when creating apps that process events on your bus so that you can use strongly-typed objects right away. Deserialization, validation, and guesswork for your event handler are all avoided as a result.

18. What are EventBridge API Destinations?

API Destinations helps developers send events back to any on-premises or SaaS applications with the ability to control throughput and authentication. You can configure rules with input transformations that will map the format of the event to the format of the receiving service, and EventBridge will take care of security and delivery.

When a rule is initiated, EventBridge will transform the event based on the conditions specified. It will then send it to the configured web service with authentication information that was provided when the rule was set up. Security is built so that developers no longer need to write authentication components for the service that they want to use.

Questions on EventBridge Limits and performances

19. Does EventBridge support resource tagging?

Yes, Amazon EventBridge supports resource tagging. You can use tags to classify your EventBridge resources and to help manage and track your resources.

20. What throughput can I expect from EventBridge?

Event bus throughput limits are given on the service limits page here. If you require higher throughput, request a service limit increase through the AWS Support Center by choosing Create Case and then choosing Service Limit Increase.

21. Does EventBridge have a Service Level Agreement?

Yes. AWS will use commercially reasonable efforts to make EventBridge available with a Monthly Uptime Percentage for each AWS Region, during any monthly billing cycle, of at least 99.99%. For details, review the full EventBridge Service Level Agreement.

Questions on EventBridge Schema Registry

22. What is a schema registry?

A schema registry stores a searchable collection of schemas so any developer in your organization can more easily access schemas generated by the application. This is in contrast to looking through documentation or finding the schema’s author for this information. You can add a schema to the registry manually or automate this process by turning on the EventBridge schema discovery feature.

23. How can I protect my use of Amazon EventBridge?

You can define the actions that a user within your AWS account is permitted to take by integrating Amazon EventBridge with AWS Identity and Access Management (IAM). You could, for instance, set an IAM policy that allows only specific users in your company to add event targets or create event buses.

24. What is the schema discovery feature?

Schema discovery automates the processes of finding schemas and adding them to your registry. When schema discovery is enabled for an EventBridge event bus, the schema of each event sent to the event bus is automatically added to the registry. If the schema of an event changes, schema discovery will automatically create a new version of the schema in the registry.

Once a schema is added to the registry, you can generate a code binding for the schema either in the EventBridge console or directly in your integrated development environment (IDE). This helps you represent the event as a strongly typed object in your code. You can then take advantage of IDE features such as validation and autocomplete.

25. How does the schema registry reduce the amount of code I need to write?

First, you can use schema discovery to identify schema automatically for any events sent to your EventBridge event bus and store them in the registry. This saves you from having to manage your event schema manually. Second, when you write applications that handle events on your bus, you can generate and download code bindings for this schema so you can use strongly typed objects directly in your code. This saves overhead for deserialization, validation, and guesswork for your event handler.

26. Why should I use the schema registry?

First, you can use schema discovery to identify schema automatically for any events sent to your EventBridge event bus and store them in the registry. This saves you from having to manage your event schema manually. Second, when you write applications that handle events on your bus, you can generate and download code bindings for this schema so you can use strongly typed objects directly in your code. This saves overhead for deserialization, validation, and guesswork for your event handler.

27. Which IDEs does the schema registry support?

The schema registry is available through the AWS Toolkit for JetBrains (IntelliJ IDEA, PyCharm, WebStorm, Rider) and AWS Toolkit for Visual Studio Code, and in the EventBridge console and API operations. Learn more about using the EventBridge schema registry within your IDE.

28. Can I use schema with the AWS Serverless Application Model (SAM)?

Yes, the latest version of the AWS SAM CLI includes an interactive mode that helps you create new serverless applications on EventBridge for any schema as an event type. Choose the EventBridge Starter App template, and the schema of your event and SAM will automatically generate an application with a Lambda function invoked by EventBridge, with the handling code of the event. This means that you can treat an event trigger like a normal object in your code, and use features such as validation and autocomplete in your IDE.

The AWS Toolkit for Jetbrains (Intellij IDEA, PyCharm, Webstorm, Rider) plugin and AWS Toolkit for VS Code also provide the functionality to generate serverless applications from this template with a schema as a trigger, directly from these IDEs.

29. In which AWS Regions is the schema registry available?

The EventBridge schema registry is available in the following Regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo).

30. Does Amazon EventBridge allow me to publish my own events?

Yes. Through the use of the service’s APIs, you can create unique application-level events and publish them to Amazon EventBridge. Additionally, you can create scheduled events that are generated on a regular basis and process these events in any of the available targets for Amazon EventBridge.

31. When should I make use of Amazon SNS and when of Amazon EventBridge?

Your choice will depend on your particular requirements, but you may create event-driven apps using both Amazon EventBridge and Amazon SNS. When creating an application that responds to events from SaaS applications and/or AWS services, Amazon EventBridge is advised. The only event-based service that interacts directly with external SaaS providers is Amazon EventBridge. Without needing developers to create any resources in their account, Amazon EventBridge also automatically ingests events from over 90 AWS services.

Over 15 AWS services, including Amazon Lambda, Amazon SQS, Amazon SNS, Amazon Kinesis Streams, and Kinesis Data Firehose, are presently supported as targets by Amazon EventBridge.With a limited throughput at launch that can be expanded upon request and an average latency of about half a second, Amazon EventBridge is currently in beta.

32. How should I failover my global endpoint? What metrics should I use?

In order to make it simple for you to identify whether there are any difficulties with EventBridge that would necessitate you failover your event ingestion to the secondary region, we have added a new measure that shows the end-to-end latency of Amazon EventBridge. By offering a pre-populated CloudFormation stack (that you may alter if you so desire) for setting a CloudWatch Alarm and Route53 Health Checks in the console, AWS has made it simple for you to get started.

Questions on EventBridge Pipes

33. What are Amazon EventBridge Pipes?

EventBridge Pipes provides a simpler, consistent, and cost-effective way to create point-to-point integration between event producers and consumers. Creating a pipe is as simple as selecting a source and a target with the ability to customize batching, starting position, concurrency, and more.

An optional filtering step allows only specific source events to flow into the pipe and an optional enrichment step using AWS Lambda, AWS Step Functions, API Destinations, or Amazon API Gateway can be used to enrich or transform events before they reach the target. By removing the need to write manage, and scale undifferentiated integration code, EventBridge Pipes allows you to spend your time building applications rather than connecting them.

34. How do I get started with EventBridge Pipes?

You can get started by visiting the EventBridge console, selecting the Pipes tab, and choosing to Create Pipe. From there, you can choose from a list of available sources and provide an optional filtering pattern that will be used to transfer only the events you require. For the optional transformation and enrichment step of a pipe, you can provide an API endpoint, such as a SaaS application API or container cluster, Lambda function, or AWS Step Function.

The pipe will then make the API request and capture the response once processing is completed. Finally, set a destination service to which the events are delivered, and specify whether you require archiving or DLQ capabilities to be enabled on the pipe. You can also create a pipe using the AWS CLI, CloudFormation, CloudFormation, or AWS Cloud Development Kit (CDK).

35. What are EventBridge Archive and Replay Events?

Customers can reprocess previous events back to an event bus or a specific EventBridge rule using the new feature Event Replay for Amazon EventBridge. Developers can use this functionality to quickly debug their apps, extend them by hydrating targets with historical events, and fix mistakes. Developers may rest easy knowing that they will always have access to any event submitted to EventBridge thanks to Event Replay.

36. What are the possible event sources for EventBridge Pipes?

EventBridge Pipes introduces Amazon SQS, Amazon Kinesis, Amazon DynamoDB, Amazon Managed Streaming Kafka, self-managed Kafka, and Amazon MQ as sources to the EventBridge product suite. EventBridge Pipes supports the same target services as event buses, such as Amazon SQS, AWS Step Functions, Amazon Kinesis Data Streams, Amazon Kinesis Data Firehose, Amazon SNS, Amazon ECS, and event buses themselves.

37. How do transformation and enrichment work?

EventBridge Pipes support basic transformations using Velocity Template Language (VTL). For more powerful transformations, EventBridge Pipes helps you specify a Lambda function or Step Functions workflow to transform your event. If you’d prefer to use a container service such as Amazon Elastic Container Service (ECS) or Amazon Elastic Kubernetes Service (EKS), you can specify the API endpoint and authentication scheme for your container cluster. EventBridge will then take care of delivering the event for transformation.

38. Do I need to use an EventBridge event bus to use EventBridge Pipes?

No, EventBridge Pipes can be used independently of existing EventBridge features, helping you receive events from other event producers such as Kinesis, SQS, or Amazon MSK, without needing to use an EventBridge event bus. It is also used for point-to-point integrations, whereas an event bus is used for many-to-many integrations. If you are already using an EventBridge event bus to route events, you can use EventBridge Pipes to connect to a supported source and set your event bus as the source of a pipe.

39. What is the difference between the EventBridge event bus and EventBridge Pipes?

EventBridge event buses are well suited for many-to-many routing of events between event-driven services. EventBridge Pipes is intended for point-to-point integrations between event publishers and consumers, with support for advanced transformations and enrichments. EventBridge Pipes can use an EventBridge event bus as a target. Migrating from an EventBridge event bus rule to a pipe is easier, as filtering and targets remain the same between the two resources.

40. Why would I use Amazon EventBridge in my SaaS application?

SaaS vendors can easily integrate their services with the event-driven architectures created by their clients and hosted on AWS thanks to Amazon EventBridge. Millions of AWS developers may now directly access your product thanks to Amazon EventBridge, opening up new applications. It provides an entirely safe, scalable, and auditable solution to convey events without requiring the SaaS vendor to handle any eventing infrastructure.

41. How are EventBridge Pipes different from AWS Lambda’s Event Source Mapping (ESM)?

AWS Lambda’s Event Source Mapping (ESM) and Amazon EventBridge Pipes use the same polling infrastructure to select and send events. ESM is ideal for customers who want to use Lambda as a target to process the received events. Pipes are ideal for customers who would rather not worry about creating, maintaining, and scaling Lambda code and instead prefer simple, managed resources to connect their source to one of over 14 targets.

42. Does EventBridge Pipes provide ordering guarantees?

Yes, Amazon EventBridge Pipes provide ordering guarantees. EventBridge Pipes are a feature that allows you to specify a set of rules that determine how events are routed between event buses. When you use EventBridge Pipes, events are guaranteed to be delivered in the order they were published, providing you with a reliable way to process events in a specific order.

43. Does EventBridge Pipes support batching events?

Yes, for services that support batching events, you can configure your desired batch size when creating a pipe. For sources and targets that don’t support batching, you can still choose to batch events for your enrichment and transformation step. This helps you save compute costs and still helps you deliver events individually to your chosen target.

44. Can I get a history of EventBridge Pipes API calls made on my account for security analysis and operational troubleshooting purposes?

Yes, you can use AWS CloudTrail to get a history of EventBridge Pipes API calls made on your account. AWS CloudTrail is a service that records AWS API calls for your account and delivers log files to you. You can use CloudTrail to monitor the EventBridge Pipes API calls made in your AWS account, including calls to create, delete, and list pipes. CloudTrail can be helpful for security analysis, operational troubleshooting, and compliance purposes.

Questions on EventBridge Scheduler

45. What is Amazon EventBridge Scheduler?

Amazon EventBridge Scheduler is a serverless task scheduler that simplifies creating, executing, and managing millions of schedules across AWS services without provisioning or managing the underlying infrastructure.

46. How do I get started with EventBridge Scheduler?

Log in to your AWS account, navigate to the EventBridge console and select the Create Schedule button. Follow the step-by-step workflow and fill in the required fields. Select a scheduling format including a time window for the task to implement, fixed-rate, cron, or a specific date and time. Select your target from a list of AWS services and configure retry policies for maximum control of your schedule implementation. Review your schedule and select Create.

47. What is the difference between EventBridge Scheduler and Scheduled Rules?

EventBridge Scheduler builds upon the scheduling functionality offered within Scheduled Rules. EventBridge Scheduler includes support for time zones, increased scale, customized target payloads, added time expressions, and a dashboard for monitoring schedules. Schedules can be created independently without the need to create an event bus with a scheduled rule.

48. When should I use EventBridge Scheduled Rules or EventBridge Scheduler?

Scheduled rules will continue to be available, however, EventBridge Scheduler offers a richer feature set providing more flexibility when creating, executing, and managing your schedules. You can also get started for free, see the pricing page for more details.

49. How does this feature work with other AWS services?

EventBridge Scheduler has deep integrations with AWS services and can create schedules for any service with an AWS API action. Configurations for time patterns and retries are uniform across AWS for a consistent scheduling experience. Monitoring schedules is easier through the EventBridge Scheduler console delivering a view of your schedules in a dashboard or with a “ListSchedule” API request.

You will be able to see critical information on your schedules such as start time, last run, and the assigned AWS target. For more granular details, you can review execution logs available in CloudWatch Logs or they can be sent to S3 or Kinesis Firehose.

50. How do I update my schedule?

To update the schedule for an Amazon EventBridge rule, you can use the UpdateRule API action or the UpdateRule AWS Management Console.

To update the schedule using the UpdateRule API action, you can use the PutTargets operation and specify the new schedule in the ScheduleExpression parameter.

To update the schedule using the AWS Management Console, you can navigate to the EventBridge dashboard, select the rule that you want to update, and then click the “Edit” button. From there, you can specify the new schedule in the “Schedule expression” field and then click the “Save” button to update the schedule.

Note that you can only update the schedule for rules that are scheduled to run on a fixed rate or fixed delay. If the rule is scheduled to run on a cron expression, you will need to delete the rule and recreate it with the updated schedule.

51. Does EventBridge Scheduler support all time zones?

Yes, with EventBridge Scheduler you can select what time zone a schedule will operate. These schedules will automatically adjust to Daylight Savings Time (DST) and back to standard time.

52. How does EventBridge Scheduler verify scheduled delivery?

EventBridge Scheduler provides at least one event delivery to targets, meaning that at least one delivery succeeds with a response from the target. Options to set retries, time windows, and timeouts are available to meet your business requirements.

53. How can I monitor the status of my schedules?

EventBridge Scheduler provides a monitoring page in the EventBridge Scheduler console for all of your created schedules where you can view details of your schedules and their implementation. This includes when your schedule started, implementation time pattern, and target delivery status with response codes to be able to see the success, failure, or retry attempts.

54. Can I schedule a task for services outside of AWS, like my on-premises server or external SaaS products?

EventBridge Scheduler does not support non-AWS targets directly. However, you can invoke non-AWS targets using Lambda, ECS, and Fargate, or with EventBridge via the API destinations feature.

55. What does EventBridge Scheduler Cost?

Amazon EventBridge Scheduler is a fully managed service that allows you to schedule the invocation of AWS resources. There is no additional charge for using EventBridge Scheduler. You only pay for the underlying AWS resources that are invoked by the scheduled events, such as AWS Lambda functions or Amazon SNS notifications.

For more information on the pricing of the underlying AWS resources, you can refer to the pricing pages for those services.

Questions on EventBridge Global Endpoints

56. What are Global Endpoints?

Global endpoints are a new feature of EventBridge that makes it easier for you to build highly available event-driven applications using AWS. You can replicate your events across primary and secondary Regions to implement failover with minimum data loss. You can also implement the ability to failover automatically to a backup Region in case of any service disruptions. This simplifies the adoption of multi-region architectures and helps you incorporate resiliency in your event-driven applications.

57. What metrics should I use to failover my global endpoint?

We have added a new metric that reports the entire latency of EventBridge that helps you more easily determine if there are errors within EventBridge that require you to failover your event ingestion to the secondary Region.

It’s easier for you to get started in the console by providing a pre-populated CloudFormation stack (that you can customize if you choose to) for creating a CloudWatch Alarm and Route 53 health checks. For more details on how to set up the alarms and the health checks, check out our launch blog and documentation.

58. Will I be charged for replication?

Yes, you will be charged $1 per million events for replication, which EventBridge charges for cross Region events.

59. How does a global endpoint increase my applications’ availability?

Events are routed to the event bus in your main area after they are published to the global endpoint. Your health check is flagged as unhealthy and incoming events are directed to the secondary area if faults are found in the primary region. Using CloudWatch Alarms (through Route53 health checks) that you set, errors can be quickly found. As soon as the problem is resolved, AWS routes fresh events back to the original Region and gets on with event processing.

Questions on EventBridge Architecture and design

60. Can I use CloudFormation with EventBridge?

Yes. CloudFormation support is available in all Regions where Amazon EventBridge is available. To learn more about how to use CloudFormation to provision and manage EventBridge resources, visit our documentation.

61. When should I use EventBridge and when should I use SNS?

Both EventBridge and SNS can be used to develop event-driven applications, and your choice will depend on your specific needs. EventBridge is recommended when you want to build an application that reacts to events from SaaS applications or AWS services.

EventBridge is the only event-based service that integrates directly with third-party SaaS partners. EventBridge also automatically ingests events from over 90 AWS services without requiring developers to create any resources in their accounts. EventBridge uses a defined JSON-based structure for events and helps you create rules that are applied across the entire event body to select events to forward to a target.

EventBridge currently supports over 15 AWS services as targets, including Lambda, SQS, SNS, Amazon Kinesis Data Streams, and Data Firehose.

EventBridge currently has limited throughput (see service limits) that can be increased upon request with a typical latency of around half a second.

SNS is recommended when you want to build an application that reacts to high throughput or low latency messages published by other applications or microservices or for applications that need high fan-out.

Messages are unstructured and can be in any format. SNS supports forwarding messages to six different types of targets, including Lambda, SQS, HTTP/S endpoints, SMS, mobile push, and email. SNS’s typical latency is under 30 milliseconds. A wide range of AWS services sends SNS messages by configuring the service to do so (more than 30, including EC2, S3, and RDS).

Questions on EventBridge Integrations

62. Why would I integrate my SaaS application with EventBridge?

EventBridge makes it easier for SaaS vendors to integrate their service into their customers’ event-driven architectures built on AWS. EventBridge makes your product directly accessible to millions of AWS developers, unlocking new use cases. It offers a fully auditable, secure, and scalable pathway to send events without the SaaS vendor managing any event infrastructure.

63. My SaaS company would be a great event source. How do I get on-boarded?

SaaS vendors interested in becoming an EventBridge partner should follow self-service instructions at the Amazon EventBridge integrations page to begin publishing events in EventBridge.

64. How much effort will be required for a SaaS vendor to integrate with EventBridge?

SaaS vendors that already support a webhook or other push-based integration modes might take less than five days to integrate with EventBridge.

65. What does the feature of schema discovery do?

The procedures for locating schemas and adding them to your registry are automated by schema discovery. Each event’s schema is automatically uploaded to the registry when schema discovery is enabled for an EventBridge event bus. Schema discovery will instantly update the schema in the registry if the schema of an event changes. Once a schema has been uploaded to the registry, you can create a code binding for it either in the EventBridge console or directly in your IDE. This enables you to represent the event in your code as a strongly-typed object and utilize IDE features like validation and auto-complete.

66. In which Regions are global endpoints available?

Global endpoints are available in the following Regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo).