AWS whitepapers documentation change
Summary
Updated publication date, fixed document history link, removed redundant 'Abstract' section, removed topics list, updated HTTP links to HTTPS, and made minor text/clarity improvements
Security assessment
The changes primarily involve formatting, link updates (HTTP->HTTPS), and content restructuring. While HTTPS links improve general security hygiene, there is no evidence these changes address a specific security vulnerability or add new security documentation. Security-related content about multi-account strategies appears to be existing guidance rather than new material.
Diff
diff --git a/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.md b/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.md index efe565880..6491f479c 100644 --- a//whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.md +++ b//whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.md @@ -5 +5 @@ -AbstractAre you Well-Architected?Introduction +Are you Well-Architected?Introduction @@ -9,3 +9 @@ AbstractAre you Well-Architected?Introduction -Publication date: **January 14, 2025** ([Document history](./doc-history.html)) - -## Abstract +Publication date: **April 30, 2025** ([Document history](./document-history.html)) @@ -15 +13 @@ Businesses that are starting to adopt Amazon Web Services (AWS), expanding their -Using multiple AWS accounts to help isolate and manage your business applications and data can help you optimize across most of the [AWS Well-Architected Framework](http://aws.amazon.com/architecture/well-architected/) pillars, including operational excellence, security, reliability, and cost optimization. This paper provides best practices and current recommendations for organizing your overall AWS environment. The extent to which you use these best practices depends on your stage of the cloud adoption journey and specific business needs. +Using multiple AWS accounts to help isolate and manage your business applications and data can help you optimize across most of the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) pillars, including operational excellence, security, reliability, and cost optimization. This paper provides best practices and current recommendations for organizing your overall AWS environment. The extent to which you use these best practices depends on your stage of the cloud adoption journey and specific business needs. @@ -27,17 +24,0 @@ Using multiple AWS accounts to help isolate and manage your business application -###### Topics - - * Multi-account strategy best practices and recommendations - - * AWS accounts - - * Stages of adoption - - * Best practices - - * Relation to AWS Well-Architected - - * Intended audience - - - - @@ -52 +33 @@ Customers need explicit security boundaries, a mechanism to have direct control -Using multiple AWS accounts to help isolate and manage your business applications and data can help you optimize across most of the [AWS Well-Architected Framework](http://aws.amazon.com/architecture/well-architected/) pillars including operational excellence, security, reliability, and cost optimization. +Using multiple AWS accounts to help isolate and manage your business applications and data can help you optimize across most of the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) pillars including operational excellence, security, reliability, and cost optimization. @@ -60 +41 @@ By default, no access is allowed between accounts. For example, if you designate -The number of accounts that best meets your needs can range from a few to hundreds or even thousands. Management of many accounts requires use of automation to help minimize your operational complexity and ensure efficient alignment with your security, governance, and operational requirements. AWS does not charge per account. Rather, you incur charges based on resources used, regardless of account quantity. +The number of accounts that best meets your needs can range from a few to hundreds or even thousands. Management of many accounts requires use of automation to help minimize your Multi-account strategy best practices and recommendations 2 operational complexity and ensure efficient alignment with your security, governance, and operational requirements. AWS does not charge per account. Rather, you incur charges based on resources used, regardless of account quantity. @@ -83 +64 @@ When initially adopting AWS, it's recommended to use a multi-account strategy ra -As your initial cloud projects demonstrate success, the motivation often arises to expand AWS adoption further across the organization. This leads to the foundation stage of the cloud adoption lifecycle. During this phase, you invest in evolving your core cloud capabilities, such as establishing center of excellence teams, automating provisioning, and implementing cost management best practices. Building this strong cloud foundation positions you for widespread enterprise-wide adoption down the line, allowing you to capitalize on the full breadth of benefits that AWS can provide. +As your initial cloud projects demonstrate success, the motivation often arises to expand AWS adoption further across the organization. This leads to the foundation stage of the cloud adoption lifecycle. During this phase, you invest in evolving your core cloud capabilities, such as establishing center of excellence teams, automating provisioning, and implementing cost management best practices. Building this strong cloud foundation positions you for widespread enterprise-wide adoption down the line, allowing you to capitalize on the full breadth of benefits that the AWS platform can provide. @@ -91 +72 @@ The best practices can help you quickly establish the initial cloud foundation o -While organizations often have similar cloud adoption needs, each has unique requirements. Therefore, these AWS multi-account best practices are intended as guidance, not a one-size-fits-all solution. Your specific AWS environment design might differ from the examples provided, but following these practices will help you make informed decisions as you plan your cloud strategy. +While organizations often have similar cloud adoption needs, each has unique requirements. Therefore, these AWS multi-account best practices are intended as guidance, not a one-size-fits-all solution. Your specific AWS environment design may differ from the examples provided, but following these practices will help you make informed decisions as you plan your cloud strategy. @@ -95 +76 @@ While organizations often have similar cloud adoption needs, each has unique req -[AWS Well-Architected](http://aws.amazon.com/architecture/well-architected) helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for their applications and workloads. Based on six pillars—operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability—AWS Well-Architected provides a consistent approach for customers and partners to evaluate architectures and implement designs that can scale over time. +[AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/) helps cloud architects build secure, high-performing, resilient, and efficient infrastructure for their applications and workloads. Based on six pillars—operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability—AWS Well-Architected provides a consistent approach for customers and partners to evaluate architectures and implement designs that can scale over time. @@ -105 +86 @@ These best practices are intended to apply to organizations largely independent -If you’re just starting to experiment and learn about AWS by using a single AWS account, you don't need to consider these best practices until you begin planning for your first few production workloads. +If you're just starting to experiment and learn about AWS by using a single AWS account, you don't need to consider these best practices until you begin planning for your first few production workloads.