Skip to main content
IAM Policy Map

AmazonSecurityLakeMetastoreManager

OperatorService roleActivePermissions reviewedShow on mapCompare

Summary

Policy for Amazon SecurityLake meta store manager lambda which allows the access to cloudwatch, S3, Glue and SQS.

Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.

Identity

ARN
arn:aws:iam::aws:policy/service-role/AmazonSecurityLakeMetastoreManager
Default version
v2
Created
Last edited
Services
glue, logs, s3, sqs

Control-plane actions (10)

By access level: 3 Read, 7 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
Glue4 of 3061 Read, 3 Write; 4 restricted, 4 conditionalglue:BatchCreatePartition, glue:CreatePartition, glue:GetTable, glue:UpdateTable
CloudWatch Logs3 of 1333 Write; 3 restricted, 3 conditionallogs:CreateLogGroup, logs:CreateLogStream, logs:PutLogEvents
SQS3 of 202 Read, 1 Write; 3 restricted, 3 conditionalsqs:DeleteMessage, sqs:GetQueueAttributes, sqs:ReceiveMessage
Glue: 4 actions
  • glue:BatchCreatePartition (Write)
  • glue:CreatePartition (Write)
  • glue:GetTable (Read)
  • glue:UpdateTable (Write)
CloudWatch Logs: 3 actions
  • logs:CreateLogGroup (Write)
  • logs:CreateLogStream (Write)
  • logs:PutLogEvents (Write)
SQS: 3 actions
  • sqs:DeleteMessage (Write)
  • sqs:GetQueueAttributes (Read)
  • sqs:ReceiveMessage (Read)

Data-plane actions (4)

By access level: 1 List, 1 Read, 2 Write.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
S34 of 251 List, 1 Read, 2 Write; 4 restricted, 4 conditionals3:DeleteObject, s3:GetObject, s3:ListBucket, s3:PutObject
S3: 4 actions
  • s3:DeleteObject (Write)
  • s3:GetObject (Read)
  • s3:ListBucket (List)
  • 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 9 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.

Same service

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

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowWriteLambdaLogs",
      "Effect": "Allow",
      "Action": [
        "logs:CreateLogStream",
        "logs:PutLogEvents",
        "logs:CreateLogGroup"
      ],
      "Resource": [
        "arn:aws:logs:*:*:log-group:/aws/lambda/AmazonSecurityLake*",
        "arn:aws:logs:*:*:/aws/lambda/AmazonSecurityLake*"
      ],
      "Condition": {
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    },
    {
      "Sid": "AllowGlueManage",
      "Effect": "Allow",
      "Action": [
        "glue:CreatePartition",
        "glue:BatchCreatePartition",
        "glue:GetTable",
        "glue:UpdateTable"
      ],
      "Resource": [
        "arn:aws:glue:*:*:table/amazon_security_lake_glue_db*/*",
        "arn:aws:glue:*:*:database/amazon_security_lake_glue_db*",
        "arn:aws:glue:*:*:catalog"
      ],
      "Condition": {
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    },
    {
      "Sid": "AllowToReadFromSqs",
      "Effect": "Allow",
      "Action": [
        "sqs:ReceiveMessage",
        "sqs:DeleteMessage",
        "sqs:GetQueueAttributes"
      ],
      "Resource": [
        "arn:aws:sqs:*:*:AmazonSecurityLake*"
      ],
      "Condition": {
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    },
    {
      "Sid": "AllowMetaDataReadWrite",
      "Effect": "Allow",
      "Action": [
        "s3:ListBucket",
        "s3:PutObject",
        "s3:GetObject"
      ],
      "Resource": [
        "arn:aws:s3:::aws-security-data-lake*"
      ],
      "Condition": {
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    },
    {
      "Sid": "AllowMetaDataCleanup",
      "Effect": "Allow",
      "Action": [
        "s3:DeleteObject"
      ],
      "Resource": [
        "arn:aws:s3:::aws-security-data-lake*/metadata/*.avro",
        "arn:aws:s3:::aws-security-data-lake*/metadata/*.metadata.json"
      ],
      "Condition": {
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    }
  ]
}

Version history

Current version v2, edited by AWS on 2024-04-01. 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/service-role/AmazonSecurityLakeMetastoreManager
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AmazonSecurityLakeMetastoreManager
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AmazonSecurityLakeMetastoreManager

CloudFormation

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

Terraform

resource "aws_iam_role_policy_attachment" "service_role_amazonsecuritylakemetastoremanager" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/service-role/AmazonSecurityLakeMetastoreManager"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("service-role/AmazonSecurityLakeMetastoreManager"),
);

Sources

Pending editorial review. No editorial sources are listed yet.