**Introducing a new console experience for AWS WAF** You can now use the updated experience to access AWS WAF functionality anywhere in the console. For more details, see [Working with the console](https://docs.aws.amazon.com/waf/latest/developerguide/working-with-console.html). # How AWS Shield works with IAM This section explains how to use the features of IAM with AWS Shield. Before you use IAM to manage access to Shield, learn what IAM features are available to use with Shield. **IAM features you can use with AWS Shield** | IAM feature | Shield support | | --- | --- | | [Identity-based policies](#shd-security_iam_service-with-iam-id-based-policies) | Yes | | [Resource-based policies](#shd-security_iam_service-with-iam-resource-based-policies) | No | | [Policy actions](#shd-security_iam_service-with-iam-id-based-policies-actions) | Yes | | [Policy resources](#shd-security_iam_service-with-iam-id-based-policies-resources) | Yes | | [Policy condition keys (service-specific)](#shd-security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes | | [ACLs](#shd-security_iam_service-with-iam-acls) | No | | [ABAC (tags in policies)](#shd-security_iam_service-with-iam-tags) | Partial | | [Temporary credentials](#shd-security_iam_service-with-iam-roles-tempcreds) | Yes | | [Forward access sessions (FAS)](#shd-security_iam_service-with-iam-principal-permissions) | Yes | | [Service roles](#shd-security_iam_service-with-iam-roles-service) | Yes | | [Service-linked roles](#shd-security_iam_service-with-iam-roles-service-linked) | Yes | To get a high-level view of how Shield and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Identity-based policies for Shield Identity-based policies This section provides identity-based policy examples for AWS Shield. **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*. To view examples of Shield identity-based policies, see [Identity-based policy examples for AWS Shield](shd-security_iam_id-based-policy-examples.md). ## Resource-based policies within Shield Resource-based policies **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. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Policy actions for Shield Policy actions **Supports policy actions:** Yes 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. Include actions in a policy to grant permissions to perform the associated operation. To see a list of Shield actions, see [Actions defined by AWS Shield](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsshield.html#awsshield-actions-as-permissions) in the *Service Authorization Reference*. Policy actions in Shield use the following prefix before the action: ``` shield ``` To specify multiple actions in a single statement, separate them with commas. ``` "Action": [ "shield:action1", "shield:action2" ] ``` You can specify multiple actions using wildcards (\$1). For example, to specify all actions in Shield that begin with `List`, include the following action: ``` "Action": "shield:List*" ``` To view examples of Shield identity-based policies, see [Identity-based policy examples for AWS Shield](shd-security_iam_id-based-policy-examples.md). ## Policy resources for Shield Policy resources **Supports policy resources:** Yes 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. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources. ``` "Resource": "*" ``` To see the list of Shield resource types and their ARNs, see [Resources defined by AWS Shield](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsshield.html#awsshield-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions you can specify the ARN of each resource, see [Actions defined by AWS Shield](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsshield.html#awsshield-actions-as-permissions). To allow or deny access to a subset of Shield resources, include the ARN of the resource in the `resource` element of your policy. In AWS Shield, the resources are *protections* and *attacks*. These resources have unique Amazon Resource Names (ARNs) associated with them, as shown in the following table. **** | Name in AWS Shield Console | Name in AWS Shield SDK/CLI | ARN Format | | --- | --- | --- | | Event or attack | AttackDetail | `arn:aws:shield::account:attack/ID` | | Protection | Protection | `arn:aws:shield::account:protection/ID` | To allow or deny access to a subset of Shield resources, include the ARN of the resource in the `resource` element of your policy. The ARNs for Shield have the following format: ``` arn:partition:shield::account:resource/ID ``` Replace the *account*, *resource*, and *ID* variables with valid values. Valid values can be the following: + *account*: The ID of your AWS account. You must specify a value. + *resource*: The type of Shield resource, either `attack` or `protection`. + *ID*: The ID of the Shield resource, or a wildcard (`*`) to indicate all resources of the specified type that are associated with the specified AWS account. For example, the following ARN specifies all protections for the account `111122223333`: ``` arn:aws:shield::111122223333:protection/* ``` The ARNs of Shield resources have the following format: ``` arn:partition:shield:region:account-id:scope/resource-type/resource-name/resource-id ``` For general information about ARN specifications, see [Amazon Resource Names (ARNs)](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html) in the Amazon Web Services General Reference. The following lists requirements that are specific to the ARNs of `wafv2` resources: + *region*: For Shield resources that you use to protect Amazon CloudFront distributions, set this to `us-east-1`. Otherwise, set this to the Region you're using with your protected regional resources. + *scope*: Set the scope to `global` for use with an Amazon CloudFront distribution or `regional` for use with any of the regional resources that AWS WAF supports. The regional resources are an Amazon API Gateway REST API, an Application Load Balancer, an AWS AppSync GraphQL API, an Amazon Cognito user pool, an AWS App Runner service, and an AWS Verified Access instance. + *resource-type*: Specify one of the following values: `attack` for events or attacks, `protection` for protections. + *resource-name*: Specify the name that you gave the Shield resource, or specify a wildcard (`*`) to indicate all resources that satisfy the other specifications in the ARN. You must either specify the resource name and resource ID or specify a wildcard for both. + *resource-id*: Specify the ID of the Shield resource, or specify a wildcard (`*`) to indicate all resources that satisfy the other specifications in the ARN. You must either specify the resource name and resource ID or specify a wildcard for both. For example, the following ARN specifies all web ACLs with regional scope for the account `111122223333` in Region `us-west-1`: ``` arn:aws:wafv2:us-west-1:111122223333:regional/webacl/*/* ``` The following ARN specifies the rule group named `MyIPManagementRuleGroup` with global scope for the account `111122223333` in Region `us-east-1`: ``` arn:aws:wafv2:us-east-1:111122223333:global/rulegroup/MyIPManagementRuleGroup/1111aaaa-bbbb-cccc-dddd-example-id ``` To view examples of Shield identity-based policies, see [Identity-based policy examples for AWS Shield](shd-security_iam_id-based-policy-examples.md). ## Policy condition keys for Shield Policy condition keys **Supports service-specific policy condition keys:** Yes 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 specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. To see a list of Shield condition keys, see [Condition keys for AWS Shield](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsshield.html#awsshield-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions defined by AWS Shield](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsshield.html#awsshield-actions-as-permissions). To view examples of Shield identity-based policies, see [Identity-based policy examples for AWS Shield](shd-security_iam_id-based-policy-examples.md). ## ACLs in Shield ACLs **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. ## ABAC with Shield ABAC **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 AWS 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*. ## Using temporary credentials with Shield Temporary credentials **Supports temporary credentials:** Yes Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Forward access sessions for Shield Forward access sessions **Supports forward access sessions (FAS):** Yes Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). ## Service roles for Shield Service roles **Supports service roles:** Yes A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) 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 AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*. **Warning** Changing the permissions for a service role might break Shield functionality. Edit service roles only when Shield provides guidance to do so. ## Service-linked roles for Shield Service-linked roles **Supports service-linked roles:** Yes A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles. For details about creating or managing Shield service-linked roles, see [Using service-linked roles for Shield Advanced](shd-using-service-linked-roles.md).