You can create a custom event bus to receive events from your applications. Your applications can also send events to the default event bus. When you create an event bus, you can attach a resource-based policy to grant permissions to other accounts. Then other accounts can send events to the event bus in the current account.
The following video goes through creating event buses:
To create a custom event busOpen the Amazon EventBridge console at https://console.aws.amazon.com/events/.
In the navigation pane, choose Event buses.
Choose Create event bus.
Enter a name for the new event bus.
Choose the KMS key for EventBridge to use when encrypting the event data stored on the event bus.
NoteSchema discovery is not supported for event buses encrypted using a customer managed key. To enable schema discovery on an event bus, choose to use an AWS owned key. For more information, see KMS key options.
Choose Use AWS owned key for EventBridge to encrypt the data using an AWS owned key.
This AWS owned key is a KMS key that EventBridge owns and manages for use in multiple AWS accounts. In general, unless you are required to audit or control the encryption key that protects your resources, an AWS owned key is a good choice.
This is the default.
Choose Use customer managed key for EventBridge to encrypt the data using the customer managed key that you specify or create.
Customer managed keys are KMS keys in your AWS account that you create, own, and manage. You have full control over these KMS keys.
Specify an existing customer managed key, or choose Create a new KMS key.
EventBridge displays the key status and any key aliases that have been associated with the specified customer managed key.
Choose the Amazon SQS queue to use as the dead-letter queue (DLQ) for this event bus, if any.
EventBridge sends events that aren't successfully encrypted to the DLQ, if configured, so you can process them later.
(Optional) Under Logs - optional, you can set up how EventBridge logs event information, including how to configure those logs.
For more information about event bus logs, see Logging event buses .
CloudWatch logs is selected as a log destination by default, as is the ERROR log level. So, by default, EventBridge creates a new CloudWatch log group to which it sends log records containing the ERROR level of detail.
To have EventBridge send log records to any of the supported log destinations, do the following:
Under Logs - optional, choose the destinations to which you want log records delivered.
For Log level, choose the level of information for EventBridge to include in log records. The ERROR log level is selected by default.
For more information, see Specifying log level.
Select Include detail data if you want EventBridge to include event and target information in log records.
For more information, see Including details in logs.
Configure each log destination you selected.
Configure optional event bus features:
Specify a resource-based policy by doing one of the following:
Enter the policy that includes the permissions to grant for the event bus. You can paste in a policy from another source or enter the JSON for the policy. You can use one of the example policies and modify it for your environment.
To use a template for the policy, choose Load template. Modify the policy as appropriate for your environment, including adding additional actions that you authorize the principal in the policy to use.
For more information about granting permissions to an event bus through resource-based policies, see Permissions for event buses in Amazon EventBridge.
Enable an archive (optional)
You can create an archive of events so that you can easily replay them at a later time. For example, you might want to replay events to recover from errors or to validate new functionality in your application. For more information, see Archiving and replaying events in Amazon EventBridge
Under Archives, choose Enabled.
Specify a name and description for the archive.
You can't change the archive name once it has been created.
When creating an archive as part of creating a new event bus, you can't set the event retention period or an event pattern for the archive. You can specify these for the archive once it has been created. For more information, see Updating archives.
Enable schema discovery (optional)
Enable schema discovery to have EventBridge automatically infer schemas directly from events running on this event bus. For more information, see Amazon EventBridge schemas
Under Schema discovery, choose Enabled.
Schema discovery is not supported for event buses encrypted using a customer managed key. To enable schema discovery on an event bus, choose to use an AWS owned key. For more information, see KMS key options.
Specify tags (optional)
A tag is a custom attribute label that you assign to an AWS resource. Use tags to identify and organize your AWS resources. Many AWS services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For more information, see Tagging resources in Amazon EventBridge
Under Tags, choose Add new tag.
Specify a key and, optionally, a value for the new tag.
Choose Create.
Event bus concepts
Updating an event bus
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4