AWS prescriptive-guidance documentation change
Summary
Reformatted notes, introduced CLI command typos ('aws ecs' to 'w secs'), and removed horizontal rules
Security assessment
Note reformatting doesn't alter security meaning. CLI typos break functionality but don't create vulnerabilities. No evidence of security fixes or feature additions.
Diff
diff --git a/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/optimizer-ecs-fargate.md b/prescriptive-guidance/latest/optimize-costs-microsoft-workloads/optimizer-ecs-fargate.md index 2c636c056..6a5ba81fa 100644 --- a//prescriptive-guidance/latest/optimize-costs-microsoft-workloads/optimizer-ecs-fargate.md +++ b//prescriptive-guidance/latest/optimize-costs-microsoft-workloads/optimizer-ecs-fargate.md @@ -55,3 +55,2 @@ For most organizations, the most efficient way to use Compute Optimizer is at th -###### Note - -It's a best practice to configure a [delegated administrator account](https://docs.aws.amazon.com/compute-optimizer/latest/ug/delegate-administrator-account.html) for Compute Optimizer. This enables you to exercise the principle of least privilege, minimizing access to the AWS Organizations management account while still providing access to the organization-wide service. +Note: It's a best practice to configure a [delegated administrator account](https://docs.aws.amazon.com/compute-optimizer/latest/ug/delegate-administrator-account.html) for Compute Optimizer. This enables you to exercise the principle of least privilege, minimizing access to the AWS Organizations management account while still providing access to the organization-wide service. +--- @@ -63,3 +62,2 @@ If you're targeting an account with high costs but don't have access to AWS Orga -###### Note - -The recommendations are refreshed daily and they can take up to 12 hours to generate. Keep in mind that Compute Optimizer requires 24 hours of metrics in the past 14 days to generate recommendations for Amazon ECS on Fargate. For more information, see [Requirements for Amazon ECS services on Fargate](https://docs.aws.amazon.com/compute-optimizer/latest/ug/requirements.html#requirements-ecs-fargate) in the Compute Optimizer documentation. +Note: The recommendations are refreshed daily and they can take up to 12 hours to generate. Keep in mind that Compute Optimizer requires 24 hours of metrics in the past 14 days to generate recommendations for Amazon ECS on Fargate. For more information, see [Requirements for Amazon ECS services on Fargate](https://docs.aws.amazon.com/compute-optimizer/latest/ug/requirements.html#requirements-ecs-fargate) in the Compute Optimizer documentation. +--- @@ -90,3 +88,2 @@ If you navigate to Compute Optimizer from within an organization's management ac -###### Note - -To save recommendations for future review, you must have an S3 bucket available for Compute Optimizer to write to in each Region. For more information, see [Amazon S3 bucket policy for AWS Compute Optimizer](https://docs.aws.amazon.com/compute-optimizer/latest/ug/create-s3-bucket-policy-for-compute-optimizer.html) in the Compute Optimizer documentation. +Note: To save recommendations for future review, you must have an S3 bucket available for Compute Optimizer to write to in each Region. For more information, see [Amazon S3 bucket policy for AWS Compute Optimizer](https://docs.aws.amazon.com/compute-optimizer/latest/ug/create-s3-bucket-policy-for-compute-optimizer.html) in the Compute Optimizer documentation. +--- @@ -135 +132 @@ Tagging your workloads is a powerful tool for organizing your resources in AWS. - ClustersArns=$( aws ecs list-clusters –query 'clusterArns' –output text) + ClustersArns=$( w secs list-clusters –query 'clusterArns' –output text) @@ -137 +134 @@ Tagging your workloads is a powerful tool for organizing your resources in AWS. - ServiceArns=$( aws ecs list-services –cluster $ClustersArn –query 'serviceArns' –output text) + ServiceArns=$( w secs list-services –cluster $ClustersArn –query 'serviceArns' –output text) @@ -139 +136 @@ Tagging your workloads is a powerful tool for organizing your resources in AWS. - TasksArns=$( aws ecs list-tasks –cluster $ClustersArn –service-name $ServiceArn –query 'taskArns' –output text) + TasksArns=$( w secs list-tasks –cluster $ClustersArn –service-name $ServiceArn –query 'taskArns' –output text) @@ -141 +138 @@ Tagging your workloads is a powerful tool for organizing your resources in AWS. - aws ecs tag-resource –resource-arn $TasksArn –tags key=$TAG_KEY,value=$TAG_VALUE + w secs tag-resource –resource-arn $TasksArn –tags key=$TAG_KEY,value=$TAG_VALUE