Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

How zonal shift works with IAM

Before you use IAM to manage access to zonal shift in Amazon Application Recovery Controller (ARC), learn what IAM features are available to use with zonal shift.

To get a high-level, overall view of how Amazon services work with most IAM features, see Amazon services that work with IAM in the IAM User Guide.

Identity-based policies for ARC

Supports identity-based policies: Yes

Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see Define custom IAM permissions with customer managed policies in the IAM User Guide.

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. To learn about all of the elements that you can use in a JSON policy, see IAM JSON policy elements reference in the IAM User Guide.

To view examples of ARC identity-based policies, see Identity-based policy examples in Amazon Application Recovery Controller (ARC).

Resource-based policies within ARC

Supports resource-based policies: No

Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM role trust policies and Amazon S3 bucket policies. In services that support resource-based policies, service administrators can use them to control access to a specific resource.

Policy actions for zonal shift

Supports policy actions: Yes

Administrators can use Amazon 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. Include actions in a policy to grant permissions to perform the associated operation.

To see a list of ARC actions for zonal shift, see Actions defined by Amazon Route 53 Zonal Shift in the Service Authorization Reference.

Policy actions in ARC for zonal shift use the following prefixes before the action:

arc-zonal-shift

To specify multiple actions in a single statement, separate them with commas. For example, the following:

"Action": [
      "arc-zonal-shift:action1",
      "arc-zonal-shift:action2"
         ]

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

"Action": "arc-zonal-shift:Describe*"

To view examples of ARC identity-based policies for zonal shift, see Identity-based policy examples for zonal shift in ARC.

Policy resources for zonal shift

Supports policy resources: Yes

Administrators can use Amazon 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. As a best practice, specify a resource using its Amazon Resource Name (ARN). For actions that don't support resource-level permissions, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

To see a list of resource types and their ARNs, and the actions that you can specify with the ARN of each resource, see the following topic in the Service Authorization Reference:

To see the actions and resources that you can use with a condition key, see the following topic in the Service Authorization Reference:

To view examples of ARC identity-based policies for zonal shift, see Identity-based policy examples for zonal shift in ARC.

Policy condition keys for zonal shift

Supports service-specific policy condition keys: Yes

Administrators can use Amazon 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 specifies when statements execute based on defined criteria. 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. To see all Amazon global condition keys, see Amazon global condition context keys in the IAM User Guide.

To see a list of zonal shift condition keys, see the following topic in the Service Authorization Reference:

To see the actions and resources that you can use with a condition key, see the following topics in the Service Authorization Reference:

To view examples of ARC identity-based policies for zonal shift, see Identity-based policy examples for zonal shift in ARC.

Access control lists (ACLs) in ARC

Supports ACLs: No

Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.

Attribute-based access control (ABAC) with ARC

Supports ABAC (tags in policies): Partial

Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and Amazon resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.

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.

If a service supports all three condition keys for every resource type, then the value is Yes for the service. If a service supports all three condition keys for only some resource types, then the value is Partial.

For more information about ABAC, see Define permissions with ABAC authorization in the IAM User Guide. To view a tutorial with steps for setting up ABAC, see Use attribute-based access control (ABAC) in the IAM User Guide.

ARC includes the following partial support for ABAC:

Using temporary credentials with ARC

Supports temporary credentials: Yes

Temporary credentials provide short-term access to Amazon resources and are automatically created when you use federation or switch roles. Amazon recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM and Amazon Web Services services that work with IAM in the IAM User Guide.

Cross-service principal permissions for ARC

Supports forward access sessions (FAS): Yes

When you use an IAM entity (user or role) to perform actions in Amazon, you are considered a principal. Policies grant permissions to a principal. When you use some services, you might perform an action that then triggers another action in a different service. In this case, you must have permissions to perform both actions.

To see whether an action requires additional dependent actions in a policy, see the following topic in the Service Authorization Reference:

Service roles for ARC

Supports service roles: No

A service role is an IAM role that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see Create a role to delegate permissions to an Amazon Web Services service in the IAM User Guide.

Service-linked roles for ARC

Supports service-linked roles: Yes

A service-linked role is a type of service role that is linked to an Amazon Web Services service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your Amazon Web Services account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.

Zonal shift does not use service-linked roles.