AWS First Steps
New feature

AWS RTB Fabric now supports configurable Availability Zone affinity

AWS RTB Fabric now allows configuration of responder gateway Availability Zone affinity, enabling client routing policies to prioritize the requester's zone or utilize all zones spanned by the gateway.

AWS RTB Fabric now supports configurable availability zone (AZ) affinity for responder gateways, letting partners choose to connect to their own AZ or any crossed AZ. This helps AdTech companies use infrastructure more efficiently with no extra cost to RTB Fabric. Demand-side and supply-side platforms deploy bidding systems across multiple AZs. Previously, AWS RTB Fabric sent requests only to the requester's AZ gateway capacity, potentially leaving other AZ capacity unused. Now, clients can set routing policies to control this, prioritizing the requester's zone to avoid cross-boundary delays or using all AZs that the responder gateway spans to offer more gateway capacity per requester. Configurable AZ affinity is available in all AWS regions where AWS RTB Fabric is offered. Review the AWS RTB Fabric user guide fleet requirements before enabling. AWS RTB Fabric connects AdTech partners such as Amazon Advertising, GumGum, Kargo, MobileFuse, Sovrn, TripleLift, Viant, and Yieldmo in three steps, providing single-digit millisecond latency over a private, high-performance network. It reduces standard cloud network costs by up to 80% with no prerequisites. AWS RTB Fabric is generally available in US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (Ireland).

Why it matters

AWS RTB Fabric is a solution for connecting with AdTech partners, and this update allows control over responder gateway Availability Zone connections, improving infrastructure efficiency for AdTech companies.

Read the original AWS announcement

Related articles and terms

AWS Availability Zone Design - How Physical Separation and Fault Isolation Create a Reliability AdvantageExamine the design philosophy behind AWS AZs as physically independent data center clusters, compare them with Azure and GCP availability zones, and look at them against the published design criteria and real-world incident examples.Why AWS Availability Zone IDs Differ Per Account - The Design Intent Behind AZ MappingExplains how us-east-1a maps to different physical AZs per account, why AZ IDs (use1-az1) were introduced, the design intent of even capacity distribution, and considerations for cross-account AZ specification.AWS Local ZonesAn infrastructure extension that places AWS compute, storage, and database services closer to major metropolitan areas, delivering single-digit millisecond latency to end usersBuilding Private Blockchains with Amazon Managed Blockchain - Operating Hyperledger FabricLearn how to build a private blockchain network with Hyperledger Fabric, develop chaincode, and manage member governance.AWS Fault Domain Design - How the Three-Layer Structure of AZs, Regions, and Partitions Protects AvailabilityLearn why AWS infrastructure is designed with three layers of fault domains - AZs (fault isolation), Regions (geographic separation), and Partitions (political separation) - and how far failures propagate at each layer, with real-world examples.