AWSElasticBeanstalkMulticontainerDocker
Summary
Provide the instances in your multicontainer Docker environment access to use the Amazon EC2 Container Service to manage container deployment tasks.
Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.
Identity
- ARN
arn:aws:iam::aws:policy/AWSElasticBeanstalkMulticontainerDocker- Default version
- v5
- Created
- Last edited
- Services
- aws-marketplace, bedrock, ecs, elasticbeanstalk
Control-plane actions (19)
By access level: 2 List, 4 Read, 1 Tagging, 12 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Marketplace | 3 of 97 | 1 List, 2 Write; 0 restricted, 0 conditional | aws-marketplace:Subscribe, aws-marketplace:Unsubscribe, aws-marketplace:ViewSubscriptions |
| Bedrock | 1 of 232 | 1 List; 0 restricted, 0 conditional | bedrock:ListFoundationModels |
| Elastic Container Service | 13 of 92 | 2 Read, 1 Tagging, 10 Write; 1 restricted, 1 conditional | ecs:DeregisterContainerInstance, ecs:DescribeContainerInstances, ecs:DescribeTasks, ecs:DiscoverPollEndpoint, ecs:Poll, ecs:RegisterContainerInstance, ecs:StartTask, ecs:StartTelemetrySession, ecs:StopTask, ecs:Submit*, ecs:TagResource |
| Elastic Beanstalk | 2 of 50 | 2 Read; 0 restricted, 0 conditional | elasticbeanstalk:DescribeEnvironmentHealth, elasticbeanstalk:DescribeEvents |
Marketplace: 3 actions
- aws-marketplace:Subscribe (Write)
- aws-marketplace:Unsubscribe (Write)
- aws-marketplace:ViewSubscriptions (List)
Bedrock: 1 actions
- bedrock:ListFoundationModels (List)
Elastic Container Service: 13 actions
- ecs:DeregisterContainerInstance (Write)
- ecs:DescribeContainerInstances (Read)
- ecs:DescribeTasks (Read)
- ecs:DiscoverPollEndpoint (Write)
- ecs:Poll (Write)
- ecs:RegisterContainerInstance (Write)
- ecs:StartTask (Write)
- ecs:StartTelemetrySession (Write)
- ecs:StopTask (Write)
- ecs:SubmitAttachmentStateChanges (Write)
- ecs:SubmitContainerStateChange (Write)
- ecs:SubmitTaskStateChange (Write)
- ecs:TagResource (Tagging)
Elastic Beanstalk: 2 actions
- elasticbeanstalk:DescribeEnvironmentHealth (Read)
- elasticbeanstalk:DescribeEvents (Read)
Data-plane actions (1)
By access level: 1 Read.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Bedrock | 1 of 37 | 1 Read; 1 restricted, 0 conditional | bedrock:InvokeModel |
Bedrock: 1 actions
- bedrock:InvokeModel (Read)
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: mixed.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants 13 write, tagging or permissions-management actions, short of full control of any service.
Guidance
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Related policies
Same service
- AdministratorAccess-AWSElasticBeanstalk
- AmazonBedrockAgentCoreMemoryBedrockModelInferenceExecutionRolePolicy
- AmazonBedrockFullAccess
- AmazonBedrockLimitedAccess
- AmazonBedrockMarketplaceAccess
- AmazonBedrockReadOnly
- AmazonBedrockStudioPermissionsBoundary
- AmazonDataZoneBedrockModelConsumptionPolicy
Same domain
Frequently asked questions
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ECSAccess",
"Effect": "Allow",
"Action": [
"ecs:Poll",
"ecs:StartTask",
"ecs:StopTask",
"ecs:DiscoverPollEndpoint",
"ecs:StartTelemetrySession",
"ecs:RegisterContainerInstance",
"ecs:DeregisterContainerInstance",
"ecs:DescribeContainerInstances",
"ecs:Submit*",
"ecs:DescribeTasks"
],
"Resource": "*"
},
{
"Sid": "AllowECSTagResource",
"Effect": "Allow",
"Action": [
"ecs:TagResource"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"ecs:CreateAction": [
"RegisterContainerInstance",
"StartTask"
]
}
}
},
{
"Sid": "AIEnvironmentAnalysisInvokeFoundationModel",
"Effect": "Allow",
"Action": "bedrock:InvokeModel",
"Resource": [
"arn:aws:bedrock:*::foundation-model/anthropic.claude-*",
"arn:aws:bedrock:*::foundation-model/amazon.nova-*"
]
},
{
"Sid": "AIEnvironmentAnalysisInvokeInferenceProfile",
"Effect": "Allow",
"Action": "bedrock:InvokeModel",
"Resource": [
"arn:aws:bedrock:*:*:inference-profile/*anthropic.claude-*",
"arn:aws:bedrock:*:*:inference-profile/*amazon.nova-*"
],
"Condition": {
"StringEquals": {
"aws:ResourceAccount": "${aws:PrincipalAccount}"
}
}
},
{
"Sid": "AIEnvironmentAnalysisReadOnly",
"Effect": "Allow",
"Action": [
"bedrock:ListFoundationModels",
"elasticbeanstalk:DescribeEvents",
"elasticbeanstalk:DescribeEnvironmentHealth"
],
"Resource": "*"
},
{
"Sid": "MarketplaceOperationsFromBedrock",
"Effect": "Allow",
"Action": [
"aws-marketplace:Subscribe",
"aws-marketplace:ViewSubscriptions",
"aws-marketplace:Unsubscribe"
],
"Resource": "*"
}
]
}
Version history
Current version v5, edited by AWS on 2026-04-29. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AWSElasticBeanstalkMulticontainerDocker
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSElasticBeanstalkMulticontainerDocker
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSElasticBeanstalkMulticontainerDockerCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AWSElasticBeanstalkMulticontainerDockerTerraform
resource "aws_iam_role_policy_attachment" "awselasticbeanstalkmulticontainerdocker" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AWSElasticBeanstalkMulticontainerDocker"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AWSElasticBeanstalkMulticontainerDocker"),
);Sources
Pending editorial review. No editorial sources are listed yet.