How to Connect External Applications to RTB Fabric on AWS

Select Language:

If you’re a partner looking to connect your external RTB applications to AWS RTB Fabric, here’s a simple guide to help you get started.

First, even if your applications are running outside of AWS, you’ll need an AWS account. To use the external link feature, you must enable it through the Service Quotas tool. This option is not turned on by default, so you’ll need to opt in explicitly.

Next, connecting your external applications to RTB Fabric is done using external links. These links create a bridge between your application and the RTB gateways. If possible, traffic will route over AWS’s Global Network, which is fast and secure. However, when necessary, the traffic can travel over the public internet to reach external endpoints. This means your data might initially travel over the internet, then continue through AWS infrastructure.

To receive external traffic, you will create an external responder gateway. This gateway is specifically designed to accept connections from outside RTB Fabric. If your goal is to send traffic out to external partners, you will set up outbound external links from your requester gateway.

Creating links varies based on whether you’re sending or receiving data:

Outbound external links, which send data to external partners, can be set up using the AWS console, API, CLI, or CloudFormation.
Inbound external links, which accept data from outside sources, can only be created and managed through the API, CLI, or CloudFormation — not through the console.

Remember that links are created by requester gateways and need to be accepted by the owner of the responder gateway before they become active.

Some key points to note about external links:

The original client IP addresses are preserved, especially in inbound links, allowing targeted filtering and geographic targeting.
Traffic travels over the AWS Global Network when possible and switches to the public internet when necessary.
The console supports inbound external links only to a limited extent.

For organizations connecting outside AWS, the recommended architecture involves:

Ensuring you have an AWS account with external link capabilities turned on.
Creating the appropriate gateway type—an external responder gateway for receiving, or outbound external links for sending.
Managing link creation and acceptance through the RTB Fabric API, CLI, or CloudFormation.
Relying on both the AWS Global Network and the internet as needed to establish a reliable connection.

It’s best to reach out to an AWS solution architect for personalized advice and to ensure your setup meets your specific needs. They can help you plan and implement your external links smoothly.

Sources: