Data protection in Amazon EventBridge - Amazon EventBridge
EncryptionEncryption at rest

Data protection in Amazon EventBridge

The AWS shared responsibility model applies to data protection in Amazon EventBridge. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the Data Privacy FAQ. For information about data protection in Europe, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog.

For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS IAM Identity Center or AWS Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:

  • Use multi-factor authentication (MFA) with each account.

  • Use SSL/TLS to communicate with AWS resources. We require TLS 1.2 and recommend TLS 1.3.

  • Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see Working with CloudTrail trails in the AWS CloudTrail User Guide.

  • Use AWS encryption solutions, along with all default security controls within AWS services.

  • Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3.

  • If you require FIPS 140-3 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-3.

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a Name field. This includes when you work with EventBridge or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.

Data encryption in EventBridge

EventBridge provides both encryption at rest and encryption in transit to protect your data:

  • Encryption at rest

    EventBridge integrates with AWS Key Management Service (KMS) to encrypt stored data. By default, EventBridge uses an AWS owned key to encrypt data. You can also specify for EventBridge to use a customer managed key for the following instead.

    • Event buses: custom and partner events

    • EventBridge Pipes

  • Encryption in transit

    EventBridge encrypts data that passes between EventBridge and other services by using Transport layer Security (TLS).

    For event buses, this includes during an event being sent to EventBridge, as well as when EventBridge sends an event to a rule target.

Encryption at rest in Amazon EventBridge

EventBridge provides transparent server-side encryption by integrating with AWS Key Management Service (KMS). Encryption of data at rest by default helps reduce the operational overhead and complexity involved in protecting sensitive data. At the same time, it enables you to build secure applications that meet strict encryption compliance and regulatory requirements.

The following table lists the artifacts that EventBridge encrypts at rest, by resource:

Resource Details AWS owned key Customer managed key

API destinations

Supported

Not supported

Archives

Supported

Not supported

Events from AWS services

Event data includes all fields contained in the event-detail element of the event.

EventBridge does not encrypt event metadata. For more information on event metadata, see AWS service event metadata in the Events Reference.

Supported

Not supported

Events from custom and partner sources

Event data includes all fields contained in the event-detail element of the event.

EventBridge does not encrypt event metadata. For more information on event metadata, see AWS service event metadata in the Events Reference.

Supported

Supported

Event patterns (event buses)

Supported

Not supported

Input transformers (event buses)

Supported

Not supported

Pipes

Includes:

Events flowing through a pipe are never stored at rest.

Supported

Supported

By default, EventBridge uses an AWS owned key to encrypt data. You can specify for EventBridge to use customer managed keys for specific resources instead.

Important

We strongly recommend that you never put confidential or sensitive information in the following artifacts, as they are not encrypted at rest:

  • Event bus names

  • Rule names

  • Shared resources, such at tags