AWS prescriptive-guidance documentation change
Summary
Changed header from 'Survey' to 'Note', updated image paths, and removed italic formatting from section header
Security assessment
Cosmetic and formatting changes only; no security content modifications
Diff
diff --git a/prescriptive-guidance/latest/privacy-reference-architecture/global-expansion.md b/prescriptive-guidance/latest/privacy-reference-architecture/global-expansion.md index 210b7beee..a6eadbfc2 100644 --- a//prescriptive-guidance/latest/privacy-reference-architecture/global-expansion.md +++ b//prescriptive-guidance/latest/privacy-reference-architecture/global-expansion.md @@ -11 +11 @@ Central landing zone with managed RegionsRegional landing zonesAWS European Sove -###### Survey +###### Note @@ -40 +40 @@ To define key architecture design components, work closely with your compliance -###### The following are three approaches you can use to plan your AWS multi-account strategy, in ascending order of infrastructure segregation: +The following are three approaches you can use to plan your AWS multi-account strategy, in ascending order of infrastructure segregation: @@ -72 +72 @@ The following diagram shows a centralized landing zone with Regional deployments - + @@ -84 +84 @@ The following diagram shows separate landing zones in two Regions. - +