AWS solutions documentation change
Summary
Updated terminology from 'solution' to 'guidance' throughout the document, including references to IAM roles following least privilege principle. Changed implementation URL and section references.
Security assessment
The changes are terminological updates (solution → guidance) without altering security content. The IAM least privilege reference remains unchanged as a security best practice, but no new security information was added or vulnerabilities addressed.
Diff
diff --git a/solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-well-architected-design-considerations.md b/solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-well-architected-design-considerations.md index 0a7c07316..9aac1489b 100644 --- a//solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-well-architected-design-considerations.md +++ b//solutions/latest/scalable-analytics-using-apache-druid-on-aws/aws-well-architected-design-considerations.md @@ -3 +3 @@ -[Documentation](/index.html)[Scalable Analytics Using Apache Druid on AWS](https://aws.amazon.com/solutions/implementations/scalable-analytics-using-apache-druid-on-aws)[Implementation Guide](solution-overview.html) +[Documentation](/index.html)[Guidance for Scalable Analytics Using Apache Druid on AWS](https://aws.amazon.com/solutions/guidance/scalable-analytics-using-apache-druid-on-aws)[Implementation Guide](solution-overview.html) @@ -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). @@ -32 +32 @@ 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). @@ -38 +38 @@ This section describes how we architected this solution using the principles and - * All IAM roles used by the solution follow the least privilege access principle. They only contain the minimum permissions required so that the service can function properly. + * All IAM roles used by the guidance follow the least privilege access principle. They only contain the minimum permissions required so that the service can function properly. @@ -55 +55 @@ 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). @@ -61 +61 @@ This section describes how we architected this solution using the principles and - * The solution stores data in Amazon S3 so it persists in multiple Availability Zones by default. + * The guidance stores data in Amazon S3 so it persists in multiple Availability Zones by default. @@ -70 +70 @@ 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). @@ -72 +72 @@ This section describes how we architected this solution using the principles and - * The solution supports AWS Fargate for serverless compute and Aurora PostgreSQL Serverless. + * The guidance supports AWS Fargate for serverless compute and Aurora PostgreSQL Serverless. @@ -74 +74 @@ This section describes how we architected this solution using the principles and - * You can deploy the solution in any AWS Region that supports the required AWS services. + * You can deploy the guidance in any AWS Region that supports the required AWS services. @@ -76 +76 @@ This section describes how we architected this solution using the principles and - * The solution provides versatile Automatic scaling policies, including CPU utilization, request per second, and scheduled scaling. + * The guidance provides versatile Automatic scaling policies, including CPU utilization, request per second, and scheduled scaling. @@ -80 +80 @@ This section describes how we architected this solution using the principles and - * The solution maximizes the utilization of AWS Managed Services. For more details, refer to the [AWS services used in this solution](./aws-services-in-this-solution.html) section. + * The guidance maximizes the utilization of AWS Managed Services. For more details, refer to the [AWS services used in this guidance](./aws-services-in-this-solution.html) section. @@ -87 +87 @@ 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). @@ -89 +89 @@ This section describes how we architected this solution using the principles and - * The solution offers support for various EC2 instance types, including Graviton-based EC2 instances. + * The guidance offers support for various EC2 instance types, including Graviton-based EC2 instances. @@ -98 +98 @@ 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).