Creating an event bus in Amazon EventBridge

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 bus

  1. Open the Amazon EventBridge console at https://console.aws.amazon.com/events/.

  2. In the navigation pane, choose Event buses.

  3. Choose Create event bus.

  4. Enter a name for the new event bus.

  5. Choose the KMS key for EventBridge to use when encrypting the event data stored on the event bus.

    Note

    Archives and schema discovery are not supported for event buses encrypted using a customer managed key. To enable archives or 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.

      1. 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.

      2. 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.

  6. 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 Amazon EventBridge archive and replay

      1. Under Archives, choose Enabled.

      2. Specify a name and description for the archive.

      Note

      Archives and schema discovery are not supported for event buses encrypted using a customer managed key. To enable archives or schema discovery on an event bus, choose to use an AWS owned key. For more information, see KMS key options.

    • 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

      1. Under Schema discovery, choose Enabled.

      Note

      Archives and schema discovery are not supported for event buses encrypted using a customer managed key. To enable archives or 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 Amazon EventBridge tags

      1. Under Tags, choose Add new tag.

      2. Specify a key and, optionally, a value for the new tag.

  7. Choose Create.