AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation, improved section headings, fixed image alt text punctuation, simplified service name references (EC2), and replaced hyphens with en dashes in OU-account links.
Security assessment
Changes are editorial and cosmetic in nature (punctuation, formatting, navigation). No security vulnerabilities, controls, or incidents are mentioned. The core security content remains unchanged, and the modifications don't introduce new security guidance or address specific security weaknesses.
Diff
diff --git a/prescriptive-guidance/latest/security-reference-architecture/architecture.md b/prescriptive-guidance/latest/security-reference-architecture/architecture.md index a3b352510..d34029afe 100644 --- a//prescriptive-guidance/latest/security-reference-architecture/architecture.md +++ b//prescriptive-guidance/latest/security-reference-architecture/architecture.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Security Reference Architecture](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Security Reference Architecture (AWS SRA) – core architecture](introduction.html) @@ -12 +12 @@ The following diagram illustrates the AWS SRA. This architectural diagram brings -###### Note +###### Architecture diagrams @@ -18 +18 @@ To customize the reference architecture diagrams in this guide based on your bus - + @@ -20 +20 @@ To customize the reference architecture diagrams in this guide based on your bus -For this reference architecture, the actual web application and data tier are deliberately represented as simply as possible, through Amazon Elastic Compute Cloud (Amazon EC2) instances and an Amazon Aurora database, respectively. Most architecture diagrams focus and dive deep on the web, application, and data tiers. For readability, they often omit the security controls. This diagram flips that emphasis to show security wherever possible, and keeps the application and data tiers as simple as necessary to show security features meaningfully. +For this reference architecture, the actual web application and data tier are deliberately represented as simply as possible, through Amazon EC2 instances and an Amazon Aurora database, respectively. Most architecture diagrams focus and dive deep on the web, application, and data tiers. For readability, they often omit the security controls. This diagram flips that emphasis to show security wherever possible, and keeps the application and data tiers as simple as necessary to show security features meaningfully. @@ -26 +26 @@ The following sections walk through each OU and account to understand its object - * Brief overview of the element and its security purpose in the AWS SRA. For more detailed descriptions and technical information about individual services, see the [appendix](./appendix.html). + * Brief overview of the element and its security purpose in the AWS SRA. For more detailed descriptions and technical information about individual services, see [the appendix](./appendix.html). @@ -41 +41 @@ The following sections walk through each OU and account to understand its object - * [Security OU - Security Tooling account](./security-tooling.html) + * [Security OU – Security Tooling account](./security-tooling.html) @@ -43 +43 @@ The following sections walk through each OU and account to understand its object - * [Security OU - Log Archive account](./log-archive.html) + * [Security OU – Log Archive account](./log-archive.html) @@ -45 +45 @@ The following sections walk through each OU and account to understand its object - * [Infrastructure OU - Network account](./network.html) + * [Infrastructure OU – Network account](./network.html) @@ -47 +47 @@ The following sections walk through each OU and account to understand its object - * [Infrastructure OU - Shared Services account](./shared-services.html) + * [Infrastructure OU – Shared Services account](./shared-services.html) @@ -49 +49 @@ The following sections walk through each OU and account to understand its object - * [Workloads OU - Application account](./application.html) + * [Workloads OU – Application account](./application.html)