AWS prescriptive-guidance documentation change
Summary
Removed code formatting from 'aws:' prefix reference and adjusted punctuation
Security assessment
Formatting changes to existing tag documentation without altering security guidance about IAM tag-based access control
Diff
diff --git a/prescriptive-guidance/latest/cost-allocation-tagging/define-tagging-dictionary.md b/prescriptive-guidance/latest/cost-allocation-tagging/define-tagging-dictionary.md index 6f0bbc7bc..22986bb17 100644 --- a//prescriptive-guidance/latest/cost-allocation-tagging/define-tagging-dictionary.md +++ b//prescriptive-guidance/latest/cost-allocation-tagging/define-tagging-dictionary.md @@ -19 +19 @@ Use the following tagging strategies to help identify and manage AWS resources. - * **Tags for access control** – AWS Identity and Access Management (IAM) permissions can be based on tags. You can constrain IAM permissions based on specific tags or tag values. For example, IAM role permissions can include conditions to limit Amazon EC2 API calls to specific environments based on their tags. + * **Tags for access control** – AWS Identity and Access Management (IAM) permissions can be based on tags. You can constrain IAM permissions based on specific tags or tag values. For example, IAM role permissions can include conditions to limit Amazon EC2 API calls to specific environments based on their tags @@ -34 +34 @@ The tag template is part of the tagging dictionary. It establishes which tags wi - * Billing tags. `aws:createdBy` (Anything with the `aws:` prefix is automatically generated by AWS when cost allocation tags are activated. This is explained in the [Using cost allocation tags](./apply-tags.html#cost-allocation) section.) + * Billing tags. `aws:createdBy` (Anything with the aws: prefix is automatically generated by AWS when cost allocation tags are activated. This is explained in the [Using cost allocation tags](./apply-tags.html#cost-allocation) section.)