AWS wellarchitected: Restructure ADVREL03 reliability guidance for single/Multi-Region
Summary
Rewrites the ADVREL03 reliability question page: renames headings, adds a 'Capability intent' section and 'Common issues to watch for' list, updates best-practice links/titles (e.g., 'full regional deployment'), and rephrases the question text. Content is reliability-focused, not security-focused.
Security assessment
The only vaguely security-adjacent line mentions data residency regulations, which is a compliance/reliability consideration, not a vulnerability fix or security control. The remainder is editorial restructuring of reliability guidance (Auto Scaling, AZ failover, capacity reservation) with no auth, encryption, IAM, or exposure content.
Evidence
+ * Selecting AWS Regions based purely on geographic proximity without considering data residency regulations for advertising audience data.
Diff
diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advrel03.md b/wellarchitected/latest/video-streaming-advertising-lens/advrel03.md index 1ac29af..d29ed9f 100644 --- a//wellarchitected/latest/video-streaming-advertising-lens/advrel03.md +++ b//wellarchitected/latest/video-streaming-advertising-lens/advrel03.md @@ -7 +7 @@ -# Design for single- and Multi-Region deployments +Capability intentCommon issues to watch for @@ -9 +9,5 @@ -ADVREL03: How have you designed application to achieve reliability in single- and multi- Region deployments? +# Single and Multi-Region deployments + +There are multiple strategies for achieving reliability in single and Multi-Region deployments. Implement full regional deployment using auto scaling and container orchestration. Select AWS Regions based on legal and disaster recovery requirements. Configure databases with appropriate reliability and recovery strategies. Manage service capacity through proper resource reservation and load testing. Focus on building resilient architectures that balance performance, compliance, and cost considerations. + +ADVREL03: How do you design your advertising workload for resilient single-region and Multi-Region deployments? @@ -10,0 +15,14 @@ ADVREL03: How have you designed application to achieve reliability in single- an +[ADVREL03-BP01 Use a full regional deployment for compute resources through Auto Scaling groups and compute container orchestrators](./advrel03-bp01.html) +[ADVREL03-BP02 Choose AWS Regions that meet your legal and disaster recovery requirements](./advrel03-bp02.html) +[ADVREL03-BP03 Deploy stateful dependencies across multiple Availability Zones](./advrel03-bp03.html) +[ADVREL03-BP04 Reserve appropriate capacity of services in the supported regions](./advrel03-bp04.html) + +## Capability intent + + * Compute resources are distributed across multiple Availability Zones behind zone-aware load balancers, enabling automatic recovery from Availability Zone-level failures without manual intervention. + + * AWS Region selection accounts for both legal data residency requirements and disaster recovery needs for your advertising workloads. + + * Databases span multiple Availability Zones with failover strategies calibrated to your component-level RTO and RPO. + + * Service capacity reservations are sized based on load test results to handle peaks without manual intervention. @@ -12 +29,0 @@ ADVREL03: How have you designed application to achieve reliability in single- an -There are multiple strategies for achieving reliability in single and multi-Region deployments. Implement full Regional deployment using auto scaling and container orchestration. Select AWS Regions based on legal and disaster recovery requirements. Configure your databases with appropriate reliability and recovery strategies. Manage service capacity through proper resource reservation and load testing. @@ -14 +30,0 @@ There are multiple strategies for achieving reliability in single and multi-Regi -Focus on building resilient architectures that balance performance, compliance, and cost considerations. @@ -16 +31,0 @@ Focus on building resilient architectures that balance performance, compliance, -###### Best practices @@ -18 +33 @@ Focus on building resilient architectures that balance performance, compliance, - * [ADVREL03-BP01 Use a full Regional deployment for compute resources through Auto Scaling groups and compute container orchestrators](./advrel03-bp01.html) +## Common issues to watch for @@ -20 +35 @@ Focus on building resilient architectures that balance performance, compliance, - * [ADVREL03-BP02 Choose AWS Regions that meet your legal and disaster recovery requirements](./advrel03-bp02.html) + * Deploying compute across multiple Availability Zones but not implementing zone-aware routing, resulting in unnecessary cross-AZ data transfer costs. @@ -22 +37 @@ Focus on building resilient architectures that balance performance, compliance, - * [ADVREL03-BP03 Configure databases to span across multiple Availability Zones](./advrel03-bp03.html) + * Selecting AWS Regions based purely on geographic proximity without considering data residency regulations for advertising audience data. @@ -24 +39 @@ Focus on building resilient architectures that balance performance, compliance, - * [ADVREL03-BP04 Reserve appropriate capacity of services in the supported Regions](./advrel03-bp04.html) + * Using Multi-AZ database deployments for all components regardless of their actual RTO requirements, paying for failover capabilities that exceed what the business needs. @@ -35 +50 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -ADVREL02-BP03 Prevent scale mismatch of both internal services and external partners +ADVREL02-BP03 Avoid scale mismatch of both internal services and external partners @@ -37 +52 @@ ADVREL02-BP03 Prevent scale mismatch of both internal services and external part -ADVREL03-BP01 Use a full Regional deployment for compute resources through Auto Scaling groups and compute container orchestrators +ADVREL03-BP01 Use a full regional deployment for compute resources through Auto Scaling groups and compute container orchestrators