AWS resource-explorer documentation change
Summary
Removed paragraph about immediate access activation and updated references from 'AWS CloudFormation' to 'CloudFormation' in multiple sections. Added warnings about potential downtime when managing tags/applications involving CloudFormation stacks.
Security assessment
The changes primarily involve branding adjustments (removing 'AWS' from CloudFormation references) and reinforcing existing warnings about operational risks when interacting with CloudFormation stacks. While the warnings mention potential downtime, there is no evidence of a specific security vulnerability being addressed.
Diff
diff --git a/resource-explorer/latest/userguide/managing-resources.md b/resource-explorer/latest/userguide/managing-resources.md index c0f9ec409..3756dd0bf 100644 --- a//resource-explorer/latest/userguide/managing-resources.md +++ b//resource-explorer/latest/userguide/managing-resources.md @@ -7,2 +6,0 @@ Resource Explorer console integrations with other AWS servicesConsole resource A -AWS Resource Explorer now provides immediate access to resource search and discovery capabilities in a Region. With this launch, you no longer need to activate Resource Explorer to discover your resources. [Learn more](https://docs.aws.amazon.com/resource-explorer/latest/userguide/manage-immediate-resource-discovery-experience.html) - @@ -64 +62 @@ The resources in your selection do not need to all reside in the AWS Region you -AWS recommends not including AWS CloudFormation stacks in your resource selection when managing tags in the Resource Explorer console. Instead, you should manage tags on AWS CloudFormation stacks only using AWS CloudFormation. Tagging AWS CloudFormation stacks from Resource Explorer can cause unexpected tagging behavior, resulting in downtime or other issues. +AWS recommends not including CloudFormation stacks in your resource selection when managing tags in the Resource Explorer console. Instead, you should manage tags on AWS CloudFormation stacks only using CloudFormation. Tagging CloudFormation stacks from Resource Explorer can cause unexpected tagging behavior, resulting in downtime or other issues. @@ -119 +117 @@ You can select up to 400 resources and create a new application that includes th -AWS recommends not including AWS CloudFormation stacks in your resource selection when creating an application in the Resource Explorer console. Creating an application that includes a AWS CloudFormation stack requires a stack update because all resources added to your application are tagged with the `awsApplication` tag. Manual configurations performed after the stack was last updated may not be reflected after this update. This can cause downtime or other application issues. For more information, see [Update behaviors of stack resources](https://docs.aws.amazon.com/servicecatalog/latest/arguide/overview-appreg.html#tag-sync-role) in the _AWS CloudFormation User Guide_. +AWS recommends not including CloudFormation stacks in your resource selection when creating an application in the Resource Explorer console. Creating an application that includes a AWS CloudFormation stack requires a stack update because all resources added to your application are tagged with the `awsApplication` tag. Manual configurations performed after the stack was last updated may not be reflected after this update. This can cause downtime or other application issues. For more information, see [Update behaviors of stack resources](https://docs.aws.amazon.com/servicecatalog/latest/arguide/overview-appreg.html#tag-sync-role) in the _CloudFormation User Guide_. @@ -182 +180 @@ You can select up to 400 resources and add those resources to an existing applic -AWS recommends not including AWS CloudFormation stacks in your resource selection when adding resources to an application in the Resource Explorer console. Adding a AWS CloudFormation stack to the application requires a stack update because all resources added to your application are tagged with the `awsApplication` tag. Manual configurations performed after the stack was last updated may not be reflected after this update. This can cause downtime or other application issues. For more information, see [Update behaviors of stack resources](https://docs.aws.amazon.com/servicecatalog/latest/arguide/overview-appreg.html#tag-sync-role) in the _AWS CloudFormation User Guide_. +AWS recommends not including CloudFormation stacks in your resource selection when adding resources to an application in the Resource Explorer console. Adding a CloudFormation stack to the application requires a stack update because all resources added to your application are tagged with the `awsApplication` tag. Manual configurations performed after the stack was last updated may not be reflected after this update. This can cause downtime or other application issues. For more information, see [Update behaviors of stack resources](https://docs.aws.amazon.com/servicecatalog/latest/arguide/overview-appreg.html#tag-sync-role) in the _CloudFormation User Guide_.