AWS tag-editor documentation change
Summary
Removed deprecated console reference and updated tag naming conventions documentation
Security assessment
Changes are organizational updates and documentation consolidation without any security-specific context or vulnerability mitigation mentioned
Diff
diff --git a/tag-editor/latest/userguide/best-practices-and-strats.md b/tag-editor/latest/userguide/best-practices-and-strats.md index 0fc135a7c..49ec225ee 100644 --- a//tag-editor/latest/userguide/best-practices-and-strats.md +++ b//tag-editor/latest/userguide/best-practices-and-strats.md @@ -7,2 +6,0 @@ Best practicesTag naming best practicesCommon tagging strategies -AWS has moved Tag Editor tag management functionality from the AWS Resource Groups console to the AWS Resource Explorer console. With Resource Explorer, you can search and filter resources and then manage resource tags from a single console. To learn more about managing resource tags in Resource Explorer, review [Managing resources](https://docs.aws.amazon.com/resource-explorer/latest/userguide/managing-resources.html#arex_console_quickactions) in the Resource Explorer user guide. - @@ -36,3 +34 @@ As you create a tagging strategy for AWS resources, follow best practices: -These are some best practices and naming conventions that we recommend that you use with your tags. - -Key names for AWS tags are case sensitive so ensure that they are used consistently. For example, the tags keys `CostCenter` and `costcenter` are different. One tag key might be configured as a cost allocation tag for financial analysis and reporting, and the other tag key might not be configured for the same use. +These are several best practices and naming conventions that we recommend that you use with your tags. Refer to [Naming tags](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_tags.html#id_tags_rules) in the _IAM User Guide_ for more information.