How AWS Device Farm works with IAM

Before you use IAM to manage access to Device Farm, you should understand which IAM features are available to use with Device Farm. To get a high-level view of how Device Farm and other AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.

Device Farm identity-based policies

With IAM identity-based policies, you can specify allowed or denied actions and resources and the conditions under which actions are allowed or denied. Device Farm 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 Device Farm use the following prefix before the action: devicefarm:. For example, to grant someone permission to start Selenium sessions with the Device Farm desktop browser testing CreateTestGridUrl API operation, you include the devicefarm:CreateTestGridUrl action in the policy. Policy statements must include either an Action or NotAction element. Device Farm 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": [
      "devicefarm:action1",
      "devicefarm:action2"

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

"Action": "devicefarm:List*"

To see a list of Device Farm actions, see Actions defined by AWS Device Farm in the IAM Service Authorization Reference.

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": "*"

The Amazon EC2 instance resource has the following ARN:

arn:${Partition}:ec2:${Region}:${Account}:instance/${InstanceId}

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

For example, to specify the i-1234567890abcdef0 instance in your statement, use the following ARN:

"Resource": "arn:aws:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0"

To specify all instances that belong to an account, use the wildcard (*):

"Resource": "arn:aws:ec2:us-east-1:123456789012:instance/*"

Some Device Farm actions, such as those for creating resources, cannot be performed on a resource. In those cases, you must use the wildcard (*).

"Resource": "*"

Many Amazon EC2 API actions involve multiple resources. For example, AttachVolume attaches an Amazon EBS volume to an instance, so an IAM user must have permissions to use the volume and the instance. To specify multiple resources in a single statement, separate the ARNs with commas.

"Resource": [
      "resource1",
      "resource2"

To see a list of Device Farm resource types and their ARNs, see Resource types defined by AWS Device Farm in the IAM Service Authorization Reference. To learn with which actions you can specify the ARN of each resource, see Actions defined by AWS Device Farm in the IAM Service Authorization Reference.

Condition keys

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 Condition element (or Condition block) lets you specify conditions in which a statement is in effect. The Condition element is optional. You can create conditional expressions that use condition operators, such as equals or less than, to match the condition in the policy with values in the request.

If you specify multiple Condition elements in a statement, or multiple keys in a single Condition element, AWS evaluates them using a logical AND operation. If you specify multiple values for a single condition key, AWS evaluates the condition using a logical OR operation. All of the conditions must be met before the statement's permissions are granted.

You can also use placeholder variables when you specify conditions. For example, you can grant an IAM user permission to access a resource only if it is tagged with their IAM user name. For more information, see IAM policy elements: variables and tags in the IAM User Guide.

AWS supports global condition keys and service-specific condition keys. To see all AWS global condition keys, see AWS global condition context keys in the IAM User Guide.

Device Farm defines its own set of condition keys and also supports the use of some global condition keys. To see all AWS global condition keys, see AWS Global Condition Context Keys in the IAM User Guide.

To see a list of Device Farm condition keys, see Condition keys for AWS Device Farm in the IAM Service Authorization Reference. To learn with which actions and resources you can use a condition key, see Actions defined by AWS Device Farm in the IAM Service Authorization Reference.

Examples

To view examples of Device Farm identity-based policies, see AWS Device Farm identity-based policy examples.

Device Farm resource-based policies

Device Farm does not support resource-based policies.

Access control lists

Device Farm does not support access control lists (ACLs).

Authorization based on Device Farm tags

You can attach tags to Device Farm resources or pass tags in a request to Device Farm. To control access based on tags, you provide tag information in the condition element of a policy using the aws:ResourceTag/key-name, aws:RequestTag/key-name, or aws:TagKeys condition keys. For more information about tagging Device Farm resources, see Tagging AWS Device Farm resources.

To view an example identity-based policy for limiting access to a resource based on the tags on that resource, see Viewing Device Farm desktop browser testing projects based on tags.

Device Farm IAM roles

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

Using temporary credentials with Device Farm

Device Farm supports the use of temporary credentials.

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

Service-linked roles

Service-linked roles allow AWS services to access resources in other services to complete an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view, but cannot edit, the permissions for service-linked roles.

Device Farm uses service-linked roles in the Device Farm desktop browser testing feature. For information on these roles, see Using Service-Linked Roles in Device Farm desktop browser testing in the developer guide.

Service roles

Device Farm does not support service roles.

This feature allows a service to assume a service role on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service.