Update S6273: Re-organize and simplify description (#3943)

* Update S6273: Re-organize and simplify description

* Remove redundant sentance from summary

* switch sentance place

* Address review comment

* Put regex in code block

rules/S6273/cloudformation/rule.adoc

@@ -10,7 +10,7 @@ include::../description.adoc[]
 
 ==== Noncompliant code example
 
-With default provided regular expression ^([A-Z][A-Za-z]*:)*([A-Z][A-Za-z]*)$:
+With default provided regular expression `^([A-Z][A-Za-z]\*:)*([A-Z][A-Za-z]*)$`:
 
 [source,yaml,diff-id=1,diff-type=noncompliant]
 ----

rules/S6273/description.adoc

@@ -1,33 +1,3 @@
-A well-structured tagging strategy is essential when working with AWS resources.
+Proper tagging enhances resource discovery, lifecycle management, and overall productivity within the AWS environment.
-Inadequate tagging practices can lead to several potential issues and make it challenging to manage your AWS environment effectively:
 
-When resources lack proper tags or have inconsistent tagging, it becomes difficult to identify their purpose, owner, or role within the infrastructure.
+This rule ensures that AWS tag keys adhere to a specified naming convention, facilitating effective resource management, cost tracking, security compliance, and automation.
-This ambiguity can lead to confusion and errors during resource management and allocation.
-Without clear and consistent tags, teams may struggle to understand the resource's function, hindering collaboration and efficiency.
-
-Effective tagging is crucial for monitoring and managing costs in AWS.
-Resources without appropriate tags may not be adequately categorized, making tracking their usage and associated expenses hard.
-As a result, it becomes challenging to allocate costs to specific projects, departments, or teams accurately.
-Poor cost visibility can lead to overspending, budgeting issues, and difficulty in optimizing resource allocation.
-
-Tags play a significant role in resource security and compliance.
-Inadequate tagging can result in incorrectly classified resources, leading to potential security vulnerabilities and compliance risks.
-It becomes challenging to apply consistent security policies, control access, and track changes without proper tagging.
-This can leave the AWS environment more susceptible to unauthorized access and compliance violations.
-
-Automation and governance rely on well-defined tags to enforce policies and ensure consistent resource management.
-Inadequate tagging practices can hinder automation efforts, making it challenging to automate resource provisioning, scaling, and deprovisioning.
-Additionally, insufficient tags can lead to governance challenges, making it harder to enforce standardized policies and configurations across resources.
-
-Tags enable efficient resource search and filtering in the AWS Management Console and API.
-When tags are missing, inconsistent, or irrelevant, locating specific resources becomes cumbersome.
-Teams may need to resort to manual searches or resort to resource-naming conventions, defeating the purpose of tags.
-The lack of well-organized tags can increase the time and effort required for resource discovery and impact productivity.
-
-Inadequate tagging practices can also impede resource lifecycle management.
-It becomes harder to track when resources were created, their purpose, and whether they are still in use.
-Without this vital information, it becomes challenging to identify and delete unused or deprecated resources, leading to resource sprawl and increased costs.
-
-In summary, an inadequate tagging strategy in AWS resources can lead to difficulties in resource identification, cost management, security, automation, and resource lifecycle management.
-It is crucial to establish a well-organized tagging approach to mitigate these potential issues and efficiently manage your AWS environment.
-In the following section, we will explore how to fix this code smell by adopting best practices for tagging AWS resources.

rules/S6273/see.adoc

@@ -1,3 +1,38 @@
 == Resources
+
+A well-structured tagging strategy is essential when working with AWS resources.
+Inadequate tagging practices can lead to several potential issues and make it challenging to manage your AWS environment effectively:
+
+When resources lack proper tags or have inconsistent tagging, it becomes difficult to identify their purpose, owner, or role within the infrastructure.
+This ambiguity can lead to confusion and errors during resource management and allocation.
+Without clear and consistent tags, teams may struggle to understand the resource's function, hindering collaboration and efficiency.
+
+Effective tagging is crucial for monitoring and managing costs in AWS.
+Resources without appropriate tags may not be adequately categorized, making tracking their usage and associated expenses hard.
+As a result, it becomes challenging to allocate costs to specific projects, departments, or teams accurately.
+Poor cost visibility can lead to overspending, budgeting issues, and difficulty in optimizing resource allocation.
+
+Tags play a significant role in resource security and compliance.
+Inadequate tagging can result in incorrectly classified resources, leading to potential security vulnerabilities and compliance risks.
+It becomes challenging to apply consistent security policies, control access, and track changes without proper tagging.
+This can leave the AWS environment more susceptible to unauthorized access and compliance violations.
+
+Automation and governance rely on well-defined tags to enforce policies and ensure consistent resource management.
+Inadequate tagging practices can hinder automation efforts, making it challenging to automate resource provisioning, scaling, and deprovisioning.
+Additionally, insufficient tags can lead to governance challenges, making it harder to enforce standardized policies and configurations across resources.
+
+Tags enable efficient resource search and filtering in the AWS Management Console and API.
+When tags are missing, inconsistent, or irrelevant, locating specific resources becomes cumbersome.
+Teams may need to resort to manual searches or resort to resource-naming conventions, defeating the purpose of tags.
+The lack of well-organized tags can increase the time and effort required for resource discovery and impact productivity.
+
+Inadequate tagging practices can also impede resource lifecycle management.
+It becomes harder to track when resources were created, their purpose, and whether they are still in use.
+Without this vital information, it becomes challenging to identify and delete unused or deprecated resources, leading to resource sprawl and increased costs.
+
+In summary, an inadequate tagging strategy in AWS resources can lead to difficulties in resource identification, cost management, security, automation, and resource lifecycle management.
+It is crucial to establish a well-organized tagging approach to mitigate these potential issues and efficiently manage your AWS environment.
+In the following section, we will explore how to fix this code smell by adopting best practices for tagging AWS resources.
+
 === Documentation
 https://docs.aws.amazon.com/whitepapers/latest/tagging-best-practices/adopt-a-standardized-approach-for-tag-names.html[AWS Documentation] Adopt a Standardized Approach for Tag Names

rules/S6273/summary.adoc

@@ -1,2 +1 @@
 Amazon Web Services (AWS) resources tags are metadata labels with keys and optional values used to categorize and manage resources.
-An ineffective tagging strategy can lead to difficulties in resource identification, cost management, and overall AWS environment management.