AWSLambda_FullAccess
Summary
Grants full access to the AWS Lambda service, AWS Lambda console features, and other related AWS services. AWS says it grants full access to Lambda actions and permissions to other AWS services used to develop and maintain Lambda resources.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AWSLambda_FullAccess- Default version
- v7
- Created
- Last edited
- Services
- cloudformation, cloudwatch, ec2, iam, kms, lambda, logs, states, tag, xray
Control-plane actions (146)
By access level: 37 List, 8 Permissions management, 42 Read, 2 Tagging, 57 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| CloudFormation | 2 of 104 | 2 List; 0 restricted, 0 conditional | cloudformation:DescribeStacks, cloudformation:ListStackResources |
| EC2 | 3 of 834 | 3 List; 0 restricted, 0 conditional | ec2:DescribeSecurityGroups, ec2:DescribeSubnets, ec2:DescribeVpcs |
| IAM | 9 of 190 | 3 List, 4 Read, 2 Write; 2 restricted, 2 conditional | iam:CreateServiceLinkedRole, iam:GetPolicy, iam:GetPolicyVersion, iam:GetRole, iam:GetRolePolicy, iam:ListAttachedRolePolicies, iam:ListRolePolicies, iam:ListRoles, iam:PassRole |
| KMS | 2 of 58 | 1 List, 1 Read; 0 restricted, 0 conditional | kms:DescribeKey, kms:ListAliases |
| Lambda | All 121 actions (see the Lambda page) | 25 List, 8 Permissions management, 31 Read, 2 Tagging, 55 Write; 0 restricted, 0 conditional | lambda:* |
| CloudWatch Logs | 6 of 133 | 2 List, 4 Read; 5 restricted, 0 conditional | logs:DescribeLogGroups, logs:DescribeLogStreams, logs:FilterLogEvents, logs:GetLogEvents, logs:StartLiveTail, logs:StopLiveTail |
| Step Functions | 2 of 37 | 1 List, 1 Read; 0 restricted, 0 conditional | states:DescribeStateMachine, states:ListStateMachines |
| Resource Group Tagging | 1 of 9 | 1 Read; 0 restricted, 0 conditional | tag:GetResources |
CloudFormation: 2 actions
- cloudformation:DescribeStacks (List)
- cloudformation:ListStackResources (List)
EC2: 3 actions
- ec2:DescribeSecurityGroups (List)
- ec2:DescribeSubnets (List)
- ec2:DescribeVpcs (List)
IAM: 9 actions
- iam:CreateServiceLinkedRole (Write)
- iam:GetPolicy (Read)
- iam:GetPolicyVersion (Read)
- iam:GetRole (Read)
- iam:GetRolePolicy (Read)
- iam:ListAttachedRolePolicies (List)
- iam:ListRolePolicies (List)
- iam:ListRoles (List)
- iam:PassRole (Write)
KMS: 2 actions
- kms:DescribeKey (Read)
- kms:ListAliases (List)
CloudWatch Logs: 6 actions
- logs:DescribeLogGroups (List)
- logs:DescribeLogStreams (List)
- logs:FilterLogEvents (Read)
- logs:GetLogEvents (Read)
- logs:StartLiveTail (Read)
- logs:StopLiveTail (Read)
Step Functions: 2 actions
- states:DescribeStateMachine (Read)
- states:ListStateMachines (List)
Resource Group Tagging: 1 actions
- tag:GetResources (Read)
Data-plane actions (18)
By access level: 2 List, 3 Read, 13 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| CloudWatch | 2 of 5 | 1 List, 1 Read; 0 restricted, 0 conditional | cloudwatch:GetMetricData, cloudwatch:ListMetrics |
| Lambda | All 14 actions (see the Lambda page) | 1 Read, 13 Write; 0 restricted, 0 conditional | lambda:* |
| X-Ray | 2 of 12 | 1 List, 1 Read; 0 restricted, 0 conditional | xray:BatchGetTraces, xray:GetTraceSummaries |
CloudWatch: 2 actions
- cloudwatch:GetMetricData (Read)
- cloudwatch:ListMetrics (List)
X-Ray: 2 actions
- xray:BatchGetTraces (List)
- xray:GetTraceSummaries (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 at least 80% of the write and permissions-management actions of: lambda (76 of 76).
- Grants iam:PassRole, but only for scoped roles or under conditions (for example iam:PassedToService).
Guidance
Practical scope
The first statement allows lambda:* plus describe, list and get actions for CloudFormation, CloudWatch, Amazon EC2, AWS KMS, IAM, CloudWatch Logs, AWS Step Functions, tagging and AWS X-Ray, on Resource "*". iam:PassRole is allowed on Resource "*" only when iam:PassedToService equals lambda.amazonaws.com. Log reads such as logs:GetLogEvents and logs:StartLiveTail are limited to log groups matching arn:aws:logs:*:*:log-group:/aws/lambda/*. iam:CreateServiceLinkedRole is limited to the AWSServiceRoleForLambda role.
Use cases
- Develop and maintain Lambda functions from the console, including assigning an execution role to a function (the PassRole permission is used when you assign an execution role to a function).
Best practices
- AWS managed policies might not grant least-privilege permissions for your use case. AWS recommends reducing permissions further with customer managed policies specific to your use cases.
Security considerations
- lambda:* allows every Lambda action on all resources. iam:PassRole on Resource "*" is limited by condition to roles passed to lambda.amazonaws.com, which is the permission used when you assign an execution role to a function.
- The policy also grants read access to IAM roles and policies (iam:GetRole, iam:GetRolePolicy, iam:ListRoles and related actions) 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. It fits where full Lambda access is intended. Where a narrower scope is needed, AWS recommends a customer managed policy specific to the use case.
Related policies
Same service
- AmazonDynamoDBFullAccesswithDataPipeline
- AmazonSageMakerPartnerServiceCatalogProductsApiGatewayServiceRolePolicy
- AmazonSageMakerPartnerServiceCatalogProductsCloudFormationServiceRolePolicy
- AmazonSageMakerPipelinesIntegrations
- AmplifyBackendDeployFullAccess
- AWSApplicationAutoscalingLambdaConcurrencyPolicy
- AWSBudgetsSpendLimitMemberRolePolicy
- AWSCodeDeployRoleForCloudFormation
Same domain
Frequently asked questions
- When should I attach AWSLambda_FullAccess?
- The AWS Lambda Developer Guide says you can attach it to your users, groups and roles and that it grants full access to Lambda actions and related services used to develop and maintain Lambda resources. Attach it where that is the intended scope, and use a customer managed policy if you need less.
- What does AWSLambda_FullAccess grant?
- It allows lambda:* and a set of describe, list and get actions for CloudFormation, CloudWatch, Amazon EC2, AWS KMS, IAM, CloudWatch Logs, AWS Step Functions, tagging and AWS X-Ray, plus iam:PassRole to lambda.amazonaws.com and log reads on /aws/lambda/* log groups.
- What are the security risks of AWSLambda_FullAccess?
- lambda:* allows every Lambda action on all resources, and the policy lets a user pass roles to Lambda when assigning execution roles. AWS managed policies might not grant least-privilege permissions for your use case, and AWS updates to the policy affect every identity it is attached to.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"cloudformation:DescribeStacks",
"cloudformation:ListStackResources",
"cloudwatch:ListMetrics",
"cloudwatch:GetMetricData",
"ec2:DescribeSecurityGroups",
"ec2:DescribeSubnets",
"ec2:DescribeVpcs",
"kms:DescribeKey",
"kms:ListAliases",
"iam:GetPolicy",
"iam:GetPolicyVersion",
"iam:GetRole",
"iam:GetRolePolicy",
"iam:ListAttachedRolePolicies",
"iam:ListRolePolicies",
"iam:ListRoles",
"lambda:*",
"logs:DescribeLogGroups",
"states:DescribeStateMachine",
"states:ListStateMachines",
"tag:GetResources",
"xray:GetTraceSummaries",
"xray:BatchGetTraces"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "iam:PassRole",
"Resource": "*",
"Condition": {
"StringEquals": {
"iam:PassedToService": "lambda.amazonaws.com"
}
}
},
{
"Effect": "Allow",
"Action": [
"logs:DescribeLogStreams",
"logs:GetLogEvents",
"logs:FilterLogEvents",
"logs:StartLiveTail",
"logs:StopLiveTail"
],
"Resource": "arn:aws:logs:*:*:log-group:/aws/lambda/*"
},
{
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "arn:aws:iam::*:role/aws-service-role/lambda.amazonaws.com/AWSServiceRoleForLambda",
"Condition": {
"StringEquals": {
"iam:AWSServiceName": "lambda.amazonaws.com"
}
}
}
]
}
Version history
Current version v7, edited by AWS on 2026-02-12. 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/AWSLambda_FullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSLambda_FullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSLambda_FullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AWSLambda_FullAccessTerraform
resource "aws_iam_role_policy_attachment" "awslambda_fullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AWSLambda_FullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AWSLambda_FullAccess"),
);Sources
- AWSLambda_FullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, assignmentGuidance, faqs)
- AWS managed policies for AWS Lambda (AWS Lambda Developer Guide) (retrieved ; supports summary, useCases, bestPractices, securityConsiderations, assignmentGuidance, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)