How Amazon EC2 Auto Scaling works with IAM - Amazon EC2 Auto Scaling
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.

How Amazon EC2 Auto Scaling works with IAM

Before you use IAM to manage access to Amazon EC2 Auto Scaling, learn what IAM features are available to use with Amazon EC2 Auto Scaling.

IAM features you can use with Amazon EC2 Auto Scaling
IAM feature Amazon EC2 Auto Scaling 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)

Partial

Temporary credentials

Yes

Service roles

Yes

Service-linked roles

Yes

To get a high-level view of how Amazon EC2 Auto Scaling and other Amazon Web Services work with most IAM features, see Amazon Web Services that work with IAM in the IAM User Guide.

Identity-based policies for Amazon EC2 Auto Scaling

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.

Identity-based policy examples for Amazon EC2 Auto Scaling

To view examples of Amazon EC2 Auto Scaling identity-based policies, see Amazon EC2 Auto Scaling identity-based policy examples.

Resource-based policies within Amazon EC2 Auto Scaling

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.

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

Policy actions for Amazon EC2 Auto Scaling

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 Amazon EC2 Auto Scaling actions, see Actions defined by Amazon EC2 Auto Scaling in the Service Authorization Reference.

Policy actions in Amazon EC2 Auto Scaling use the following prefix before the action:

autoscaling

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

"Action": [ "autoscaling:action1", "autoscaling:action2" ]

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

"Action": "autoscaling:Describe*"

To view examples of Amazon EC2 Auto Scaling identity-based policies, see Amazon EC2 Auto Scaling identity-based policy examples.

Policy resources for Amazon EC2 Auto Scaling

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

You can use ARNs to identify the Auto Scaling groups and launch configurations that the IAM policy applies to.

An Auto Scaling group has the following ARN.

"Resource": "arn:aws-cn:autoscaling:region:account-id:autoScalingGroup:uuid:autoScalingGroupName/asg-name"

A launch configuration has the following ARN.

"Resource": "arn:aws-cn:autoscaling:region:account-id:launchConfiguration:uuid:launchConfigurationName/lc-name"

To specify an Auto Scaling group with the CreateAutoScalingGroup action, you must replace the UUID with a wildcard (*) as shown in the following example.

"Resource": "arn:aws-cn:autoscaling:region:account-id:autoScalingGroup:*:autoScalingGroupName/asg-name"

To specify a launch configuration with the CreateLaunchConfiguration action, you must replace the UUID with a wildcard (*) as shown in the following example.

"Resource": "arn:aws-cn:autoscaling:region:account-id:launchConfiguration:*:launchConfigurationName/lc-name"

For more information about Amazon EC2 Auto Scaling resource types and their ARNs, see Resources defined by Amazon EC2 Auto Scaling in the Service Authorization Reference. To learn with which actions you can specify the ARN of each resource, see Actions defined by Amazon EC2 Auto Scaling.

Not all Amazon EC2 Auto Scaling actions support resource-level permissions. For actions that don't support resource-level permissions, you must use a wildcard (*) as the resource.

The following Amazon EC2 Auto Scaling actions do not support resource-level permissions.

  • DescribeAccountLimits

  • DescribeAdjustmentTypes

  • DescribeAutoScalingGroups

  • DescribeAutoScalingInstances

  • DescribeAutoScalingNotificationTypes

  • DescribeInstanceRefreshes

  • DescribeLaunchConfigurations

  • DescribeLifecycleHooks

  • DescribeLifecycleHookTypes

  • DescribeLoadBalancers

  • DescribeLoadBalancerTargetGroups

  • DescribeMetricCollectionTypes

  • DescribeNotificationConfigurations

  • DescribePolicies

  • DescribeScalingActivities

  • DescribeScalingProcessTypes

  • DescribeScheduledActions

  • DescribeTags

  • DescribeTerminationPolicyTypes

  • DescribeWarmPool

Policy condition keys for Amazon EC2 Auto Scaling

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.

Amazon EC2 Auto Scaling defines its own set of condition keys and also supports using some global condition keys.

Amazon EC2 Auto Scaling supports the following condition keys that you can use in permission policies to determine who can access Amazon EC2 Auto Scaling:

  • autoscaling:InstanceTypes

  • autoscaling:LaunchConfigurationName

  • autoscaling:LaunchTemplateVersionSpecified

  • autoscaling:LoadBalancerNames

  • autoscaling:MaxSize

  • autoscaling:MinSize

  • autoscaling:ResourceTag/key-name: tag-value

  • autoscaling:TargetGroupARNs

  • autoscaling:VPCZoneIdentifiers

The following condition keys are specific to create launch configuration requests:

  • autoscaling:ImageId

  • autoscaling:InstanceType

  • autoscaling:MetadataHttpEndpoint

  • autoscaling:MetadataHttpPutResponseHopLimit

  • autoscaling:MetadataHttpTokens

  • autoscaling:SpotPrice

Amazon EC2 Auto Scaling also supports the following global condition keys that you can use to define permissions based on the tags in the request or present on the Auto Scaling group. For more information, see Tag Auto Scaling groups and instances.

  • aws:RequestTag/key-name: tag-value

  • aws:ResourceTag/key-name: tag-value

  • aws:TagKeys: [tag-key, ...]

To learn which Amazon EC2 Auto Scaling API actions you can use a condition key with, see Actions defined by Amazon EC2 Auto Scaling in the Service Authorization Reference. For more information about using Amazon EC2 Auto Scaling condition keys, see Condition keys for Amazon EC2 Auto Scaling.

For examples of IAM policies you can use to control access, see the following topics:

ACLs in Amazon EC2 Auto Scaling

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 Amazon EC2 Auto Scaling

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

ABAC is possible for resources that support tags, but not everything supports tags. Launch configurations and scaling policies don't support tags, but Auto Scaling groups support tags.

For more information about tagging Auto Scaling groups, see Tag Auto Scaling groups and instances.

To view an example of an identity-based policy for limiting access to an Auto Scaling group based on the tags on that group, see Tags for security.

Using temporary credentials with Amazon EC2 Auto Scaling

Supports temporary credentials

Yes

Some Amazon Web Services don't work when you sign in using temporary credentials. For additional information, including which Amazon Web Services work with temporary credentials, see Amazon Web 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 Switching to a 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.

Service roles for Amazon EC2 Auto Scaling

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

When you create a lifecycle hook that notifies an Amazon SNS topic or Amazon SQS queue, you must specify a role to allow Amazon EC2 Auto Scaling to access Amazon SNS or Amazon SQS on your behalf. Use the IAM console to set up the service role for your lifecycle hook. The console helps you create a role with a sufficient set of permissions using a managed policy. For more information, see Receive notifications using Amazon SNS and Receive notifications using Amazon SQS.

When you create an Auto Scaling group, you can optionally pass in a service role to allow Amazon EC2 instances to access other Amazon Web Services on your behalf. The service role for Amazon EC2 instances (also called the Amazon EC2 instance profile for a launch template or launch configuration) is a special type of service role that is assigned to every EC2 instance in an Auto Scaling group when the instance launches. You can use the IAM console and Amazon CLI to create or edit this service role. For more information, see IAM role for applications that run on Amazon EC2 instances.

Warning

Changing the permissions for a service role might break Amazon EC2 Auto Scaling functionality. Edit service roles only when Amazon EC2 Auto Scaling provides guidance to do so.

Service-linked roles for Amazon EC2 Auto Scaling

Supports service-linked roles

Yes

A service-linked role is a type of service role that is linked to an Amazon Web Service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your IAM 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 Amazon EC2 Auto Scaling service-linked roles, see Service-linked roles for Amazon EC2 Auto Scaling.