AWS location documentation change
Summary
Fixed multiple documentation URLs by correcting path formatting (removing double slashes) and updated security-iam policy examples link to point to a parent section.
Security assessment
These changes are purely documentation link maintenance. While the IAM policy section discusses security controls, the link update doesn't introduce new security content or address vulnerabilities - it simply reorganizes existing documentation references. Tagging strategies and cost allocation reports remain unchanged in their security implications.
Diff
diff --git a/location/latest/developerguide/manage-resources.md b/location/latest/developerguide/manage-resources.md index 5aab931db..c63d0fd4a 100644 --- a//location/latest/developerguide/manage-resources.md +++ b//location/latest/developerguide/manage-resources.md @@ -9 +9 @@ RestrictionsGrant permission to tag resourcesAdd a tag to a resourceHow to use t -Use resource tagging in Amazon Location to create tags to categorize your resources by purpose, owner, environment, or criteria. Tagging your resources helps you manage, identify, organize, search, and filter your resources. For example, with AWS Resource Groups, you can create groups of AWS resources based on one or more tags or portions of tags. You can also create groups based on their occurrence in an AWS CloudFormation stack. Using Resource Groups and Tag Editor, you can consolidate and view data for applications that consist of multiple services, resources, and Regions in one place. For more information on [Common Tagging Strategies](https://docs.aws.amazon.com//general/latest/gr/aws_tagging.html#tag-strategies), see the _AWS General Reference_. +Use resource tagging in Amazon Location to create tags to categorize your resources by purpose, owner, environment, or criteria. Tagging your resources helps you manage, identify, organize, search, and filter your resources. For example, with AWS Resource Groups, you can create groups of AWS resources based on one or more tags or portions of tags. You can also create groups based on their occurrence in an AWS CloudFormation stack. Using Resource Groups and Tag Editor, you can consolidate and view data for applications that consist of multiple services, resources, and Regions in one place. For more information on [Common Tagging Strategies](https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html#tag-strategies), see the _AWS General Reference_. @@ -24 +24 @@ For more information about: - * Tagging best practices, see [Tagging AWS resources](https://docs.aws.amazon.com//general/latest/gr/aws_tagging.html#tag-best-practices) in the _AWS General Reference_. + * Tagging best practices, see [Tagging AWS resources](https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html#tag-best-practices) in the _AWS General Reference_. @@ -137 +137 @@ After you activate your tags, AWS generates a [monthly Cost Allocation Report](h -AWS Identity and Access Management (IAM) policies support tag-based conditions, which enables you to manage authorization for your resources based on specific tags key and values. For example, an IAM role policy can include conditions to limit access to specific environments, such as development, test, or production, based on tags. For more information, see the topic on [control resource access based on tags](https://docs.aws.amazon.com/location/latest/developerguide/security_iam_id-based-policy-examples.html#security_iam_tag-based-policy-example). +AWS Identity and Access Management (IAM) policies support tag-based conditions, which enables you to manage authorization for your resources based on specific tags key and values. For example, an IAM role policy can include conditions to limit access to specific environments, such as development, test, or production, based on tags. For more information, see the topic on [control resource access based on tags](https://docs.aws.amazon.com/location/latest/developerguide/security-iam.html#security_iam_id-based-policy-examples).