AWS Security ChangesHomeSearch

AWS wellarchitected: Clarify least-network path with PrivateLink and residency

Service: wellarchitected · 2026-11-11 · Documentation medium

File: wellarchitected/latest/video-streaming-advertising-lens/advperf01-bp01.md · Type: network

Summary

Expands the performance best practice for network path selection, adding PrivateLink for same-Region DSP/SSP traffic, Clean Rooms placement guidance, data residency considerations, and routing validation steps.

Security assessment

The change documents private connectivity using AWS PrivateLink, keeping bid traffic off the public internet and reducing network exposure, but it does not address a specific vulnerability, CVE, or incident.

Evidence

+  * Keeping traffic on the AWS backbone reduces round-trip latency, lowers data transfer costs, and shrinks network exposure surface.

Diff

diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advperf01-bp01.md b/wellarchitected/latest/video-streaming-advertising-lens/advperf01-bp01.md
index 1d80c8f..d90c62a 100644
--- a//wellarchitected/latest/video-streaming-advertising-lens/advperf01-bp01.md
+++ b//wellarchitected/latest/video-streaming-advertising-lens/advperf01-bp01.md
@@ -7 +7 @@
-Implementation guidanceKey AWS servicesResources
+Implementation guidanceResources
@@ -11 +11,38 @@ Implementation guidanceKey AWS servicesResources
-Design for the least-network path, but keep regulatory needs in consideration. Use the AWS backbone network to improve latency. 
+Design for the least-network path between publishers, SSPs, DSPs, and data partners. Route traffic over the AWS backbone network using geographic proximity and keep same-cloud partner traffic off the public internet. 
+
+**Desired outcome:**
+
+  * Your workloads route traffic over the shortest possible path using AWS backbone infrastructure. 
+
+  * Latency is minimized for end users and integrated partners, while data residency and compliance obligations are satisfied by design. 
+
+  * Same-region DSP-to-SSP traffic flows over [AWS PrivateLink](https://aws.amazon.com/privatelink/) rather than the public internet. 
+
+  * [AWS Clean Rooms](https://aws.amazon.com/clean-rooms/) collaborations run within a single Region, avoiding cross-region transfer latency. 
+
+
+
+
+**Common anti-patterns:**
+
+  * Routing traffic between two AWS-hosted parties (such as a DSP and SSP) over the public internet when AWS PrivateLink could keep that traffic private and local. 
+
+  * Deploying all compute in a single Region regardless of where requests originate, when geolocation-aware routing would serve distant users faster. 
+
+  * Using the same Route 53 routing policy for all traffic types without distinguishing between latency-sensitive bid requests and batch analytics workloads. 
+
+
+
+
+**Benefits of establishing this best practice:**
+
+  * Keeping traffic on the AWS backbone reduces round-trip latency, lowers data transfer costs, and shrinks network exposure surface. 
+
+  * Geolocation-aware routing gives you a foundation to address data residency requirements proactively, reducing compliance risk as your architecture scales. 
+
+  * Private connectivity between same-region partners removes public internet routing variability from the bid response path. 
+
+
+
+
+**Level of risk exposed if this best practice is not established:** High 
@@ -15 +52 @@ Design for the least-network path, but keep regulatory needs in consideration. U
-Implement Amazon Route 53 (fail-over and geolocation routing) to route traffic to the target load balancers and compute workloads in the closest Region to the origination of intake requests. This architecture may help align with specific compliance and residency needs. Consult with legal counsel for guidance tailored to your specific use case and jurisdiction. 
+Programmatic advertising latency budgets are tight. The industry standard for a complete bid round-trip (from publisher ad request to DSP response) is typically under 100 ms. Network path selection reduces this budget without changing application code. 
@@ -17 +54 @@ Implement Amazon Route 53 (fail-over and geolocation routing) to route traffic t
-Implement AWS PrivateLink on the same Region between external entities (like DSPs and SSPs) where both parties are on AWS. 
+The regional deployment for a request is chosen upstream, before any packet reaches your workload. Physics bounds the outcome: no downstream tuning can make a transoceanic request fast. Placement determines the minimum latency. In-region path quality determines the variance. Optimizing path while getting placement wrong is the common mistake. In-region tuning is measurable, whereas the transoceanic hop is invisible in the metrics of any single service. 
@@ -19 +56 @@ Implement AWS PrivateLink on the same Region between external entities (like DSP
-For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to have collaborators in the same Region as the clean room to avoid latency with cross-Region data transfer. 
+In a deadline-driven auction, variance matters more than the mean. The bid deadline is absolute, and late requests are equal to undelivered requests. AWS measurements show a larger improvement in jitter than in first-byte latency for the backbone compared to public-internet paths. A path with a good median but an unpredictable tail misses auctions at the tail. 
@@ -21 +58 @@ For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to h
-## Key AWS services
+Bid traffic carries pricing signals and audience attributes. Keeping it off the public internet removes a class of observation that competitors or intermediaries can otherwise perform on volume and timing patterns alone. This benefit applies even when the path is not measurably faster. 
@@ -23 +60 @@ For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to h
-  * [Amazon Route 53 (R53)](https://aws.amazon.com/route53/)
+Routing traffic to the nearest deployment usually keeps data inside its jurisdiction, because viewers and their data are co-located. When the nearest deployment is outside the required jurisdiction, the residency requirement is non-negotiable. Define the candidate regions from residency, then pick among those by latency. Routing rules that satisfy residency without documenting the intent are fragile: the next engineer tuning for latency cannot tell which rules exist for compliance. 
@@ -25 +62 @@ For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to h
-  * [AWS PrivateLink](https://aws.amazon.com/privatelink/)
+In multi-party collaboration, placement is set by where the joint computation runs. Data contributed from elsewhere must move before it can be matched, and that transfer is both a latency cost and a residency event. Negotiate placement with counterparties before the collaboration is live. 
@@ -27 +64,11 @@ For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to h
-  * [AWS Clean Rooms](https://aws.amazon.com/clean-rooms/)
+### Implementation steps
+
+  1. **Configure Route 53 geographic routing for regional workloads:** Set up Route 53 with geolocation and failover routing policies to direct incoming bid requests to the load balancers and compute resources in the Region geographically closest to the request origin. Use weighted routing within a region to distribute load across multiple availability zones. Test routing behavior by simulating requests from each geographic zone before going live. 
+
+  2. **Establish AWS PrivateLink for same-region DSP/SSP connectivity:** For external partners (DSPs and SSPs) operating on AWS in the same Region, create AWS PrivateLink endpoint services so that bid traffic flows over a private VPC endpoint rather than the public internet. Document which partners use PrivateLink compared to public connectivity. Prioritize the highest-volume partner links for PrivateLink migration first. 
+
+  3. **Colocate Clean Rooms collaborators with the clean room:** When setting up AWS Clean Rooms collaborations for audience matching or campaign measurement, verify that all contributing parties store their source data in the same AWS region as the clean room. Document regional placement requirements as part of the collaboration onboarding checklist to guard against cross-region transfers being introduced unnoticed. 
+
+  4. **Validate routing with latency measurement:** After configuring geographic routing, measure round-trip latency from each major publisher or partner location to confirm that traffic is reaching the nearest regional endpoint. Use [Amazon CloudWatch Synthetics](https://aws.amazon.com/cloudwatch/) to run ongoing latency probes from multiple geographic origins. Establish baseline latency targets per region and set alarms when latency exceeds thresholds. 
+
+  5. **Document data residency constraints alongside routing policies:** For each Route 53 routing rule, annotate the data residency requirement it satisfies. This makes it possible to audit compliance intent alongside technical configuration, so that routing changes are reviewed against residency obligations before deployment. 
@@ -34 +81,18 @@ For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to h
-  * [Disaster Recovery Solutions with AWS managed services, Part 3: Multi-Site Active/Passive](https://aws.amazon.com/blogs/architecture/disaster-recovery-solutions-with-aws-managed-services-part-3-multi-site-active-passive/)
+**Related best practices:**
+
+  * [ADVPERF01-BP03 Design for low latency with appropriate compute, storage, and network considerations](./advperf01-bp03.html)
+
+  * [ADVSEC02-BP01 Encrypt DSP to SSP communication in transit using TLS](./advsec02-bp01.html)
+
+
+
+
+**Related documents:**
+
+  * [AWS Global Accelerator FAQs (latency and jitter measurements at p90)](https://aws.amazon.com/global-accelerator/faqs/)
+
+  * [Amazon Route 53 routing policies](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html)
+
+  * [AWS PrivateLink concepts](https://docs.aws.amazon.com/vpc/latest/privatelink/concepts.html)
+
+  * [Navigating GDPR compliance on AWS](https://aws.amazon.com/compliance/gdpr-center/)
@@ -36 +100,17 @@ For privacy-enhanced collaboration using AWS Clean Rooms, it is recommended to h
-  * [How Storygize and Sharethrough are using AWS PrivateLink to reduce costs and increase revenue](https://aws.amazon.com/blogs/industries/how-storygize-and-sharethrough-are-using-aws-privatelink-to-reduce-costs-and-increase-revenue/)
+
+
+
+**Related examples:**
+
+  * [Disaster Recovery Solutions with AWS managed services, Part 3: Multi-Site Active/Passive](https://aws.amazon.com/blogs/architecture/disaster-recovery-dr-architecture-on-aws-part-iii-pilot-light-and-warm-standby/)
+
+
+
+
+**Related services:**
+
+  * [Amazon Route 53](https://aws.amazon.com/route53/)
+
+  * [AWS PrivateLink](https://aws.amazon.com/privatelink/)
+
+  * [AWS Clean Rooms](https://aws.amazon.com/clean-rooms/)