Configuring rollup Regions in Security Lake
A rollup Region consolidates data from one or more contributing Regions. Specifying a rollup Region can help you comply with Regional compliance requirements.
Important
If you created a custom source, to ensure that custom source data is replicated properly to the destination, Security Lake recommends following the best practices described in Best practices for ingesting custom sources. Replication cannot be performed on data that does not follow the S3 partition data path format as described on the page.
Before adding a rollup Region, you first need to create two different roles in AWS Identity and Access Management (IAM):
Note
Security Lake creates these IAM roles or uses existing roles on your behalf when you use the Security Lake console. However, you must create these roles when using the Security Lake API or AWS CLI.
IAM role for data replication
This IAM role grants permission to Amazon S3 to replicate source logs and events across multiple Regions.
To grant these permissions, create an IAM role that starts with the prefix
SecurityLake, and attach the following sample policy to the role.
You'll need the Amazon Resource Name (ARN) of the role when you create a rollup
Region in Security Lake. In this policy,
sourceRegions are contributing Regions, and
destinationRegions are rollup Regions.
{ "Version": "2012-10-17", "Statement": [ { "Sid": "AllowReadS3ReplicationSetting", "Action": [ "s3:ListBucket", "s3:GetReplicationConfiguration", "s3:GetObjectVersionForReplication", "s3:GetObjectVersion", "s3:GetObjectVersionAcl", "s3:GetObjectVersionTagging", "s3:GetObjectRetention", "s3:GetObjectLegalHold" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::aws-security-data-lake-[[sourceRegions]]*", "arn:aws:s3:::aws-security-data-lake-[[sourceRegions]]*/*" ], "Condition": { "StringEquals": { "s3:ResourceAccount": [ "{{bucketOwnerAccountId}}" ] } } }, { "Sid": "AllowS3Replication", "Action": [ "s3:ReplicateObject", "s3:ReplicateDelete", "s3:ReplicateTags", "s3:GetObjectVersionTagging" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::aws-security-data-lake-[[destinationRegions]]*/*" ], "Condition": { "StringEquals": { "s3:ResourceAccount": [ "{{bucketOwnerAccountId}}" ] } } } ] }
Attach the following trust policy to your role to permit Amazon S3 to assume the role:
{ "Version": "2012-10-17", "Statement": [ { "Sid": "AllowS3ToAssume", "Effect": "Allow", "Principal": { "Service": "s3.amazonaws.com" }, "Action": "sts:AssumeRole" } ] }
If you use a customer managed key from AWS Key Management Service (AWS KMS) to encrypt your Security Lake data lake, you must grant the following permissions in addition to the permissions in the data replication policy.
{ "Action": [ "kms:Decrypt" ], "Effect": "Allow", "Condition": { "StringLike": { "kms:ViaService": [ "s3.{sourceRegion1}.amazonaws.com", "s3.{sourceRegion2}.amazonaws.com" ], "kms:EncryptionContext:aws:s3:arn": [ "arn:aws:s3:::aws-security-data-lake-{sourceRegion1}*", "arn:aws:s3:::aws-security-data-lake-{sourceRegion2}*" ] } }, "Resource": [ "{sourceRegion1KmsKeyArn}", "{sourceRegion2KmsKeyArn}" ] }, { "Action": [ "kms:Encrypt" ], "Effect": "Allow", "Condition": { "StringLike": { "kms:ViaService": [ "s3.{destinationRegion1}.amazonaws.com", ], "kms:EncryptionContext:aws:s3:arn": [ "arn:aws:s3:::aws-security-data-lake-{destinationRegion1}*", ] } }, "Resource": [ "{destinationRegionKmsKeyArn}" ] }
For more information about replication roles, see Setting up permissions in the Amazon Simple Storage Service User Guide.
IAM role to register AWS Glue partitions
This IAM role grants permissions for a partition updater AWS Lambda function used by Security Lake to register AWS Glue partitions for the S3 objects that were replicated from other regions. Without creating this role, subscribers can't query events from those objects.
To grant these permissions, create a role named AmazonSecurityLakeMetaStoreManager (you may have already created this role
while onboarding to Security Lake). For more information about this role, including a sample policy, see Step 1: Create IAM roles.
In the Lake Formation console, you must also grant AmazonSecurityLakeMetaStoreManager permissions as a data lake administrator by following these steps:
Open the Lake Formation console at https://console.aws.amazon.com/lakeformation/
. Sign in as an administrative user.
If a Welcome to Lake Formation window appears, choose the user that you created or selected in Step 1, and then choose Get started.
If you don't see a Welcome to Lake Formation window, then perform the following steps to configure a Lake Formation Administrator.
In the navigation pane, under Permissions, choose Administrative Roles and tasks. In the Data lake administrators section of the console page, choose Choose administrators.
In the Manage data lake administrators dialog box, for IAM users and roles, choose the AmazonSecurityLakeMetaStoreManager IAM role that you created, and then choose Save.
For more information about changing permissions for data lake administrators, see Create a data lake administrator in the AWS Lake Formation Developer Guide.
Adding rollup Regions
Choose your preferred access method, and follow these steps to add a rollup Region.
Note
A Region can contribute data to multiple rollup Regions. However, a rollup Region cannot be a contributing Region for another rollup Region.
Updating or removing rollup Regions
Choose your preferred access method, and follow these steps to update or remove rollup Regions in Security Lake.
