AWS wellarchitected: Rewrite ADVREL07-BP01 for privacy-preserving fault tolerance
Summary
Replaces the generic failure-tolerance best practice (cell-based architecture, AZ spreading, static stability) with a privacy-centric resilience practice: multi-Region KMS key access for AWS Clean Rooms, fail-closed circuit breakers when privacy controls cannot be verified, durable tracking and monitoring of differential privacy budget consumption, and runbook ownership for exposure decisions. Updates anti-patterns, benefits, implementation steps, related documents/services, and the page breadcrumb/navigation text.
Security assessment
The added guidance is defensive security documentation rather than a fix for a specific vulnerability: it mandates fail-closed behavior to avoid exposing partner records, requires KMS Multi-Region keys so collaboration encryption keys remain available, and requires durable tracking of the differential privacy budget so replayed queries cannot double-spend it. These are privacy/encryption hardening and availability-preserving controls, with no CVE or incident referenced.
Evidence
+Configure circuit breakers to fail closed when privacy controls can't be verified. A fail-closed circuit breaker halts collaboration until controls verify, at the cost of availability. A fail-open circuit breaker keeps queries flowing but risks exposing partner records or overspending the budget. One unverified exposure harms the partner relationship more than a measured outage.
Diff
diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advrel07-bp01.md b/wellarchitected/latest/video-streaming-advertising-lens/advrel07-bp01.md index 447a562..7f3ae25 100644 --- a//wellarchitected/latest/video-streaming-advertising-lens/advrel07-bp01.md +++ b//wellarchitected/latest/video-streaming-advertising-lens/advrel07-bp01.md @@ -7 +7 @@ -Implementation guidanceKey AWS servicesResources +Implementation guidanceResources @@ -9 +9 @@ Implementation guidanceKey AWS servicesResources -# ADVREL07-BP01 Design your workloads to withstand failures of individual components, such as compute instances, queues, databases, and caches +# ADVREL07-BP01 Design resilient architectures with privacy-preserving fault tolerance @@ -11 +11 @@ Implementation guidanceKey AWS servicesResources -Build building resilient advertising systems by identifying critical components, and implement fault tolerance through cell-based architectures and distributed resources across Availability Zones. +Deploy privacy-enhancing data collaboration environments across multiple regions with replicated privacy policies, differential privacy budgets, and encrypted collaboration configurations so that privacy-protected analytics continue during regional outages. @@ -13 +13,27 @@ Build building resilient advertising systems by identifying critical components, -## Implementation guidance +**Desired outcome:** + + * Privacy-enhanced collaboration environments remain available during regional failures with privacy controls intact. + + * Failover procedures preserve privacy policies, differential privacy budgets, and cryptographic configurations. + + * Circuit breakers fail-closed when privacy controls can't be verified, so that collaboration halts rather than proceeding without privacy protection. + + + + +**Common anti-patterns:** + + * Circuit breakers that fail open, which lets collaboration proceed without verified privacy controls. + + * Single-region AWS Clean Rooms setup with no cross-region KMS key access, so a regional outage halts privacy-protected analytics. + + * No monitoring of differential privacy budget, so budget exhaustion halts queries without warning. + + * Failover procedures that restore compute but not the privacy policies, budgets, and cryptographic configuration. + + + + +**Benefits of establishing this best practice:** + + * Privacy-enhanced collaboration stays available during regional failures with privacy controls intact. @@ -15 +41 @@ Build building resilient advertising systems by identifying critical components, -Determine which components of your workload are in a critical path to maintain operations for real-time bidding, ad serving, and other crucial functions. Identify AWS services that provide built-in fault tolerance mechanisms which are within your workload's response time, RTO, and RPO targets. Use cell-based architectures, with resources spread across multiple availability zones, to reduce the scope of a disruptive event. Where consistent communications are necessary, implement static stability mechanisms to reduce the dependency on control plane actions. + * Fail-closed circuit breakers guarantee collaboration halts rather than proceeding without privacy protection. @@ -17 +43 @@ Determine which components of your workload are in a critical path to maintain o -## Key AWS services + * Budget monitoring alerts measurement teams before exhaustion disrupts queries. @@ -19 +44,0 @@ Determine which components of your workload are in a critical path to maintain o - * [Amazon Simple Queue Service (Amazon SQS)](https://aws.amazon.com/sqs/) @@ -21 +45,0 @@ Determine which components of your workload are in a critical path to maintain o - * [Amazon DynamoDB](https://aws.amazon.com/dynamodb/) @@ -23 +46,0 @@ Determine which components of your workload are in a critical path to maintain o - * [Amazon ElastiCache](https://aws.amazon.com/elasticache/) @@ -25 +48 @@ Determine which components of your workload are in a critical path to maintain o - * [AWS Lambda](https://aws.amazon.com/lambda/) +**Level of risk exposed if this best practice is not established:** High @@ -27 +50,9 @@ Determine which components of your workload are in a critical path to maintain o - * [Amazon API Gateway](https://aws.amazon.com/api-gateway/) +## Implementation guidance + +Treat privacy state as unique, with its own failover considerations. For example, a Clean Rooms session keeps encryption contexts in memory, and Nitro Enclave attestation binds to the hardware that produced it. Neither of these survives a move to another Region, so recovery must rebuild these protections from durable configuration. + +The differential privacy budget measures information extraction across queries, and consumption moves in one direction only. A failover can replay a query, and replaying spends the budget twice. Enclave memory hides the duplicate spend, so track the budget durably in DynamoDB. Then you can recognize and refuse the second execution. + +Configure circuit breakers to fail closed when privacy controls can't be verified. A fail-closed circuit breaker halts collaboration until controls verify, at the cost of availability. A fail-open circuit breaker keeps queries flowing but risks exposing partner records or overspending the budget. One unverified exposure harms the partner relationship more than a measured outage. + +The team that negotiated the collaboration agreement defines acceptable exposure. Measurement teams consume the budget and need visibility into how much remains. Assign both responsibilities in a runbook before an incident. @@ -29 +60 @@ Determine which components of your workload are in a critical path to maintain o - * [AWS Auto Scaling](https://aws.amazon.com/autoscaling/) +### Implementation steps @@ -31 +62 @@ Determine which components of your workload are in a critical path to maintain o - * [AWS Availability Zones and Regions](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) + 1. **Deploy Clean Rooms collaborations with Multi-Region KMS key access:** Configure Clean Rooms with KMS Multi-Region keys so that collaboration encryption keys are available in both the primary and failover regions. Test key access from the failover region before any DR exercise. @@ -33 +64 @@ Determine which components of your workload are in a critical path to maintain o - * [AWS Elastic Load Balancing](https://aws.amazon.com/elasticloadbalancing/) + 2. **Implement circuit breakers with privacy-first fail-closed logic:** For all privacy-enhanced computation workflows, implement circuit breakers that halt operations when: differential privacy budget is exhausted, cryptographic attestation verification fails, or privacy policy enforcement can't be confirmed. These circuit breakers should fail closed (halt computation) rather than failing open (continue without privacy protections). @@ -35 +66 @@ Determine which components of your workload are in a critical path to maintain o - * [Monitoring and Alerting](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) + 3. **Monitor differential privacy budget consumption:** Publish differential privacy budget consumption as a custom CloudWatch metric. Configure alarms at 75% and 95% budget consumption to alert measurement teams before budget exhaustion halts queries. Implement budget distribution policies that limit how much of the period's budget any single measurement workflow can consume. @@ -42 +73,19 @@ Determine which components of your workload are in a critical path to maintain o - * [Reducing the Scope of Impact with Cell-Based Architecture](https://docs.aws.amazon.com/wellarchitected/latest/reducing-scope-of-impact-with-cell-based-architecture/reducing-scope-of-impact-with-cell-based-architecture.html) +**Related best practices:** + + * [ADVREL07-BP02 Maintain data consistency and availability across collaboration workflows](./advrel07-bp02.html) + + * [ADVREL04-BP02 Architect defensively against failures](./advrel04-bp02.html) + + + + +**Related documents:** + + * [AWS Clean Rooms documentation](https://docs.aws.amazon.com/clean-rooms/latest/userguide/what-is.html) + + * [AWS Nitro Enclaves](https://docs.aws.amazon.com/enclaves/latest/user/nitro-enclave.html) + + + + +**Related services:** @@ -44 +93 @@ Determine which components of your workload are in a critical path to maintain o - * [Static stability using Availability Zones](https://aws.amazon.com/builders-library/static-stability-using-availability-zones/) + * [AWS Clean Rooms](https://aws.amazon.com/clean-rooms/) @@ -46 +95 @@ Determine which components of your workload are in a critical path to maintain o - * [Control planes and data planes](https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/control-planes-and-data-planes.html) + * [Amazon Route 53](https://aws.amazon.com/route53/) @@ -57 +106 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Failure and recovery +Privacy-enhanced collaboration reliability @@ -59 +108 @@ Failure and recovery -ADVREL07-BP02 Implement a backup strategy which would meet RTO and RPO objectives +ADVREL07-BP02 Maintain data consistency and availability across collaboration workflows