AWS solutions documentation change
Summary
Replaced all instances of 'this solution' with 'this Guidance' and 'the solution' with 'the Guidance' throughout the document to standardize terminology
Security assessment
The changes are purely terminological updates from 'solution' to 'Guidance' without altering security-related content. The existing security practices (like least privilege roles) remain unchanged in substance. No new security vulnerabilities or features were introduced.
Diff
diff --git a/solutions/latest/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/aws-well-architected-design-considerations.md b/solutions/latest/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/aws-well-architected-design-considerations.md index 517cf757e..bfa89b5c4 100644 --- a//solutions/latest/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/aws-well-architected-design-considerations.md +++ b//solutions/latest/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/aws-well-architected-design-considerations.md @@ -9 +9 @@ Operational excellenceSecurityReliabilityPerformance efficiencyCost optimization -This solution uses the best practices from the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/), which helps customers design and operate reliable, secure, efficient, and cost-effective workloads in the cloud. +This Guidance uses the best practices from the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/), which helps customers design and operate reliable, secure, efficient, and cost-effective workloads in the cloud. @@ -11 +11 @@ This solution uses the best practices from the [AWS Well-Architected Framework]( -This section describes how the design principles and best practices of the Well-Architected Framework benefit this solution. +This section describes how the design principles and best practices of the Well-Architected Framework benefit this Guidance. @@ -15 +15 @@ This section describes how the design principles and best practices of the Well- -This section describes how we architected this solution using the principles and best practices of the [operational excellence pillar](https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html). +This section describes how we architected this Guidance using the principles and best practices of the [operational excellence pillar](https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html). @@ -17 +17 @@ This section describes how we architected this solution using the principles and - * This solution pushes metrics to CloudWatch at various stages to provide visibility into archive transfer progress. + * This Guidance pushes metrics to CloudWatch at various stages to provide visibility into archive transfer progress. @@ -24 +24 @@ This section describes how we architected this solution using the principles and -This section describes how we architected this solution using the principles and best practices of the [security pillar](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/welcome.html). +This section describes how we architected this Guidance using the principles and best practices of the [security pillar](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/welcome.html). @@ -28 +28 @@ This section describes how we architected this solution using the principles and - * All roles used by the solution follow least privilege access. They only contain the minimum permissions required to accomplish the transfer. + * All roles used by the Guidance follow least privilege access. They only contain the minimum permissions required to accomplish the transfer. @@ -37 +37 @@ This section describes how we architected this solution using the principles and -This section describes how we architected this solution using the principles and best practices of the [reliability pillar](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/welcome.html). +This section describes how we architected this Guidance using the principles and best practices of the [reliability pillar](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/welcome.html). @@ -39 +39 @@ This section describes how we architected this solution using the principles and - * The solution uses a serverless architecture to achieve high availability and recovery from failure. + * The Guidance uses a serverless architecture to achieve high availability and recovery from failure. @@ -41 +41 @@ This section describes how we architected this solution using the principles and - * The solution protects against state machine definition errors through a suite of automated tests. + * The Guidance protects against state machine definition errors through a suite of automated tests. @@ -50 +50 @@ This section describes how we architected this solution using the principles and -This section describes how we architected this solution using the principles and best practices of the [performance efficiency pillar](https://docs.aws.amazon.com/wellarchitected/latest/performance-efficiency-pillar/welcome.html). +This section describes how we architected this Guidance using the principles and best practices of the [performance efficiency pillar](https://docs.aws.amazon.com/wellarchitected/latest/performance-efficiency-pillar/welcome.html). @@ -52 +52 @@ This section describes how we architected this solution using the principles and - * The solution uses a serverless architecture with the ability to scale horizontally as needed. + * The Guidance uses a serverless architecture with the ability to scale horizontally as needed. @@ -54 +54 @@ This section describes how we architected this solution using the principles and - * The solution is tested and deployed daily to achieve consistency as AWS services change. + * The Guidance is tested and deployed daily to achieve consistency as AWS services change. @@ -61 +61 @@ This section describes how we architected this solution using the principles and -This section describes how we architected this solution using the principles and best practices of the [cost optimization pillar](https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/welcome.html). +This section describes how we architected this Guidance using the principles and best practices of the [cost optimization pillar](https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/welcome.html). @@ -63 +63 @@ This section describes how we architected this solution using the principles and - * The solution uses a serverless architecture that only charges customers for what they use. + * The Guidance uses a serverless architecture that only charges customers for what they use. @@ -72 +72 @@ This section describes how we architected this solution using the principles and -This section describes how we architected this solution using the principles and best practices of the [sustainability pillar](https://docs.aws.amazon.com/wellarchitected/latest/sustainability-pillar/sustainability-pillar.html). +This section describes how we architected this Guidance using the principles and best practices of the [sustainability pillar](https://docs.aws.amazon.com/wellarchitected/latest/sustainability-pillar/sustainability-pillar.html). @@ -74 +74 @@ This section describes how we architected this solution using the principles and - * The solution uses managed serverless services to minimize the environmental impact of the backend services compared to continually operating on-premises services. + * The Guidance uses managed serverless services to minimize the environmental impact of the backend services compared to continually operating on-premises services.