AWS Security ChangesHomeSearch

AWS wellarchitected: Ad ops data governance: retention, residency IAM boundaries

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

File: wellarchitected/latest/video-streaming-advertising-lens/advops01-bp04.md · Type: iam

Summary

Rewrites the ADVOPS01-BP04 best practice page, replacing generic residency/governance bullets with a structured guide: desired outcomes, anti-patterns, implementation guidance and steps covering data classification (AWS Glue Data Catalog tags), retention policies for agentic AI traces with PII redaction, governance of managed connectivity (RTB Fabric) logs, AWS Config compliance rules (encryption, CloudTrail, S3 policies), and IAM permission boundaries with aws:RequestedRegion conditions plus SCPs to enforce regional data residency. Related documents/services links and the page navigation footer are also updated.

Security assessment

This is best-practice documentation rather than a fix for a specific vulnerability or incident, so security_issue_related is false. However, it clearly documents security controls: IAM permission boundaries with aws:RequestedRegion conditions and Organizations SCPs to enforce data residency/authorization, AWS Config rules verifying encryption and CloudTrail enablement, access controls on connectivity logs, and PII redaction from agent traces. These are hardening/compliance guidance with real security impact, warranting medium severity rather than high (no vulnerability or credential/secret remediation is being made).

Evidence

  5. **Implement IAM Permission Boundaries for regional data residency:** For advertising workloads processing EU viewer data, configure IAM Permission Boundaries with aws:RequestedRegion conditions that restrict principals from creating resources or accessing data outside designated regions. Apply Service Control Policies (SCPs) at the AWS Organizations level to enforce region restrictions for advertising accounts handling EU or California resident data. Test boundary enforcement by attempting to create a restricted resource from outside the allowed region. 

Diff

diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advops01-bp04.md b/wellarchitected/latest/video-streaming-advertising-lens/advops01-bp04.md
index b304608..6ae32bb 100644
--- a//wellarchitected/latest/video-streaming-advertising-lens/advops01-bp04.md
+++ b//wellarchitected/latest/video-streaming-advertising-lens/advops01-bp04.md
@@ -7 +7 @@
-Implementation guidanceKey AWS servicesResources
+Implementation guidanceResources
@@ -11 +11,9 @@ Implementation guidanceKey AWS servicesResources
-Advertising data management requires robust governance and compliance procedures, especially in a multi-Region environment. This best practice verifies adherence to regional data privacy laws while maintaining operational efficiency across global advertising operations. 
+Advertising data management requires governance and compliance procedures for Multi-Region environments, where regional privacy laws vary by jurisdiction. Procedures must cover application logs, managed connectivity service logs, and agentic AI agent traces. 
+
+**Desired outcome:**
+
+  * Data governance procedures cover all layers of the advertising stack, such as application logs, managed connectivity service logs (RTB Fabric), and agentic AI agent traces and reasoning chains. 
+
+  * Retention policies, access controls, and compliance monitoring are defined per data type and jurisdiction (GDPR for EU data, CCPA for California data, and COPPA for child-directed content). 
+
+  * Agent traces from agentic AI advertising workflows have documented retention policies that balance operational needs with data minimization principles. 
@@ -13 +20,0 @@ Advertising data management requires robust governance and compliance procedures
-## Implementation guidance
@@ -15 +21,0 @@ Advertising data management requires robust governance and compliance procedures
-  * For data residency compliance alignment: 
@@ -17 +22,0 @@ Advertising data management requires robust governance and compliance procedures
-    * Implement landing zone controls for different geographical Regions 
@@ -19 +24 @@ Advertising data management requires robust governance and compliance procedures
-    * Configure data boundary controls using AWS Control Tower 
+**Common anti-patterns:**
@@ -21 +26 @@ Advertising data management requires robust governance and compliance procedures
-    * Set up guardrails for data movement between Regions 
+  * Treating managed connectivity service logs as equivalent to application logs without recognizing that they may contain partner identifiers and traffic management decisions subject to separate compliance requirements. 
@@ -23 +28 @@ Advertising data management requires robust governance and compliance procedures
-    * Monitor and enforce data locality requirements 
+  * Retaining agentic AI agent traces indefinitely without a defined retention policy, accumulating campaign data, audience information, and automated decisions without audit controls. 
@@ -25 +30 @@ Advertising data management requires robust governance and compliance procedures
-  * For data governance: 
+  * Applying a single data retention policy to all advertising data regardless of jurisdiction, data type, or consent scope. 
@@ -27 +31,0 @@ Advertising data management requires robust governance and compliance procedures
-    * Establish data classification policies for advertising data types 
@@ -29 +32,0 @@ Advertising data management requires robust governance and compliance procedures
-    * Implement data retention and archival procedures 
@@ -31 +33,0 @@ Advertising data management requires robust governance and compliance procedures
-    * Set up access controls and encryption policies 
@@ -33 +35 @@ Advertising data management requires robust governance and compliance procedures
-    * Configure audit logging and compliance reporting 
+**Benefits of establishing this best practice:**
@@ -35 +37 @@ Advertising data management requires robust governance and compliance procedures
-  * For regulatory compliance alignment: 
+  * Enables proactive identification of compliance gaps before they become enforcement actions. 
@@ -37 +39 @@ Advertising data management requires robust governance and compliance procedures
-    * Implement GDPR requirements for EU user data 
+  * Supports multi-framework compliance (GDPR, CCPA, COPPA, IAB TCF, and TAG) from a single data governance architecture. 
@@ -39 +41 @@ Advertising data management requires robust governance and compliance procedures
-    * Set up consent management systems 
+  * Reduces audit preparation time by maintaining ongoing compliance evidence. 
@@ -41 +42,0 @@ Advertising data management requires robust governance and compliance procedures
-    * Monitor compliance with regional advertising laws 
@@ -44,0 +46,7 @@ Advertising data management requires robust governance and compliance procedures
+**Level of risk exposed if this best practice is not established:** High 
+
+## Implementation guidance
+
+Advertising data governance spans multiple regulatory frameworks, and a single bid request may contain data subject to multiple regulatory frameworks at once. Classify data at collection time, and enforce retention and access policies at the storage and processing layers. This design avoids per-request regulatory routing logic. 
+
+Agent traces contain both personal data and the reasoning behind automated bid or audience decisions. Privacy regulations require you to discard the personal data promptly. Some jurisdictions require you to keep the reasoning for audit. Separate the reasoning from the personal data it referenced, so the decision record survives without the identifiers that made it sensitive. 
@@ -46 +54 @@ Advertising data management requires robust governance and compliance procedures
-## Key AWS services
+Connectivity-layer logs are another category without a clear owner. Network infrastructure produces them, which suggests the network team, but their contents are commercial, such as which partners sent what volume, and which requests were throttled or filtered. That data is competitively sensitive information about counterparties, with an exposure profile distinct from bid data. Because the infrastructure team treats them as operational and the advertising team might not know they exist, the logs accumulate without a retention period. Classify connectivity-layer logs as their own category, distinct from bid logs, to prevent this default. 
@@ -48 +56 @@ Advertising data management requires robust governance and compliance procedures
-  * AWS Control Tower 
+Enforce residency at the account and permission layer. When you enforce residency in application logic, each service must implement the restriction separately. The control is only as strong as the newest service written by the team least aware of the requirement. A newly added service can violate the restriction without triggering an alert. At the account and permission layer, residency becomes a property of the environment, so the restriction applies regardless of what any individual service does. Account-level controls are coarser, though, so test them against real workflows first. They can block legitimate work with confusing permission errors rather than clear policy messages. 
@@ -50 +58 @@ Advertising data management requires robust governance and compliance procedures
-  * AWS Organizations 
+### Implementation steps
@@ -52 +60 @@ Advertising data management requires robust governance and compliance procedures
-  * AWS Config 
+  1. **Classify advertising data by regulatory scope and retention requirement:** Create a data classification inventory covering each data type (bid requests, impression logs, user profiles, campaign configurations, agent traces, and connectivity logs). For each type, document: applicable regulations, maximum retention period, required access controls, encryption requirements, and the team responsible for enforcement. Use AWS Glue Data Catalog to register classifications as metadata tags on data assets. 
@@ -54 +62 @@ Advertising data management requires robust governance and compliance procedures
-  * AWS CloudTrail 
+  2. **Define retention policies for agentic AI agent traces:** Establish separate retention policies for agent traces based on their content sensitivity. For traces containing targeting data and audience information, apply retention limits aligned with the underlying data's consent scope (typically 30–90 days). For traces used for model optimization and debugging, apply minimum retention for operational utility. Implement automated redaction of sensitive fields (audience identifiers, PII) from agent traces before long-term storage using AWS Glue ETL jobs. 
@@ -56 +64 @@ Advertising data management requires robust governance and compliance procedures
-  * Amazon Macie 
+  3. **Establish data governance for managed connectivity service logs:** Define ownership for RTB Fabric or equivalent managed connectivity logs as a distinct data category. Document retention periods (typically 30 days for operational debugging, shorter for partner identifier data), access controls (limit access to network operations and security teams), and the review process for logs containing partner commercial data. Configure Amazon CloudWatch Logs delivery for connectivity logs with appropriate log group retention settings. 
@@ -58 +66 @@ Advertising data management requires robust governance and compliance procedures
-  * AWS Local Zones 
+  4. **Deploy ongoing compliance monitoring with AWS Config:** Create custom AWS Config rules that verify: encryption is enabled on all data stores containing advertising data, CloudTrail is active in all regions processing advertising data, S3 buckets with audience data have appropriate bucket policies, and data stores have lifecycle policies configured. Set Config rules to evaluate on configuration change and periodically. Route noncompliant findings to AWS Security Hub for centralized tracking. 
@@ -60 +68 @@ Advertising data management requires robust governance and compliance procedures
-  * AWS Identity and Access Management
+  5. **Implement IAM Permission Boundaries for regional data residency:** For advertising workloads processing EU viewer data, configure IAM Permission Boundaries with aws:RequestedRegion conditions that restrict principals from creating resources or accessing data outside designated regions. Apply Service Control Policies (SCPs) at the AWS Organizations level to enforce region restrictions for advertising accounts handling EU or California resident data. Test boundary enforcement by attempting to create a restricted resource from outside the allowed region. 
@@ -67 +75,14 @@ Advertising data management requires robust governance and compliance procedures
-  * [Best Practices for managing data residency in AWS Local Zones using landing zone controls](https://aws.amazon.com/blogs/compute/best-practices-for-managing-data-residency-in-aws-local-zones-using-landing-zone-controls/)
+**Related documents:**
+
+  * [Data Residency with Hybrid Cloud Services Lens](https://docs.aws.amazon.com/wellarchitected/latest/data-residency-hybrid-cloud-services-lens/data-residency-with-hybrid-cloud-services-lens.html)
+
+  * [Configuring RTB Fabric logs with Amazon CloudWatch Logs](https://docs.aws.amazon.com/rtb-fabric/latest/userguide/monitoring-cloudwatch-logs.html)
+
+  * [Amazon Bedrock Agent Tracing documentation](https://docs.aws.amazon.com/bedrock/latest/userguide/trace-events.html)
+
+
+
+
+**Related services:**
+
+  * [AWS Control Tower](https://aws.amazon.com/controltower/)
@@ -69 +90 @@ Advertising data management requires robust governance and compliance procedures
-  * [General Data Protection Regulation (GDPR) Center](https://aws.amazon.com/compliance/gdpr-center/)
+  * [AWS Config](https://aws.amazon.com/config/)
@@ -71 +92 @@ Advertising data management requires robust governance and compliance procedures
-  * [Scale across borders: build a multi-Region architecture while maintaining data residency](https://community.aws/content/2dhVhtsciD5gVBlCKUlHoszrDzU/scale-beyond-borders?lang=en#aws-reference-architecture-for-multiregion-with-data-residency)
+  * [Amazon Macie](https://aws.amazon.com/macie/)
@@ -84 +105 @@ ADVOPS01-BP03 Establish performance metrics by defining key performance indicato
-Prepare
+ADVOPS01-BP05 Foster a publisher operations culture that prioritizes yield reliability