How Amazon Shield works with IAM
This section explains how to use the features of IAM with Amazon Shield.
Before you use IAM to manage access to Shield, learn what IAM features are available to use with Shield.
IAM feature | Shield support |
---|---|
Yes |
|
No |
|
Yes |
|
Yes |
|
Yes |
|
No |
|
Partial |
|
Yes |
|
Yes |
|
Yes |
|
Yes |
To get a high-level view of how Shield and other Amazon services work with most IAM features, see Amazon services that work with IAM in the IAM User Guide.
Identity-based policies for Shield
This section provides identity-based policy examples for Amazon 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 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. You can't specify the principal in an identity-based policy because it applies to the user or role to which it is attached. 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 Shield identity-based policies, see Identity-based policy examples for Amazon Shield.
Resource-based policies within Shield
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 in a resource-based policy. Principals can include accounts, users, roles, federated users, or Amazon Web Services 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. Adding a cross-account principal to a resource-based policy is only half of establishing the trust relationship. When the principal and the resource are in different Amazon Web Services accounts, an IAM administrator in the trusted account must also grant the principal entity (user or role) permission to access the resource. They grant permission by attaching an identity-based policy to the entity. However, if a resource-based policy grants access to a principal in the same account, no additional identity-based policy is required. For more information, see Cross account resource access in IAM in the IAM User Guide.
Policy actions for Shield
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. Policy
actions usually have the same name as the associated Amazon 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.
To see a list of Shield actions, see Actions defined by Amazon Shield 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 (*). 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 Amazon Shield.
Policy resources for Shield
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. 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": "*"
To see the list of Shield resource types and their ARNs, see
Resources defined by Amazon Shield in the Service Authorization Reference. To learn with
which actions you can specify the ARN of each resource, see Actions defined by Amazon Shield. 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 Amazon 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 Amazon Shield Console | Name in Amazon Shield SDK/CLI | ARN Format |
---|---|---|
Event or attack | AttackDetail |
|
Protection | Protection |
|
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 Amazon Web Services account. You must specify a value. -
resource
: The type of Shield resource, eitherattack
orprotection
. -
ID
: The ID of the Shield resource, or a wildcard (*
) to indicate all resources of the specified type that are associated with the specified Amazon Web Services 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) 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 tous-east-1
. Otherwise, set this to the Region you're using with your protected regional resources. -
scope
: Set the scope toglobal
for use with an Amazon CloudFront distribution orregional
for use with any of the regional resources that Amazon WAF supports. The regional resources are an Amazon API Gateway REST API, an Application Load Balancer, an Amazon AppSync GraphQL API, an Amazon Cognito user pool, an Amazon App Runner service, and an Amazon 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 Amazon Shield.
Policy condition keys for Shield
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 (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, Amazon evaluates them using
a logical AND
operation. If you specify multiple values for a single
condition key, Amazon 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.
Amazon supports global condition keys and service-specific condition keys. To see all Amazon global condition keys, see Amazon global condition context keys in the IAM User Guide.
To see a list of Shield condition keys, see Condition keys for Amazon Shield in the Service Authorization Reference. To learn with which actions and resources you can use a condition key, see Actions defined by Amazon Shield.
To view examples of Shield identity-based policies, see Identity-based policy examples for Amazon Shield.
ACLs in Shield
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
Supports ABAC (tags in policies): Partial
Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes. In Amazon, these attributes are called tags. You can attach tags to IAM entities (users or roles) and to many Amazon resources. Tagging entities and resources is the first step of ABAC. Then you design ABAC policies to allow operations when the principal's tag matches the tag on the resource that they are trying to access.
ABAC is helpful in environments that are growing rapidly and helps with situations where policy management becomes cumbersome.
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/
, or
key-name
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.
Using temporary credentials with Shield
Supports temporary credentials: Yes
Some Amazon Web Services services don't work when you sign in using temporary credentials. For additional information, including which Amazon Web Services services work with temporary credentials, see Amazon Web Services services that work with IAM in the IAM User Guide.
You are using temporary credentials if you sign in to the Amazon Web Services Management Console using any method except a user name and password. For example, when you access Amazon using your company's single sign-on (SSO) link, that process automatically creates temporary credentials. You also automatically create temporary credentials when you sign in to the console as a user and then switch roles. For more information about switching roles, see Switch from a user to an IAM role (console) in the IAM User Guide.
You can manually create temporary credentials using the Amazon CLI or Amazon API. You can then use those temporary credentials to access Amazon. Amazon recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM.
Forward access sessions for Shield
Supports forward access sessions (FAS): Yes
When you use an IAM user or role to perform actions in Amazon, you are considered a principal. When you use some services, you might perform an action that then initiates another action in a different service. FAS uses the permissions of the principal calling an Amazon Web Services service, combined with the requesting Amazon Web Services service to make requests to downstream services. FAS requests are only made when a service receives a request that requires interactions with other Amazon Web Services services or resources to complete. In this case, you must have permissions to perform both actions. For policy details when making FAS requests, see Forward access sessions.
Service roles for Shield
Supports service roles: Yes
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.
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
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.
For details about creating or managing Shield service-linked roles, see Using service-linked roles for Shield Advanced.