AWSLambdaExecute
Summary
Provides Put, Get access to S3 and full access to CloudWatch Logs.
Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.
Identity
- ARN
arn:aws:iam::aws:policy/AWSLambdaExecute- Default version
- v1
- Created
- Last edited
- Services
- logs, s3
Control-plane actions (133)
By access level: 33 List, 2 Permissions management, 26 Read, 4 Tagging, 68 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| CloudWatch Logs | All 133 actions (see the CloudWatch Logs page) | 33 List, 2 Permissions management, 26 Read, 4 Tagging, 68 Write; 133 restricted, 0 conditional | logs:* |
Data-plane actions (2)
By access level: 1 Read, 1 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| S3 | 2 of 25 | 1 Read, 1 Write; 2 restricted, 0 conditional | s3:GetObject, s3:PutObject |
S3: 2 actions
- s3:GetObject (Read)
- s3:PutObject (Write)
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: scoped.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants 75 write, tagging or permissions-management actions, short of full control of any service.
- Grants data-plane write actions on a data store, but only for scoped resources or under conditions.
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
- AlexaForBusinessGatewayExecution
- AmazonAPIGatewayPushToCloudWatchLogs
- AmazonBraketFullAccess
- AmazonBraketJobsExecutionPolicy
- AmazonBraketServiceRolePolicy
- AmazonCloudWatchRUMFullAccess
- AmazonDataZoneProjectRolePermissionsBoundary
- AmazonDMSCloudWatchLogsRole
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": [
{
"Effect": "Allow",
"Action": [
"logs:*"
],
"Resource": "arn:aws:logs:*:*:*"
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject"
],
"Resource": "arn:aws:s3:::*"
}
]
}
Version history
Current version v1, edited by AWS on 2015-02-06. 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/AWSLambdaExecute
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSLambdaExecute
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSLambdaExecuteCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AWSLambdaExecuteTerraform
resource "aws_iam_role_policy_attachment" "awslambdaexecute" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AWSLambdaExecute"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AWSLambdaExecute"),
);Sources
Pending editorial review. No editorial sources are listed yet.