Skip to main content
IAM Policy Map

AWSLambdaFullAccess

High privilegeAdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides full access to Lambda, S3, DynamoDB, CloudWatch Metrics and Logs. AWS says this policy is on a deprecation path and points to the Lambda 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/AWSLambdaFullAccess
Default version
v8
Created
Last edited
Services
cloudformation, cloudwatch, cognito-identity, cognito-sync, dynamodb, ec2, events, iam, iot, kinesis, kms, lambda, logs, s3, sns, sqs, tag, xray

Control-plane actions (750)

By access level: 136 List, 51 Permissions management, 208 Read, 20 Tagging, 335 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
CloudFormation5 of 1042 List, 3 Read; 0 restricted, 0 conditionalcloudformation:DescribeChangeSet, cloudformation:DescribeStackResources, cloudformation:DescribeStacks, cloudformation:GetTemplate, cloudformation:ListStackResources
CloudWatchAll 160 actions (see the CloudWatch page)24 List, 8 Permissions management, 46 Read, 2 Tagging, 80 Write; 0 restricted, 0 conditionalcloudwatch:*
Cognito Identity1 of 211 List; 0 restricted, 0 conditionalcognito-identity:ListIdentityPools
Cognito Sync2 of 191 Read, 1 Write; 0 restricted, 0 conditionalcognito-sync:GetCognitoEvents, cognito-sync:SetCognitoEvents
DynamoDBAll 68 actions (see the DynamoDB page)7 List, 3 Permissions management, 22 Read, 2 Tagging, 34 Write; 0 restricted, 0 conditionaldynamodb:*
EC23 of 8343 List; 0 restricted, 0 conditionalec2:DescribeSecurityGroups, ec2:DescribeSubnets, ec2:DescribeVpcs
EventBridgeAll 71 actions (see the EventBridge page)15 List, 4 Permissions management, 12 Read, 2 Tagging, 38 Write; 0 restricted, 0 conditionalevents:*
IAM8 of 1903 List, 4 Read, 1 Write; 0 restricted, 0 conditionaliam:GetPolicy, iam:GetPolicyVersion, iam:GetRole, iam:GetRolePolicy, iam:ListAttachedRolePolicies, iam:ListRolePolicies, iam:ListRoles, iam:PassRole
IoT12 of 2933 List, 2 Permissions management, 2 Read, 5 Write; 0 restricted, 0 conditionaliot:AttachPrincipalPolicy, iot:AttachThingPrincipal, iot:CreateKeysAndCertificate, iot:CreatePolicy, iot:CreateThing, iot:CreateTopicRule, iot:DescribeEndpoint, iot:GetTopicRule, iot:ListPolicies, iot:ListThings, iot:ListTopicRules, iot:ReplaceTopicRule
Kinesis2 of 421 List, 1 Read; 0 restricted, 0 conditionalkinesis:DescribeStream, kinesis:ListStreams
KMS1 of 581 List; 0 restricted, 0 conditionalkms:ListAliases
LambdaAll 121 actions (see the Lambda page)25 List, 8 Permissions management, 31 Read, 2 Tagging, 55 Write; 0 restricted, 0 conditionallambda:*
CloudWatch LogsAll 133 actions (see the CloudWatch Logs page)33 List, 2 Permissions management, 26 Read, 4 Tagging, 68 Write; 0 restricted, 0 conditionallogs:*
S3All 155 actions (see the S3 page)15 List, 24 Permissions management, 58 Read, 8 Tagging, 50 Write; 0 restricted, 0 conditionals3:*
SNS5 of 403 List, 2 Write; 0 restricted, 0 conditionalsns:ListSubscriptions, sns:ListSubscriptionsByTopic, sns:ListTopics, sns:Subscribe, sns:Unsubscribe
SQS2 of 201 Read, 1 Write; 0 restricted, 0 conditionalsqs:ListQueues, sqs:SendMessage
Resource Group Tagging1 of 91 Read; 0 restricted, 0 conditionaltag:GetResources
CloudFormation: 5 actions
  • cloudformation:DescribeChangeSet (Read)
  • cloudformation:DescribeStackResources (Read)
  • cloudformation:DescribeStacks (List)
  • cloudformation:GetTemplate (Read)
  • cloudformation:ListStackResources (List)
Cognito Identity: 1 actions
  • cognito-identity:ListIdentityPools (List)
Cognito Sync: 2 actions
  • cognito-sync:GetCognitoEvents (Read)
  • cognito-sync:SetCognitoEvents (Write)
EC2: 3 actions
  • ec2:DescribeSecurityGroups (List)
  • ec2:DescribeSubnets (List)
  • ec2:DescribeVpcs (List)
IAM: 8 actions
  • iam:GetPolicy (Read)
  • iam:GetPolicyVersion (Read)
  • iam:GetRole (Read)
  • iam:GetRolePolicy (Read)
  • iam:ListAttachedRolePolicies (List)
  • iam:ListRolePolicies (List)
  • iam:ListRoles (List)
  • iam:PassRole (Write)
IoT: 12 actions
  • iot:AttachPrincipalPolicy (Permissions management)
  • iot:AttachThingPrincipal (Write)
  • iot:CreateKeysAndCertificate (Write)
  • iot:CreatePolicy (Permissions management)
  • iot:CreateThing (Write)
  • iot:CreateTopicRule (Write)
  • iot:DescribeEndpoint (Read)
  • iot:GetTopicRule (Read)
  • iot:ListPolicies (List)
  • iot:ListThings (List)
  • iot:ListTopicRules (List)
  • iot:ReplaceTopicRule (Write)
Kinesis: 2 actions
  • kinesis:DescribeStream (Read)
  • kinesis:ListStreams (List)
KMS: 1 actions
  • kms:ListAliases (List)
SNS: 5 actions
  • sns:ListSubscriptions (List)
  • sns:ListSubscriptionsByTopic (List)
  • sns:ListTopics (List)
  • sns:Subscribe (Write)
  • sns:Unsubscribe (Write)
SQS: 2 actions
  • sqs:ListQueues (Read)
  • sqs:SendMessage (Write)
Resource Group Tagging: 1 actions
  • tag:GetResources (Read)

Data-plane actions (68)

By access level: 4 List, 3 Permissions management, 21 Read, 4 Tagging, 36 Write.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
CloudWatchAll 5 actions (see the CloudWatch page)1 List, 3 Read, 1 Write; 0 restricted, 0 conditionalcloudwatch:*
DynamoDBAll 17 actions (see the DynamoDB page)9 Read, 8 Write; 0 restricted, 0 conditionaldynamodb:*
EventBridgeAll 3 actions (see the EventBridge page)3 Write; 0 restricted, 0 conditionalevents:*
Kinesis1 of 51 Write; 0 restricted, 0 conditionalkinesis:PutRecord
LambdaAll 14 actions (see the Lambda page)1 Read, 13 Write; 0 restricted, 0 conditionallambda:*
S3All 25 actions (see the S3 page)3 List, 3 Permissions management, 8 Read, 4 Tagging, 7 Write; 0 restricted, 0 conditionals3:*
SNSAll 1 actions (see the SNS page)1 Write; 0 restricted, 0 conditionalsns:Publish
X-Ray2 of 122 Write; 0 restricted, 0 conditionalxray:PutTelemetryRecords, xray:PutTraceSegments
Kinesis: 1 actions
  • kinesis:PutRecord (Write)
X-Ray: 2 actions
  • xray:PutTelemetryRecords (Write)
  • xray:PutTraceSegments (Write)

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), dynamodb (45 of 45), events (45 of 45), lambda (76 of 76), logs (70 of 70), s3 (84 of 84).
  • Grants data-plane write actions on a data store on all resources without conditions.
  • Grants iam:PassRole on all resources without conditions.
  • 27 granted write or permissions-management actions have no data-plane classification from AWS, so the data-plane rule cannot assess them.

Guidance

Practical scope

One statement allows, on Resource "*" with no Condition, lambda:*, s3:*, dynamodb:*, cloudwatch:*, logs:* and events:*, iam:PassRole, and read actions for IAM roles and policies (iam:GetPolicy, iam:GetPolicyVersion, iam:GetRole, iam:GetRolePolicy, iam:ListAttachedRolePolicies, iam:ListRolePolicies and iam:ListRoles). It also allows IoT actions (including iot:CreateKeysAndCertificate, iot:CreatePolicy, iot:AttachPrincipalPolicy and iot:ReplaceTopicRule), sns:Publish, sns:Subscribe and sns:Unsubscribe, sqs:SendMessage, kinesis:PutRecord, cognito-sync:SetCognitoEvents, X-Ray telemetry writes, and describe, list and get actions for CloudFormation, EC2, Cognito, KMS, SNS, SQS, Kinesis and tagging.

Use cases

  • Use Lambda together with S3, DynamoDB, CloudWatch Metrics and CloudWatch Logs, with full access to those services. AWS says the policy is on a deprecation path, so check the Lambda 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

  • lambda:*, s3:*, dynamodb:*, cloudwatch:*, logs:* and events:* 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 IoT actions include iot:CreateKeysAndCertificate, iot:CreatePolicy and iot:AttachPrincipalPolicy.
  • 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.

Same service

Same domain

Frequently asked questions

When should I attach AWSLambdaFullAccess?
AWS says this policy is on a deprecation path and links to the Lambda documentation for guidance, so review that page before attaching it. The policy is meant for users, groups or roles that need full Lambda access together with S3, DynamoDB, CloudWatch Logs and EventBridge.
What does AWSLambdaFullAccess grant?
It allows lambda:*, s3:*, dynamodb:*, cloudwatch:*, logs:* and events:* on all resources, iam:PassRole, read access to IAM roles and policies, IoT, SNS, SQS, Kinesis and Cognito Sync actions, and X-Ray telemetry writes.
What are the security risks of AWSLambdaFullAccess?
It combines wildcard access to several data services with iam:PassRole on all resources and no service condition, plus IoT credential and policy actions. 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

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "cloudformation:DescribeChangeSet",
        "cloudformation:DescribeStackResources",
        "cloudformation:DescribeStacks",
        "cloudformation:GetTemplate",
        "cloudformation:ListStackResources",
        "cloudwatch:*",
        "cognito-identity:ListIdentityPools",
        "cognito-sync:GetCognitoEvents",
        "cognito-sync:SetCognitoEvents",
        "dynamodb:*",
        "ec2:DescribeSecurityGroups",
        "ec2:DescribeSubnets",
        "ec2:DescribeVpcs",
        "events:*",
        "iam:GetPolicy",
        "iam:GetPolicyVersion",
        "iam:GetRole",
        "iam:GetRolePolicy",
        "iam:ListAttachedRolePolicies",
        "iam:ListRolePolicies",
        "iam:ListRoles",
        "iam:PassRole",
        "iot:AttachPrincipalPolicy",
        "iot:AttachThingPrincipal",
        "iot:CreateKeysAndCertificate",
        "iot:CreatePolicy",
        "iot:CreateThing",
        "iot:CreateTopicRule",
        "iot:DescribeEndpoint",
        "iot:GetTopicRule",
        "iot:ListPolicies",
        "iot:ListThings",
        "iot:ListTopicRules",
        "iot:ReplaceTopicRule",
        "kinesis:DescribeStream",
        "kinesis:ListStreams",
        "kinesis:PutRecord",
        "kms:ListAliases",
        "lambda:*",
        "logs:*",
        "s3:*",
        "sns:ListSubscriptions",
        "sns:ListSubscriptionsByTopic",
        "sns:ListTopics",
        "sns:Publish",
        "sns:Subscribe",
        "sns:Unsubscribe",
        "sqs:ListQueues",
        "sqs:SendMessage",
        "tag:GetResources",
        "xray:PutTelemetryRecords",
        "xray:PutTraceSegments"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v8, edited by AWS on 2017-11-27. 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/AWSLambdaFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSLambdaFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSLambdaFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AWSLambdaFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "awslambdafullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AWSLambdaFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AWSLambdaFullAccess"),
);

Sources