AWS wellarchitected documentation change
Summary
Changed 'Amazon S3 Glacier' to 'Amazon Glacier' in storage cost optimization example
Security assessment
The change corrects a service name reference but does not introduce or modify security-related content. No evidence of addressing vulnerabilities or security controls.
Diff
diff --git a/wellarchitected/latest/management-and-governance-guide/implementation-priorities-6.md b/wellarchitected/latest/management-and-governance-guide/implementation-priorities-6.md index 3a25332b3..18cae5588 100644 --- a//wellarchitected/latest/management-and-governance-guide/implementation-priorities-6.md +++ b//wellarchitected/latest/management-and-governance-guide/implementation-priorities-6.md @@ -27 +27 @@ Create policies and mechanisms that define how resources are managed by your org -Review historic spend patterns to detect cost spikes (one-time or recurring) or continual cost increases, assuming 14–30 days of historical spend. Implement mechanisms to periodically identify and [right-size instances based on current workload metrics](https://docs.aws.amazon.com/whitepapers/latest/cost-optimization-right-sizing/cost-optimization-right-sizing.html) and characteristics. This can be evaluated using AWS Cost Explorer, AWS Trusted Advisor, and AWS Compute Optimizer, along with AWS Partner tools, such as VMware CloudHealth, Apptio Cloudability, and CloudCheckr. Cost efficiencies can also be achieved with Compute Savings Plans, Reserved Instances, Spot Instances for ephemeral workloads, and Amazon CloudFront Security Savings Bundle. Continually reviewing cost metrics can help to identify over purchased or underutilized savings mechanisms. For example, you can optimize your storage costs with S3 Intelligent-Tiering, Amazon S3 Glacier, or implementing lifecycle policies and purge processes. Centralize redundant or shared infrastructure to optimize costs. Manage demand and supply resources dynamically by implementing scheduled or automatic scaling, buffering, or throttling. Review new EC2 instance types as they are released to take advantage of a better price-performance ratio. +Review historic spend patterns to detect cost spikes (one-time or recurring) or continual cost increases, assuming 14–30 days of historical spend. Implement mechanisms to periodically identify and [right-size instances based on current workload metrics](https://docs.aws.amazon.com/whitepapers/latest/cost-optimization-right-sizing/cost-optimization-right-sizing.html) and characteristics. This can be evaluated using AWS Cost Explorer, AWS Trusted Advisor, and AWS Compute Optimizer, along with AWS Partner tools, such as VMware CloudHealth, Apptio Cloudability, and CloudCheckr. Cost efficiencies can also be achieved with Compute Savings Plans, Reserved Instances, Spot Instances for ephemeral workloads, and Amazon CloudFront Security Savings Bundle. Continually reviewing cost metrics can help to identify over purchased or underutilized savings mechanisms. For example, you can optimize your storage costs with S3 Intelligent-Tiering, Amazon Glacier, or implementing lifecycle policies and purge processes. Centralize redundant or shared infrastructure to optimize costs. Manage demand and supply resources dynamically by implementing scheduled or automatic scaling, buffering, or throttling. Review new EC2 instance types as they are released to take advantage of a better price-performance ratio.