Data protection in AWS RTB Fabric - AWS RTB Fabric
Data encryption

Data protection in AWS RTB Fabric

The AWS shared responsibility model applies to data protection in AWS RTB Fabric. 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 RTB Fabric 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

RTB Fabric supports encrypting data in transit using TLS 1.2 or higher when you configure TLS for RTB communications between applications. All API calls to RTB Fabric are encrypted using HTTPS endpoints.

RTB Fabric supports HTTP/1.1 with gzip compression for all RTB traffic to optimize bandwidth usage and improve performance. Compression is automatically applied when supported by both endpoints, reducing the size of bid requests and responses during transmission.

Encryption in transit

When you configure TLS encryption, RTB traffic between requester and responder applications is encrypted using TLS 1.2+ protocols. This ensures that bid requests, responses, and other RTB communications are protected during transmission across networks when TLS is enabled.

Encryption at rest

RTB Fabric encrypts configuration data and application metadata at rest using AWS managed encryption keys. This includes RTB application configurations, link settings, and operational logs. AWS does not access or read your operational logs, maintaining the confidentiality of your RTB data and business operations.