What is AWS RTB Fabric?

Requester RTB application – A customer-owned and customer-operated RTB application that initiates bid requests to other RTB applications. Examples include supply-side platforms (SSPs), ad servers, and publishers. Requester applications run in customer-controlled environments and connect to RTB Fabric through AWS managed requester gateways colocated with the customer's VPC.

External requester RTB application – An RTB application that runs outside AWS and does not use VPCs, but sends bid requests to RTB Fabric.

Requester gateway – An AWS managed network endpoint that operates colocated with the customer's VPC to facilitate secure communication from requester applications to RTB Fabric infrastructure. Requester gateways serve as connection points that route outbound bid requests and receive responses but do not host, store, or process the customer's application logic or business data.

Link – An AWS managed connection component within RTB Fabric infrastructure that enables secure, bidirectional communication between requester and responder gateways. Links are created by requester gateways and must be accepted by the AWS account that owns the responder gateway before becoming active.

Responder gateway – An AWS managed network endpoint that operates colocated with the customer's VPC to facilitate secure communication from RTB Fabric infrastructure to responder applications. Responder gateways serve as connection points that route inbound bid requests and return responses but do not host, store, or process the customer's application logic or business data.

Responder RTB application – A customer-owned and customer-operated RTB application that receives and processes bid requests from requester applications. Examples include demand-side platforms (DSPs). Responder applications run in customer-controlled environments and connect to RTB Fabric through AWS managed responder gateways colocated with the customer's VPC.

External responder RTB application – An RTB application that runs outside AWS and does not use VPCs, but receives bid requests from RTB Fabric.

Logs – Optional requester and responder logs generated by links that can be delivered to external AWS services such as Amazon CloudWatch Logs or Amazon Simple Storage Service (Amazon S3). Both requester and responder sides can independently configure log delivery through sampling rates for error logs and filter logs. Log delivery requires setup of log delivery sources, destinations, and appropriate AWS Identity and Access Management (IAM) permissions. Logs are not stored within the RTB Fabric infrastructure.

Internal to internal – Both requester and responder applications are RTB Fabric customers with single applications on each end of the link. Requester applications send requests to RTB Fabric requester gateways, which forward them through links to RTB Fabric responder gateways. Responder gateways forward requests to responder applications, which process them and return responses through the same pathway. A typical example is an SSP connecting to a DSP that both use RTB Fabric.

External to internal – Requester applications are external to RTB Fabric (not RTB Fabric customers) and may represent multiple applications that can be located on or outside AWS. External requester applications send requests to RTB Fabric requester gateways, which forward them through links to RTB Fabric responder gateways. Responder gateways forward requests to responder applications, which process them and send responses back through the same pathway. A typical example is an SSP that is not on AWS connecting to a DSP that uses RTB Fabric.

Internal to external – Requester applications send requests to RTB Fabric requester gateways, which forward them through links to external RTB Fabric responder gateways. External responder gateways forward requests to a single responder application that is external to RTB Fabric (not an RTB Fabric customer) and can be located on or outside AWS. The external application processes requests and returns responses through the same pathway. A typical example is an SSP that uses RTB Fabric to connect to a DSP that is not on AWS.

AWS Management Console – The console is a browser-based interface that you can use to create and manage RTB Fabric gateways and links. Sign in to the AWS Management Console and open the RTB Fabric console at https://console.aws.amazon.com/rtbfabric.

AWS CloudFormation – Provides templates to create and manage RTB Fabric resources as code. You can use AWS CloudFormation to automate the deployment and configuration of gateways and links. For more information, see the .

AWS Command Line Interface – Provides commands for a broad set of AWS services, including RTB Fabric. It's supported on Windows, macOS, and Linux. For more information about getting started with the AWS CLI, see the AWS Command Line Interface User Guide.

AWS SDKs – Provide language-specific APIs and take care of many of the connection details, such as calculating signatures, handling request retries, and error handling. For more information, see AWS SDKs and Tools Reference Guide.

HTTPS API – Provides programmatic access to RTB Fabric and AWS. The HTTPS API lets you issue HTTPS requests directly to the service. When you use the HTTPS API, you must include code to digitally sign requests using your credentials. For more information, see the AWS RTB Fabric API Reference.