capabilities.work

Provision Data Lake

A 3-step recipe with Amazon Security Lake. We can help you get access.

Recipe · 3 steps

Provision Data Lake

with Amazon Security Lake

Create a data lake in a region and verify it is registered and collecting sources.

  1. Create the data lake in the target region with the supplied encryption, lifecycle, and metadata store manager configuration.
  2. List the data lakes in the account and region to confirm the newly created lake is registered and to capture its current status.
  3. Retrieve a snapshot of which sources the data lake is collecting security data from for the supplied accounts.
What you'll need to have ready
  • region: The AWS region in which to configure the data lake (e.g. us-east-1).
  • metaStoreManagerRoleArn: The ARN of the IAM role for the metadata store manager.
  • kmsKeyId: The KMS key ID used to encrypt data at rest in the data lake.
  • expirationDays: Number of days after which collected data expires.
  • accounts: AWS account IDs to retrieve collecting sources for.
For your developer

Arazzo workflow amazon-security-lake:provision-data-lake, 3 operations: CreateDataLake → ListDataLakes → GetDataLakeSources. Specs on APIs.io.

More recipes with Amazon Security Lake

Decommission Data LakeOffboard SubscriberOnboard AWS Log SourceProvision SubscriberRegister Custom SourceRename Subscriber