AWS location: Document required geo:TagResource permission for Amazon Location stacks
Summary
Adds a 'Required permissions' section explaining that the CloudFormation IAM identity (service role, CDK execution role, or user identity) must have geo:TagResource to create or replace taggable Amazon Location resources starting February 26, 2027, including a sample IAM policy statement, the AccessDenied error message, and behavior for existing resources and stack updates. Also reorders the list of supported AWS::Location resource types.
Security assessment
The diff documents an IAM permission requirement (geo:TagResource) for the CloudFormation execution identity and provides a least-privilege-style policy statement scoped to arn:aws:geo:region:account-id:*, plus the AccessDenied failure mode. This is IAM/authorization guidance with security impact but no evidence of a specific vulnerability or incident being remediated.
Evidence
+Starting February 26, 2027, this identity needs permission to use the `geo:TagResource` action to create Amazon Location resources that support tags, and to replace them during a stack update. Of the resource types listed above, only `AWS::Location::TrackerConsumer` doesn't support tags, and it isn't affected.
Diff
diff --git a/location/latest/developerguide/cloudformation.md b/location/latest/developerguide/cloudformation.md index 2e2f7eb..b4fd604 100644 --- a//location/latest/developerguide/cloudformation.md +++ b//location/latest/developerguide/cloudformation.md @@ -7 +7 @@ -Related CloudFormation templatesLearn more about CloudFormation +Related CloudFormation templatesRequired permissionsLearn more about CloudFormation @@ -20,0 +21,10 @@ Amazon Location supports creating the following resource types in CloudFormation + * [AWS::Location::APIKey](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-location-apikey.html) + + * [AWS::Location::GeofenceCollection](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-location-geofencecollection.html) + + * [AWS::Location::Map](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-location-map.html) + + * [AWS::Location::PlaceIndex](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-location-placeindex.html) + + * [AWS::Location::RouteCalculator](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-location-routecalculator.html) + @@ -25,2 +34,0 @@ Amazon Location supports creating the following resource types in CloudFormation - * [AWS::Location::GeofenceCollection](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-location-geofencecollection.html) - @@ -31,0 +40,50 @@ For more information, including examples of JSON and YAML templates for Amazon L +## Required permissions + +CloudFormation uses an IAM identity to create and update your Amazon Location resources. This identity is one of the following: + + * The service role you specify for the stack. + + * The CloudFormation execution role, if you deploy with the AWS CDK. + + * Your own IAM identity, if you don't specify a service role. + + + + +Starting February 26, 2027, this identity needs permission to use the `geo:TagResource` action to create Amazon Location resources that support tags, and to replace them during a stack update. Of the resource types listed above, only `AWS::Location::TrackerConsumer` doesn't support tags, and it isn't affected. + +The permission is required even if your template doesn't specify tags. CloudFormation adds the `aws:cloudformation:stack-name`, `aws:cloudformation:stack-id`, and `aws:cloudformation:logical-id` tags to each resource it creates. For more information about the tags that CloudFormation adds, see the [_CloudFormation Template Reference_](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-resource-tags.html). To learn how to manage the required permissions, see [Grant permission to tag resources](./manage-resources.html#manage-resources_grant-permission). + +### Step 1: Add the permission + +Add the following statement to the policy of the identity that CloudFormation uses: + + + { + "Effect": "Allow", + "Action": "geo:TagResource", + "Resource": "arn:aws:geo:region:account-id:*" + } + +You don't need to add the statement if the identity already allows `geo:TagResource`, for example through `geo:*` or the `AdministratorAccess` managed policy. + +If you deploy with the AWS CDK, the CloudFormation execution role uses the `AdministratorAccess` policy by default, which already allows this action. You need to add the statement only if you use managed policies. For more information, see [Customize AWS CDK bootstrapping](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping-customizing.html) in the _AWS CDK Developer Guide_. + +### Step 2: Check for the error + +If the identity doesn't have permission to use `geo:TagResource`, the resource fails to create and the stack event shows the following message. + + + Resource handler returned message: "Access denied for operation 'AWS::Location::PlaceIndex'." (RequestToken: request-token, HandlerErrorCode: AccessDenied) + +### Existing resources and stack updates + +Existing resources keep working. + + * Stack updates that replace a resource require `geo:TagResource`, including for stacks created before February 26, 2027. For example, changing `IndexName` for `AWS::Location::PlaceIndex` replaces the resource. If the permission is missing, CloudFormation rolls back the update. + + * Stack updates that don't replace a resource, and stack deletes, don't require the new permission. Resources created before February 26, 2027 don't receive the CloudFormation tags from these updates. + + + +