How Elastic Load Balancing works with IAM - Elastic Load Balancing

How Elastic Load Balancing works with IAM

Before you use IAM to manage access to Elastic Load Balancing, learn what IAM features are available to use with Elastic Load Balancing.

IAM features you can use with Elastic Load Balancing
IAM feature Elastic Load Balancing support

Identity-based policies

Yes

Resource-based policies

No

Policy actions

Yes

Policy resources

Yes

Policy condition keys (service-specific)

Yes

ACLs

No

ABAC (tags in policies)

Yes

Temporary credentials

Yes

Principal permissions

Yes

Service roles

No

Service-linked roles

Yes

Identity-based policies for Elastic Load Balancing

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 Creating IAM 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.

Resource-based policies within Elastic Load Balancing

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 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. 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 AWS 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 How IAM roles differ from resource-based policies in the IAM User Guide.

Policy actions for Elastic Load Balancing

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. 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.

To see a list of Elastic Load Balancing actions, see Actions defined by Elastic Load Balancing in the Service Authorization Reference.

Policy actions in Elastic Load Balancing use the following prefix before the action:

elasticloadbalancing

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

"Action": [ "elasticloadbalancing:action1", "elasticloadbalancing: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": "elasticloadbalancing:Describe*"

For the complete list of the API actions for Elastic Load Balancing, see the following documentation:

For more information about the permissions required by each Elastic Load Balancing action, see Elastic Load Balancing API permissions.

Policy resources for Elastic Load Balancing

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

Some Elastic Load Balancing API actions support multiple resources. To specify multiple resources in a single statement, separate the ARNs with commas.

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

To see a list of Elastic Load Balancing resource types and their ARNs, see Resources defined by Elastic Load Balancing in the Service Authorization Reference. To learn with which actions you can specify the ARN of each resource, see Actions defined by Elastic Load Balancing.

Policy condition keys for Elastic Load Balancing

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 (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.

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

elasticloadbalancing:ResourceTag condition key

The elasticloadbalancing:ResourceTag/key condition key is specific to Elastic Load Balancing. The following actions support this condition key:

API version 2015-12-01
  • AddTags

  • CreateListener

  • CreateLoadBalancer

  • DeleteLoadBalancer

  • DeleteTargetGroup

  • DeregisterTargets

  • ModifyLoadBalancerAttributes

  • ModifyTargetGroup

  • ModifyTargetGroupAttributes

  • RegisterTargets

  • RemoveTags

  • SetIpAddressType

  • SetSecurityGroups

  • SetSubnets

API version 2012-06-01
  • AddTags

  • ApplySecurityGroupsToLoadBalancer

  • AttachLoadBalancersToSubnets

  • ConfigureHealthCheck

  • CreateAppCookieStickinessPolicy

  • CreateLBCookieStickinessPolicy

  • CreateLoadBalancer

  • CreateLoadBalancerListeners

  • CreateLoadBalancerPolicy

  • DeleteLoadBalancer

  • DeleteLoadBalancerListeners

  • DeleteLoadBalancerPolicy

  • DeregisterInstancesFromLoadBalancer

  • DetachLoadBalancersFromSubnets

  • DisableAvailabilityZonesForLoadBalancer

  • EnableAvailabilityZonesForLoadBalancer

  • ModifyLoadBalancerAttributes

  • RegisterInstancesWithLoadBalancer

  • RemoveTags

  • SetLoadBalancerListenerSSLCertificate

  • SetLoadBalancerPoliciesForBackendServer

  • SetLoadBalancerPoliciesOfListener

elasticloadbalancing:ListenerProtocol condition key

The elasticloadbalancing:ListenerProtocol condition key can be used for conditions that define the types of listeners that can be created and used. The following actions support this condition key:

API version 2015-12-01
  • CreateListener

  • ModifyListener

API version 2012-06-01
  • CreateLoadBalancer

  • CreateLoadBalancerListeners

The policy is available for Application Load Balancers, Network Load Balancers, and Classic Load Balancers. The following is an example policy that only allows users to select one of the specified protocols for their listener.

Supported protocols:
  • HTTPS

  • HTTP

  • TCP

  • SSL

  • TLS

  • UDP

  • TCP_UDP

"Version": "2015-12-01", "Statement": {"Effect": "Allow", "Action": [ "elasticloadbalancing:CreateListener", "elasticloadbalancing:ModifyListener" ], "Resource": "*", "Condition": { "StringEquals":{ "elasticloadbalancing:ListenerProtocol": [ "HTTPS", "TLS" ] }, }

elasticloadbalancing:SecurityPolicy condition key

The elasticloadbalancing:SecurityPolicy condition key can be used for conditions that define and enforce specific security policies on the load balancers. The following actions support this condition key:

API version 2015-12-01
  • CreateListener

  • ModifyListener

API version 2012-06-01
  • CreateLoadBalancerPolicy

  • SetLoadBalancerPoliciesOfListener

The policy is available for Application Load Balancers, Network Load Balancers and Classic Load Balancers. The following is an example policy that only allows users to select one of the specified security policies for their load balancer.

"Resource": [ "Version": "2015-12-01", "Statement": {"Effect": "Allow", "Action": [ "elasticloadbalancing:CreateListener", "elasticloadbalancing:ModifyListener" ], "Resource": "*", "Condition": { "ForAnyValue:StringEquals":{ "elasticloadbalancing:SecurityPolicy": [ "ELBSecurityPolicy-TLS13-1-2-2021-06", "ELBSecurityPolicy-TLS13-1-2-Res-2021-06", "ELBSEcurityPolicy-TLS13-1-1-2021-06" ] }, } ]

elasticloadbalancing:Scheme condition key

The elasticloadbalancing:Scheme condition key can be used for conditions that define which scheme can be selected during load balancer creation. The following actions support this condition key:

API version 2015-12-01
  • CreateLoadBalancer

API version 2012-06-01
  • CreateLoadBalancer

The policy is available for Application Load Balancers, Network Load Balancers, and Classic Load Balancers. The following is an example policy that only allows users to select one of the specified scheme for their load balancer.

"Version": "2015-12-01", "Statement": {"Effect": "Allow", "Action":"elasticloadbalancing:CreateLoadBalancer", "Resource": "*", "Condition": { "StringEquals":{ "elasticloadbalancing:Scheme": "internal" }, }

elasticloadbalancing:Subnet condition key

Important

Elastic Load Balancing accepts all capitalizations of Subnet IDs. However, make sure to use the appropriate case insensitive condition operators, for example StringEqualsIgnoreCase.

The elasticloadbalancing:Subnet condition key can be used for conditions that define which subnets can be created and attached to load balancers. The following actions support this condition key:

API version 2015-12-01
  • CreateLoadBalancer

  • SetSubnets

API version 2012-06-01
  • CreateLoadBalancer

  • AttachLoadBalancerToSubnets

The policy is available for Application Load Balancers, Network Load Balancers, Gateway Load Balancers and Classic Load Balancers. The following is an example policy that only allows users to select one of the specified subnets for their load balancer.

"Version": "2015-12-01", "Statement": {"Effect": "Allow", "Action": [ "elasticloadbalancing:CreateLoadBalancer", "elasticloadbalancing:SetSubnets" ], "Resource": "*", "Condition": { "ForAnyValue:StringEqualsIgnoreCase":{ "elasticloadbalancing:Subnet": [ "subnet-01234567890abcdef", "subnet-01234567890abcdeg " ] }, }

elasticloadbalancing:SecurityGroup condition key

Important

Elastic Load Balancing accepts all capitalizations of SecurityGroup IDs. However, make sure to use the appropriate case insensitive condition operators, for example StringEqualsIgnoreCase.

The elasticloadbalancing:SecurityGroup condition key can be used for conditions that define which security groups can be applied to the load balancers. The following actions support this condition key:

API version 2015-12-01
  • CreateLoadBalancer

  • SetSecurityGroups

API version 2012-06-01
  • CreateLoadBalancer

  • ApplySecurityGroupsToLoadBalancer

The policy is available for Application Load Balancers, Network Load Balancers and Classic Load Balancers. The following is an example policy that only allows users to select one of the specified security groups for their load balancer.

"Version": "2015-12-01", "Statement": {"Effect": "Allow", "Action": [ "elasticloadbalancing:CreateLoadBalancer", "elasticloadbalancing:SetSecurityGroup" ], "Resource": "*", "Condition": { "ForAnyValue:StringEqualsIgnoreCase":{ "elasticloadbalancing:SecurityGroup": [ "sg-51530134", "sg-51530144", "sg-51530139" ] }, }

ACLs in Elastic Load Balancing

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 Elastic Load Balancing

Supports ABAC (tags in policies)

Yes

Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes. In AWS, these attributes are called tags. You can attach tags to IAM entities (users or roles) and to many AWS 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/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 What is ABAC? 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 Elastic Load Balancing

Supports temporary credentials

Yes

Some AWS services don't work when you sign in using temporary credentials. For additional information, including which AWS services work with temporary credentials, see AWS services that work with IAM in the IAM User Guide.

You are using temporary credentials if you sign in to the AWS Management Console using any method except a user name and password. For example, when you access AWS 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 Switching to a role (console) in the IAM User Guide.

You can manually create temporary credentials using the AWS CLI or AWS API. You can then use those temporary credentials to access AWS. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM.

Cross-service principal permissions for Elastic Load Balancing

Supports forward access sessions (FAS)

Yes

When you use an IAM user or role to perform actions in AWS, 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 AWS service, combined with the requesting AWS service to make requests to downstream services. FAS requests are only made when a service receives a request that requires interactions with other AWS 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 Elastic Load Balancing

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 Creating a role to delegate permissions to an AWS service in the IAM User Guide.

Service-linked roles for Elastic Load Balancing

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 Elastic Load Balancing service-linked roles, see Elastic Load Balancing service-linked role.