AWS tag-editor: Fix IAM documentation URL formatting
Summary
Corrected double slashes in IAM User Guide URLs to ensure proper linking.
Security assessment
The change fixes broken URLs by removing extra slashes. This improves documentation usability but does not address security vulnerabilities or add security content.
Evidence
+For instructions on creating an IAM identity-based policy using these example JSON policy documents, see [Creating Policies on the JSON Tab](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the _IAM User Guide_.
Diff
diff --git a/tag-editor/latest/userguide/security_iam_id-based-policy-examples.md b/tag-editor/latest/userguide/security_iam_id-based-policy-examples.md index ba1c4a340..430d2e048 100644 --- a//tag-editor/latest/userguide/security_iam_id-based-policy-examples.md +++ b//tag-editor/latest/userguide/security_iam_id-based-policy-examples.md @@ -13 +13 @@ By default, IAM principals, such as roles and users, don't have permission to cr -For instructions on creating an IAM identity-based policy using these example JSON policy documents, see [Creating Policies on the JSON Tab](https://docs.aws.amazon.com//IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the _IAM User Guide_. +For instructions on creating an IAM identity-based policy using these example JSON policy documents, see [Creating Policies on the JSON Tab](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the _IAM User Guide_. @@ -51 +51 @@ To access the Tag Editor console and the Resource Groups Tagging API, you must h -To ensure that those principals can still use Tag Editor, attach the following policy (or a policy that contains the permissions listed in the following policy) to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com//IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the _IAM User Guide_ : +To ensure that those principals can still use Tag Editor, attach the following policy (or a policy that contains the permissions listed in the following policy) to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the _IAM User Guide_ : @@ -150 +150 @@ JSON -You can attach this policy to the users in your account. If a user with the tag key `project` and tag value `alpha` attempts to view a resource group, the group must also be tagged `project=alpha`. Otherwise the user is denied access. The condition tag key `project` matches both `Project` and `project` because condition key names are not case-sensitive. For more information, see [IAM JSON policy elements: Condition](https://docs.aws.amazon.com//IAM/latest/UserGuide/reference_policies_elements_condition.html) in the _IAM User Guide_. +You can attach this policy to the users in your account. If a user with the tag key `project` and tag value `alpha` attempts to view a resource group, the group must also be tagged `project=alpha`. Otherwise the user is denied access. The condition tag key `project` matches both `Project` and `project` because condition key names are not case-sensitive. For more information, see [IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the _IAM User Guide_.