Amazon ECS container instances, including both Amazon EC2 and external instances, run the Amazon ECS container agent and require an IAM role for the service to know that the agent belongs to you. Before you launch container instances and register them to a cluster, you must create an IAM role for your container instances to use. The role is created in the account that you use to log into the console or run the AWS CLI commands.
ImportantIf you are registering external instances to your cluster, the IAM role you use requires Systems Manager permissions as well. For more information, see Amazon ECS Anywhere IAM role.
Amazon ECS provides the AmazonEC2ContainerServiceforEC2Role managed IAM policy which contains the permissions needed to use the full Amazon ECS feature set. This managed policy can be attached to an IAM role and associated with your container instances. Alternatively, you can use the managed policy as a guide when creating a custom policy to use. The container instance role provides permissions needed for the Amazon ECS container agent and Docker daemon to call AWS APIs on your behalf. For more information on the managed policy, see AmazonEC2ContainerServiceforEC2Role.
You can manually create the role and attach the managed IAM policy for container instances to allow Amazon ECS to add permissions for future features and enhancements as they are introduced. Use the following procedure to attach the managed IAM policy if needed.
Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
In the navigation pane of the IAM console, choose Roles, and then choose Create role.
For Trusted entity type, choose AWS service.
For Service or use case, choose Elastic Container Service, and then choose the EC2 Role for Elastic Container Service use case.
Choose Next.
In the Permissions policies section, verify that the AmazonEC2ContainerServiceforEC2Role policy is selected.
ImportantThe AmazonEC2ContainerServiceforEC2Role managed policy should be attached to the container instance IAM role, otherwise you will receive an error using the AWS Management Console to create clusters.
Choose Next.
For Role name, enter ecsInstanceRole
Review the role, and then choose Create role.
Replace all user input with your own values.
Create a file called instance-role-trust-policy.json with the following contents.
JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": { "Service": "ec2.amazonaws.com"},
"Action": "sts:AssumeRole"
}
]
}
Use the following command to create the instance IAM role using the trust policy document.
aws iam create-role \
--role-name ecsInstanceRole \
--assume-role-policy-document file://instance-role-trust-policy.jsonCreate an instance profile named ecsInstanceRole-profile using the create-instance-profile command.
aws iam create-instance-profile --instance-profile-name ecsInstanceRole-profileExample response
{
"InstanceProfile": {
"InstanceProfileId": "AIPAJTLBPJLEGREXAMPLE",
"Roles": [],
"CreateDate": "2022-04-12T23:53:34.093Z",
"InstanceProfileName": "ecsInstanceRole-profile",
"Path": "/",
"Arn": "arn:aws:iam::123456789012:instance-profile/ecsInstanceRole-profile"
}
}Add the ecsInstanceRoleecsInstanceRole-profile
aws iam add-role-to-instance-profile \
--instance-profile-name ecsInstanceRole-profile \
--role-name ecsInstanceRoleAttach the AmazonEC2ContainerServiceRoleForEC2Role managed policy to the role using the following command.
aws iam attach-role-policy \
--policy-arn arn:aws:iam::aws:policy/service-role/AmazonEC2ContainerServiceforEC2Role \
--role-name ecsInstanceRoleAfter you create the role, add additional permissions to the role for the following features.
Amazon ECR permissionsThe Amazon ECS container instance role that you use with your container instances must have the following IAM policy permissions for Amazon ECR.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ecr:BatchCheckLayerAvailability",
"ecr:BatchGetImage",
"ecr:GetDownloadUrlForLayer",
"ecr:GetAuthorizationToken"
],
"Resource": "*"
}
]
}
If you use the AmazonEC2ContainerServiceforEC2Role managed policy for your container instances, then your role has the proper permissions. To check that your role supports Amazon ECR, see Amazon ECS Container Instance IAM Role in the Amazon Elastic Container Service Developer Guide.
Amazon ECS supports launching container instances with increased ENI density using supported Amazon EC2 instance types. When you use this feature, we recommend that you create 2 container instance roles. Enable the awsvpcTrunking account setting for one role and use that role for tasks that require ENI trunking. For information about the awsvpcTrunking account setting, see Access Amazon ECS features with account settings.
The container instance role that you use with your container instances must have the following IAM policy permissions for setting the account setting
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ecs:ListAccountSettings",
"ecs:ListAttributes",
"ecs:PutAccountSetting"
],
"Resource": "*"
}
]
}
In order to use the container instance role, add the following to instance user data:
#!/bin/bash
aws ecs put-account-setting --name awsvpcTrunking --value enabled --region region
ECS_CLUSTER=MyCluster>> /etc/ecs/ecs.config
EOFFor more information about adding user data to your EC2 instances, see Run commands on your Linux instance at launch in the Amazon EC2 User Guide.
Amazon S3 read-only accessStoring configuration information in a private bucket in Amazon S3 and granting read-only access to your container instance IAM role is a secure and convenient way to allow container instance configuration at launch time. You can store a copy of your ecs.config file in a private bucket, use Amazon EC2 user data to install the AWS CLI and then copy your configuration information to /etc/ecs/ecs.config when the instance launches.
For more information about creating an ecs.config file, storing it in Amazon S3, and launching instances with this configuration, see Storing Amazon ECS container instance configuration in Amazon S3.
You can use the following AWS CLI command to allow Amazon S3 read-only access for your container instance role. Replace ecsInstanceRole with the name of the role that you created.
aws iam attach-role-policy \
--role-name ecsInstanceRole \
--policy-arn arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccessYou can also use the IAM console to add Amazon S3 read-only access (AmazonS3ReadOnlyAccess) to your role. For more information, see Updating permissions for a role in the AWS Identity and Access Management User Guide.
The Amazon ECS container instance role that you use with your container instances must have the following IAM policy permissions for setting the account setting
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ecs:ListAccountSettings",
"ecs:ListAttributes",
"ecs:PutAccountSetting"
],
"Resource": "*"
}
]
}
Before your container instances can send log data to CloudWatch Logs, you must create an IAM policy to allow the Amazon ECS agent to write the customer's application logs to CloudWatch (normally handled through the awslogs driver). After you create the policy, attach that policy to ecsInstanceRole.
Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
In the navigation pane on the left, choose Policies.
If this is your first time choosing Policies, the Welcome to Managed Policies page appears. Choose Get Started.
At the top of the page, choose Create policy.
In the Policy editor section, choose the JSON option.
Enter the following JSON policy document:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents",
"logs:DescribeLogStreams"
],
"Resource": ["arn:aws:logs:*:*:*"]
}
]
}Choose Next.
NoteYou can switch between the Visual and JSON editor options anytime. However, if you make changes or choose Next in the Visual editor, IAM might restructure your policy to optimize it for the visual editor. For more information, see Policy restructuring in the IAM User Guide.
On the Review and create page, enter a Policy name and a Description (optional) for the policy that you are creating. Review Permissions defined in this policy to see the permissions that are granted by your policy.
Choose Create policy to save your new policy.
After you create the policy, attach the policy to the container instance role. For information about how to attach the policy to the role, see Updating permissions for a role in the AWS Identity and Access Management User Guide.
Create a file called instance-cw-logs.json with the following content.
JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents",
"logs:DescribeLogStreams"
],
"Resource": ["arn:aws:logs:*:*:*"]
}
]
}
Use the following command to create the IAM policy using the JSON policy document file.
aws iam create-policy \
--policy-name cwlogspolicy \
--policy-document file://instance-cw-logs.jsonRetrieve the ARN of the IAM policy you created using the following command. Replace cwlogspolicy with the name of the policy you created.
aws iam list-policies --scope Local --query 'Policies[?PolicyName==`cwlogspolicy`].Arn'Use the following command to attach the policy to the container instance IAM role using the policy ARN.
aws iam attach-role-policy \
--role-name ecsInstanceRole \
--policy-arn arn:aws:iam:111122223333:aws:policy/cwlogspolicyRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4