How Tag Editor works with IAM

Before you use IAM to manage access to Tag Editor, you should understand what IAM features are available to use with Tag Editor. To get a high-level view of how Tag Editor and other AWS services work with IAM, see AWS services that work with IAM in the IAM User Guide.

Tag Editor identity-based policies

With IAM identity-based policies, you can specify allowed or denied actions and resources in addition to the conditions under which actions are allowed or denied. Tag Editor 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 Tag Editor use the following prefix before the action: tag:. Tag Editor actions are performed entirely in the console, but have the prefix tag in log entries.

For example, to grant someone permission to tag a resource with the tag:TagResources API operation, you include the tag:TagResources action in their policy. Policy statements must include either an Action or NotAction element. Tag Editor defines its own set of actions that describe tasks that you can perform with this service.

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

"Action": [
      "tag:action1",
      "tag:action2",
      "tag:action3"

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

"Action": "tag:Get*"

To see a list of Tag Editor actions, see Actions, resources, and condition keys for Tag Editor in the 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": "*"

Tag Editor does not have any resources of its own. Instead, it manipulates the metadata (tags) that are attached to resources created by other AWS services.

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.

Tag Editor does not define any service-specific condition keys.

Examples

To view examples of Tag Editor identity-based policies, see Tag Editor identity-based policy examples.

Resource-based policies

Tag Editor does not support resource-based policies because it doesn't define any of its own resources.

Authorization based on tags

Authorization based on tags is part of the security strategy called attribute-based access control (ABAC).

To control access to a resource based on its 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. You can apply tags to a resource when you are creating or updating the resource.

To view an example identity-based policy for limiting access to a resource based on the tags on that resource, see Viewing groups based on tags. For more information about attribute-based access control (ABAC), see What is ABAC for AWS? in the IAM User Guide.

Tag Editor IAM roles

An IAM role is an entity within your AWS account that has specific permissions. Tag Editor does not have or use service roles.

Using temporary credentials with Tag Editor

In Tag Editor, 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.

Service-linked roles

Service-linked roles allow AWS services to access resources in other services to complete an action on your behalf.

Tag Editor does not have or use service-linked roles.

Service roles

This feature allows a service to assume a service role on your behalf.

Tag Editor does not have or use service roles.