AmazonElasticMapReduceFullAccess
Summary
Provides full access to Amazon Elastic MapReduce and the underlying services it requires, such as EC2 and S3. AWS says this policy is on a deprecation path and points to the Amazon EMR documentation for guidance.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AmazonElasticMapReduceFullAccess- Default version
- v8
- Created
- Last edited
- Services
- cloudformation, cloudwatch, ec2, elasticmapreduce, iam, kms, s3, sdb
Control-plane actions (460)
By access level: 73 List, 35 Permissions management, 131 Read, 16 Tagging, 205 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| CloudFormation | 4 of 104 | 1 Read, 2 Tagging, 1 Write; 2 restricted, 2 conditional | cloudformation:CreateStack, cloudformation:DescribeStackEvents, cloudformation:TagResource, cloudformation:UntagResource |
| CloudWatch | All 160 actions (see the CloudWatch page) | 24 List, 8 Permissions management, 46 Read, 2 Tagging, 80 Write; 0 restricted, 0 conditional | cloudwatch:* |
| EC2 | 28 of 834 | 12 List, 2 Tagging, 14 Write; 0 restricted, 0 conditional | ec2:AuthorizeSecurityGroupEgress, ec2:AuthorizeSecurityGroupIngress, ec2:CancelSpotInstanceRequests, ec2:CreateRoute, ec2:CreateSecurityGroup, ec2:CreateTags, ec2:CreateVpcEndpoint, ec2:DeleteRoute, ec2:DeleteSecurityGroup, ec2:DeleteTags, ec2:DescribeAccountAttributes, ec2:DescribeAvailabilityZones and 16 more |
| EMR | All 88 actions (see the EMR page) | 12 List, 3 Permissions management, 20 Read, 2 Tagging, 51 Write; 0 restricted, 0 conditional | elasticmapreduce:* |
| IAM | 5 of 190 | 1 List, 2 Read, 2 Write; 1 restricted, 1 conditional | iam:CreateServiceLinkedRole, iam:GetPolicy, iam:GetPolicyVersion, iam:ListRoles, iam:PassRole |
| KMS | 7 of 58 | 7 List; 0 restricted, 0 conditional | kms:List* |
| S3 | All 155 actions (see the S3 page) | 15 List, 24 Permissions management, 58 Read, 8 Tagging, 50 Write; 0 restricted, 0 conditional | s3:* |
| SimpleDB | All 13 actions (see the SimpleDB page) | 2 List, 4 Read, 7 Write; 0 restricted, 0 conditional | sdb:* |
CloudFormation: 4 actions
- cloudformation:CreateStack (Write)
- cloudformation:DescribeStackEvents (Read)
- cloudformation:TagResource (Tagging)
- cloudformation:UntagResource (Tagging)
EC2: 28 actions
- ec2:AuthorizeSecurityGroupEgress (Write)
- ec2:AuthorizeSecurityGroupIngress (Write)
- ec2:CancelSpotInstanceRequests (Write)
- ec2:CreateRoute (Write)
- ec2:CreateSecurityGroup (Write)
- ec2:CreateTags (Tagging)
- ec2:CreateVpcEndpoint (Write)
- ec2:DeleteRoute (Write)
- ec2:DeleteSecurityGroup (Write)
- ec2:DeleteTags (Tagging)
- ec2:DescribeAccountAttributes (List)
- ec2:DescribeAvailabilityZones (List)
- ec2:DescribeInstances (List)
- ec2:DescribeKeyPairs (List)
- ec2:DescribeNetworkAcls (List)
- ec2:DescribeRouteTables (List)
- ec2:DescribeSecurityGroups (List)
- ec2:DescribeSpotInstanceRequests (List)
- ec2:DescribeSpotPriceHistory (List)
- ec2:DescribeSubnets (List)
- ec2:DescribeVpcAttribute (List)
- ec2:DescribeVpcs (List)
- ec2:ModifyImageAttribute (Write)
- ec2:ModifyInstanceAttribute (Write)
- ec2:RequestSpotInstances (Write)
- ec2:RevokeSecurityGroupEgress (Write)
- ec2:RunInstances (Write)
- ec2:TerminateInstances (Write)
IAM: 5 actions
- iam:CreateServiceLinkedRole (Write)
- iam:GetPolicy (Read)
- iam:GetPolicyVersion (Read)
- iam:ListRoles (List)
- iam:PassRole (Write)
KMS: 7 actions
- kms:ListAliases (List)
- kms:ListGrants (List)
- kms:ListKeyPolicies (List)
- kms:ListKeyRotations (List)
- kms:ListKeys (List)
- kms:ListResourceTags (List)
- kms:ListRetirableGrants (List)
Data-plane actions (30)
By access level: 4 List, 3 Permissions management, 11 Read, 4 Tagging, 8 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| CloudWatch | All 5 actions (see the CloudWatch page) | 1 List, 3 Read, 1 Write; 0 restricted, 0 conditional | cloudwatch:* |
| S3 | All 25 actions (see the S3 page) | 3 List, 3 Permissions management, 8 Read, 4 Tagging, 7 Write; 0 restricted, 0 conditional | s3:* |
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: all-resources.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants at least 80% of the write and permissions-management actions of: cloudwatch (89 of 89), elasticmapreduce (54 of 54), s3 (84 of 84), sdb (7 of 7).
- Grants data-plane write actions on a data store on all resources without conditions.
- Grants iam:PassRole on all resources without conditions.
- 18 granted write or permissions-management actions have no data-plane classification from AWS, so the data-plane rule cannot assess them.
Guidance
Practical scope
The first statement allows, on Resource "*" with no Condition, elasticmapreduce:*, s3:*, cloudwatch:*, sdb:*, kms:List*, iam:PassRole and read actions iam:GetPolicy, iam:GetPolicyVersion and iam:ListRoles, two CloudFormation actions, and EC2 actions including ec2:RunInstances, ec2:TerminateInstances, ec2:CreateSecurityGroup, ec2:DeleteSecurityGroup, ec2:AuthorizeSecurityGroupIngress, ec2:ModifyInstanceAttribute and ec2:CreateVpcEndpoint. iam:CreateServiceLinkedRole is allowed on all resources when the service name matches elasticmapreduce.amazonaws.com or elasticmapreduce.amazonaws.com.cn. cloudformation:TagResource and cloudformation:UntagResource are allowed when cloudformation:CreateAction is CreateStack.
Use cases
- Run and manage Amazon EMR, with the EC2, S3 and related actions it needs. AWS says the policy is on a deprecation path, so check the EMR documentation it links to before using it for new work.
Best practices
- AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.
Security considerations
- s3:*, elasticmapreduce:*, cloudwatch:* and sdb:* allow every action in those services on all resources.
- iam:PassRole is allowed on all resources with no iam:PassedToService condition. The IAM User Guide says a user needs permission to pass a role to an AWS service before the service can be configured with it.
- The EC2 actions include ec2:RunInstances, ec2:TerminateInstances, security group changes and ec2:ModifyInstanceAttribute on all resources.
- You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.
Assignment guidance
You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. AWS marks this policy as being on a deprecation path, so check the guidance it links to before using it in a new permission set. Where a narrower scope is needed, AWS recommends customer managed policies specific to your use cases.
Related policies
Same service
- AccessAnalyzerServiceRolePolicy
- AdministratorAccess-AWSElasticBeanstalk
- AmazonAppFlowFullAccess
- AmazonApplicationRecoveryControllerRegionSwitchPlanExecutionPolicy
- AmazonAppStreamServiceAccess
- AmazonAthenaServiceRolePolicy
- AmazonAuroraDSQLReadOnlyAccess
- AmazonBedrockStudioPermissionsBoundary
Same domain
Frequently asked questions
- When should I attach AmazonElasticMapReduceFullAccess?
- AWS says this policy is on a deprecation path and links to the Amazon EMR documentation for guidance, so review that page before attaching it. The policy is meant for users, groups or roles that need full EMR access together with the EC2 and S3 actions it includes.
- What does AmazonElasticMapReduceFullAccess grant?
- It allows elasticmapreduce:*, s3:*, cloudwatch:* and sdb:* on all resources, EC2 actions to launch and manage instances and security groups, iam:PassRole, read actions for IAM policies and roles, kms:List*, and creating the EMR service-linked role.
- What are the security risks of AmazonElasticMapReduceFullAccess?
- It combines wildcard access to EMR and S3 with EC2 instance control and iam:PassRole on all resources without a service condition. AWS says the policy is on a deprecation path. AWS managed policies do not grant least privilege permissions, and an AWS update to the policy affects every identity it is attached to.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"cloudwatch:*",
"cloudformation:CreateStack",
"cloudformation:DescribeStackEvents",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:CancelSpotInstanceRequests",
"ec2:CreateRoute",
"ec2:CreateSecurityGroup",
"ec2:CreateTags",
"ec2:DeleteRoute",
"ec2:DeleteTags",
"ec2:DeleteSecurityGroup",
"ec2:DescribeAvailabilityZones",
"ec2:DescribeAccountAttributes",
"ec2:DescribeInstances",
"ec2:DescribeKeyPairs",
"ec2:DescribeRouteTables",
"ec2:DescribeSecurityGroups",
"ec2:DescribeSpotInstanceRequests",
"ec2:DescribeSpotPriceHistory",
"ec2:DescribeSubnets",
"ec2:DescribeVpcAttribute",
"ec2:DescribeVpcs",
"ec2:DescribeRouteTables",
"ec2:DescribeNetworkAcls",
"ec2:CreateVpcEndpoint",
"ec2:ModifyImageAttribute",
"ec2:ModifyInstanceAttribute",
"ec2:RequestSpotInstances",
"ec2:RevokeSecurityGroupEgress",
"ec2:RunInstances",
"ec2:TerminateInstances",
"elasticmapreduce:*",
"iam:GetPolicy",
"iam:GetPolicyVersion",
"iam:ListRoles",
"iam:PassRole",
"kms:List*",
"s3:*",
"sdb:*"
],
"Effect": "Allow",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "*",
"Condition": {
"StringLike": {
"iam:AWSServiceName": [
"elasticmapreduce.amazonaws.com",
"elasticmapreduce.amazonaws.com.cn"
]
}
}
},
{
"Sid": "CloudFormationTagOnCreate",
"Effect": "Allow",
"Action": [
"cloudformation:TagResource",
"cloudformation:UntagResource"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"cloudformation:CreateAction": [
"CreateStack"
]
}
}
}
]
}
Version history
Current version v8, edited by AWS on 2026-09-11. 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/AmazonElasticMapReduceFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonElasticMapReduceFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonElasticMapReduceFullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AmazonElasticMapReduceFullAccessTerraform
resource "aws_iam_role_policy_attachment" "amazonelasticmapreducefullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AmazonElasticMapReduceFullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonElasticMapReduceFullAccess"),
);Sources
- AmazonElasticMapReduceFullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)
- Grant a user permissions to pass a role to an AWS service (IAM User Guide) (retrieved ; supports securityConsiderations)