Tagging your Amazon Location Service resources

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, see the AWS General Reference.

Each tag is a label consisting of a key and value that you define:

• Tag key – A general label that categorizes the tag values. For example, CostCenter.

• Tag value – An optional description for the tag key category. For example, MobileAssetTrackingResourcesProd.

This topic helps you get started with tagging by reviewing tagging restrictions. It also shows you how to create tags and use tags to track your AWS cost for each active tag by using cost allocation reports.

Tagging restrictions

The following basic restrictions apply to tags:

• Maximum tags per resource – 50

• For each resource, each tag key must be unique, and each tag key can have only one value.

  Note

  If you add a new tag with the same tag key as an existing tag, the new tag overwrites the existing tag.

• Maximum key length – 128 Unicode characters in UTF-8

• Maximum value length – 256 Unicode characters in UTF-8

• The allowed characters across services are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

• Tag keys and values are case-sensitive.

• The aws: prefix is reserved for AWS use. If a tag has a tag key with this prefix, then you can't edit or delete the tag's key or value. Tags with the aws: prefix don't count against your tags per resource limit.

Grant permission to tag resources

You can use IAM policies to control access to your Amazon Location resources and grant permission to tag a resource on creation. In addition to granting permission to create resources, the policy can include Action permissions to allow tagging operations:

• geo:TagResource – Allows a user to assign one or more tags to a specified Amazon Location resource.

• geo:UntagResource – Allows a user to remove one or more tags from a specified Amazon Location resource.

• geo:ListTagsForResource – Allows a user to list all the tags assigned to an Amazon Location resource.

The following is a policy example to allow a user to create a geofence collection and tag resources:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowTaggingForGeofenceCollectionOnCreation",
            "Effect": "Allow",
            "Action": [
                "geo:CreateGeofenceCollection",
                "geo:TagResource"
            ],
            "Resource": "arn:aws:geo:region:accountID:geofence-collection/*"
    ]
}

Add a tag to an Amazon Location Service resource

You can add tags when creating your resources using the Amazon Location console, the AWS CLI, or the Amazon Location APIs:

• Create a map resource

• Create a place index resource

• Create a route calculator resource

• Create a geofence collection

• Create a tracker resource

To tag existing resources, edit or delete tags

1. Open the Amazon Location console at https://console.aws.amazon.com/location/.

2. In the left navigation pane, choose the resource you want to tag. For example, Maps.

3. Choose a resource from the list.

4. Choose Manage tags to add, edit, or delete your tags.

Track resource cost by tag

You can use tags for cost allocation to track your AWS cost in detail. After you activate the cost allocation tags, AWS uses the cost allocation tags to organize your resource billing on your cost allocation report. This helps you categorize and track your usage costs.

There are two types of cost allocation tags you can activate:

• AWS-generated – These tags are generated by AWS. AWS tags use the aws: prefix, for example, aws:createdBy.

• User-defined – These are custom tags that you create. The user-defined tags use the user: prefix, for example, user:CostCenter.

You must activate each tag type individually. After your tags are activated, you can enable AWS Cost Explorer or view your monthly cost allocation report.

AWS-generated tags

To activate AWS-generated tags

1. Open the Billing and Cost Management console at https://console.aws.amazon.com/billing/.

2. In the left navigation pane, choose Cost Allocation Tags.

3. Under the AWS-Generated Cost Allocation Tags tab, select the tag keys that you want to activate.

4. Choose Activate.

User-defined tags

To activate user-defined tags

1. Open the Billing and Cost Management console at https://console.aws.amazon.com/billing/.

2. In the left navigation pane, choose Cost Allocation Tags.

3. Under the User-Defined Cost Allocation Tags tab, select the tag keys you want to activate.

4. Choose Activate.

After you activate your tags, AWS generates a monthly Cost Allocation Report for your resource usage and cost. This cost allocation report includes all of your AWS costs for each billing period, including tagged and untagged resources. For more information, see Using Cost Allocation Tags in the AWS Billing and Cost Management User Guide.

Control access to Amazon Location Service resources using tags

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.

Learn more

For more information about:

• Tagging best practices, see Tagging AWS resources in the AWS General Reference.

• Using tags to control access to AWS resources, see Controlling access to AWS resources using tags in the AWS Identity and Access Management User Guide.