AWS devops-guru documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for consistency in terminology
Security assessment
The changes are purely stylistic, removing redundant 'AWS' prefixes from CloudFormation references. No security implications or security-related content modifications are present.
Diff
diff --git a/devops-guru/latest/userguide/working-with-resource-collections.md b/devops-guru/latest/userguide/working-with-resource-collections.md index 0f2563548..624caf072 100644 --- a//devops-guru/latest/userguide/working-with-resource-collections.md +++ b//devops-guru/latest/userguide/working-with-resource-collections.md @@ -7 +7 @@ -Amazon DevOps Guru groups the resources that are in the coverage boundary that specifies which resources it analyzes for operational insights. The resources are grouped by resources in AWS CloudFormation stacks or by resources with tags. You choose the stacks or tags when you set up DevOps Guru. You can also update the stacks or tags later. We recommend that you think of your resource groups as applications. For example, you might have all resources that you use for a monitoring application defined in one stack. Or you might add the same tag to all the resources that you use in a database application. the boundary that defines which resources DevOps Guru analyzes. All the resources in the collection are inside this boundary. Any resources in your account that are not in your resource collection are outside the boundary and are not analyzed. For more information about the supported services and resources, see [Amazon DevOps Guru pricing](https://aws.amazon.com/devops-guru/pricing/). +Amazon DevOps Guru groups the resources that are in the coverage boundary that specifies which resources it analyzes for operational insights. The resources are grouped by resources in CloudFormation stacks or by resources with tags. You choose the stacks or tags when you set up DevOps Guru. You can also update the stacks or tags later. We recommend that you think of your resource groups as applications. For example, you might have all resources that you use for a monitoring application defined in one stack. Or you might add the same tag to all the resources that you use in a database application. the boundary that defines which resources DevOps Guru analyzes. All the resources in the collection are inside this boundary. Any resources in your account that are not in your resource collection are outside the boundary and are not analyzed. For more information about the supported services and resources, see [Amazon DevOps Guru pricing](https://aws.amazon.com/devops-guru/pricing/). @@ -13 +13 @@ You can define your coverage boundary that contains the resources in your applic - * Use AWS CloudFormation stacks to specify the resources in your applications. A stack contains resources that are generated using AWS CloudFormation. In DevOps Guru, you choose stacks in your account. The resources you in each stack you choose are grouped into an application. All resources in the stacks are analyzed by DevOps Guru for insights. + * Use CloudFormation stacks to specify the resources in your applications. A stack contains resources that are generated using CloudFormation. In DevOps Guru, you choose stacks in your account. The resources you in each stack you choose are grouped into an application. All resources in the stacks are analyzed by DevOps Guru for insights. @@ -26 +26 @@ For more information, see [Updating your AWS analysis coverage in DevOps Guru](. - * [Using AWS CloudFormation stacks to identify resources in your DevOps Guru applications](./working-with-cfn-stacks.html) + * [Using CloudFormation stacks to identify resources in your DevOps Guru applications](./working-with-cfn-stacks.html)