How Amazon Location Service works with IAM - Amazon Location Service

How Amazon Location Service works with IAM

Before you use IAM to manage access to Amazon Location, you should understand what IAM features are available to use with Amazon Location. For a high-level view of how Amazon Location and other AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.

Identity-based policies

With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. Amazon Location supports specific actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see IAM JSON Policy Elements Reference in the IAM User Guide.

Actions

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Policy actions usually have the same name as the associated AWS API operation. There are some exceptions, such as permission-only actions that don't have a matching API operation. There are also some operations that require multiple actions in a policy. These additional actions are called dependent actions.

Include actions in a policy to grant permissions to perform the associated operation.

Policy actions in Amazon Location use the following prefix: geo:.

Example

To grant someone read-only permission for Amazon Location Service trackers with the Amazon Location Tracking API operation, you'll need to include geo:BatchGetDevicePosition, geo:GetDevicePosition and geo:GetDevicePositionHistory in their policy.

Policy statements must include either an Action or NotAction element. Amazon Location defines its own set of actions that describe tasks that you can perform with this service.

To specify multiple actions in a single statement, separate them with commas as follows:

{ "Action": [ "geo:BatchGetDevicePosition", "geo:GetDevicePosition", "geo:GetDevicePositionHistory" ] }

You can specify multiple actions using wildcards (*). For example, to specify all actions that begin with the word Get, include the following action:

"Action": "geo:Get*"
Warning

Avoid using wildcards (*) to specify all actions for a service. Use the best practice of granting least privilege and narrow the permissions used in a policy.

To see a list of Amazon Location actions, see the Amazon Location API references.

Resources

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Resource JSON policy element specifies the object or objects to which the action applies. Statements must include either a Resource or a NotResource element. As a best practice, specify a resource using its Amazon Resource Name (ARN). You can do this for actions that support a specific resource type, known as resource-level permissions.

For actions that don't support resource-level permissions, such as listing operations, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

Amazon Location Service uses the following prefixes for resources:

Amazon Location resource prefix
Resource Resource prefix
Map resources map
Place resources place-index
Tracking resources tracker
Geofence Collection resources geofence-collection

Use the following ARN syntax:

arn:Partition:geo:Region:Account:ResourcePrefix/ResourceName

For more information about the format of ARNs, see Amazon Resource Names (ARNs) and AWS Service Namespaces.

Examples

  • Use the following ARN to allow access to a specified map resource.

    "Resource": "arn:aws:geo:us-west-2:account-id:map/map-resource-name"
  • To specify access to all map resources that belong to a specific account, use the wildcard (*):

    "Resource": "arn:aws:geo:us-west-2:account-id:map/*"
  • Some Amazon Location actions, such as those for creating resources, can't be performed on a specific resource. In those cases, you must use the wildcard (*).

    "Resource": "*"

Many Amazon Location Service API actions involve multiple resources. For example, getting map tiles requires the IAM user to have permissions to retrieve map tiles, sprite files, glyphs, and the style descriptor file.

To specify multiple resources in a single statement, separate the ARNs with commas:

{ "Resource": [ "geo:GetMapTile", "geo:GetMapSprites", "geo:GetMapGlyphs", "geo:GetMapStyleDescriptor" ] }

Condition keys

Amazon Location does not provide any service-specific condition keys, but it does support using some global condition keys. To see all AWS global condition keys, see AWS Global Condition Context Keys in the IAM User Guide.

Amazon Location resource-based policies

Amazon Location does not support resource-based policies.

Amazon Location IAM roles

An IAM role is an entity within your AWS account that has specific permissions.

Using temporary credentials with Amazon Location

You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross-account role. You obtain temporary security credentials by calling AWS STS API operations such as AssumeRole or GetFederationToken.

Amazon Location supports using temporary credentials.