AWS Integration - Terraform from Any Supported Host

tip

To integrate with AWS, Lacework recommends using guided configuration. The guided interface takes your input and generates a script that downloads and sets up all necessary Lacework CLI and Terraform components to create the integration non-interactively.

To use guided configuration:

1. In the Lacework Console go to Settings > Integrations > Cloud accounts.
2. Click + Add New.
3. Click Amazon Web Services and select Guided configuration.

Alternatively, follow the steps in this topic for the following methods:

• Use the Lacework CLI to generate and run Terraform code.
• Create the main.tf file manually and run Terraform from any supported host. This may be required for complex integration scenarios.

Overview

This topic describes how to integrate with AWS by running Lacework Terraform modules from any host supported by Terraform.

If you are new to the Lacework Terraform provider, or Lacework Terraform modules, read Terraform for Lacework Overview to learn the basics on how to configure the provider.

note

Lacework Terraform modules for AWS do not support GovCloud integration yet.

Resources Provisioned by Lacework Terraform Modules

To integrate AWS with Lacework, Lacework Terraform modules provision the following resources in the designated AWS account:

• IAM Cross-Account Role - A cross-account role is required to give access to Lacework access for assessments of cloud resource configurations and for analysis of CloudTrail events. The cross-account role is given the following policies:
  • SecurityAudit - AWS-managed policy to provide read-only access to cloud resource configurations.
  • Lacework Custom Audit Policy - A custom policy that extends SecurityAudit to enable read-only access to additional configuration resources.
  • Lacework Custom IAM Policy - A custom policy that provides Lacework read-only access to ingest CloudTrail logs.
• CloudTrail - Lacework can create a new trail or use an existing CloudTrail.
• S3 Bucket - An S3 bucket is required for all CloudTrail integrations. Lacework can use an existing bucket or create a new bucket in the designated account.
• SNS Topic - An SNS topic is required for all CloudTrail integrations. Terraform can use an existing SNS topic or create one if an SNS topic has not been added to an existing CloudTrail.
• SQS Queue - An SQS queue is required for all CloudTrail integrations and monitored by Lacework.

Requirements

• AWS Account Admin - The account used to run Terraform must have administrative privileges on every AWS account you intend to integrate with Lacework.
• AWS CLI - The Terraform provider for AWS leverages the configuration from the AWS CLI and it is recommended the AWS CLI is installed and configured with API keys for the account being integrated.
• Lacework Administrator - A Lacework account with administrator privileges.
• Lacework CLI - The Terraform Provider for Lacework leverages the configuration from the Lacework CLI.
• Terraform - ~> 0.14, ~> 0.15, ~> 1.0, ~> 1.1.
• Ensure that you are deploying the integration to a supported AWS region.

Module Inputs Reference

For an up-to-date guide on all available configuration inputs, refer to the Terraform Registry documentation:

• AWS CloudTrail Module Inputs
• AWS Config Module Inputs
• AWS IAM Role Module Inputs
• AWS CloudTrail for Control Tower Module Inputs

Module Dependencies

Lacework Terraform modules for AWS have the following dependencies that are installed when running terraform init:

• aws
• random
• time

For detailed information on these dependencies, see Lacework on the Terraform Registry.

Install and Configure the Lacework CLI

To configure accounts, the Terraform provider for Lacework leverages the Lacework CLI configuration to authenticate with the Lacework API server. Lacework provides a shell script to install the Lacework CLI in your system.

Follow these instructions to install and configure the Lacework CLI before continuing.

Install the AWS CLI

For details on how to install the AWS CLI, see Configuring your AWS CLI.

Deployment Scenarios

Lacework Terraform modules for AWS support the following deployment scenarios:

• Add Configuration Assessment Only - This deployment scenario configures an AWS account for cloud resource configuration assessment.
• Deploy New CloudTrail and Add Configuration Assessment - This deployment scenario configures a new CloudTrail in an AWS account, configures an AWS account for cloud resource configuration assessment, and integrates the AWS account with Lacework.
• Integrate Existing CloudTrail and Add Configuration Assessment - This deployment scenario uses an existing CloudTrail, S3 bucket, and can create a new or use an existing SNS topic passed as inputs to the module. The example creates the SQS queue and IAM role for Lacework, and then configures both integrations with Lacework.
• New Consolidated CloudTrail - This scenario enables a new consolidated CloudTrail and IAM role for Lacework, then configures both integrations with Lacework. Finally, it configures a new CloudTrail Trail in an AWS sub-account that points to the main CloudTrail.
• Existing Consolidated CloudTrail - This scenario uses a consolidated CloudTrail and creates an IAM role for Lacework, then configures all sub-accounts to be integrated with Lacework.
• AWS Organization Using Control Tower or Similar Structure - This scenario is for integrating with AWS organizations that use AWS Control Tower (or similar setup) to automatically set up their CloudTrail logging. This scenario uses a different module that only creates an IAM role for Lacework in the log_archive account and an SQS queue in the audit account.
• Configure Multiple AWS Accounts - This scenario configures multiple AWS accounts for cloud resource configuration compliance only.
• Existing CloudTrail Using S3 Bucket Notifications - This scenario configures a cross-account IAM role to provide Lacework access to an existing CloudTrail with Lacework and uses S3 Bucket notifications rather than CloudTrail SNS notifications.
• Supplemental: New or Existing CloudTrail with KMS Bucket Encryption - Additional parameters for use of KMS-encrypted S3 buckets.

Scenario 1 - Add Configuration Assessment Only

This scenario configures an AWS account for cloud resource configuration assessment.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws  \
     --config --noninteractive          \
     --aws_region AWSRegion

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see AwsCfg for the Configuration integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Cloud Accounts.

Scenario 2 - Deploy New CloudTrail and Add Configuration Assessment

This scenario creates a new CloudTrail in an AWS account along with a cross-account IAM role to provide Lacework access to monitor CloudTrail, AWS resource configurations, and integrate the AWS account into Lacework.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws       \
     --config --cloudtrail --noninteractive  \
     --aws_region AWSRegion

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see two integrations: AwsCfg for the Configuration integration, and AwsCtSqs for the CloudTrail integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Scenario 3 - Integrate Existing CloudTrail and Add Configuration Assessment

In this scenario, Terraform configures a cross-account IAM role to provide Lacework access to monitor an existing CloudTrail. That same cross-account role also provides Lacework permissions to audit AWS resource configurations and integrate the AWS account into Lacework. An SQS queue is created for Lacework, and you can optionally deploy an SNS topic for that SQS queue if one does not already exist.

About SNS Topics

AWS CloudTrail provides an option to create an SNS topic, which is required to integrate AWS environments with Lacework. The Lacework Terraform module for CloudTrail creates a new SNS topic by default. The SNS topic must be created in the same region as the existing CloudTrail, and it must be manually attached to the CloudTrail by logging in to the AWS console, navigating to CloudTrail, and then selecting the new SNS topic.

Run the Lacework CLI

note

The command must be run in the account that owns the S3 bucket used with the CloudTrail.

1. Run the following CLI command:

   lacework generate cloud-account aws       \
     --config --cloudtrail --noninteractive  \
     --aws_region AWSRegion                  \
     --existing_bucket_arn BucketARN

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

If you have an SNS topic configured on the existing CloudTrail, specify it using the --existing_sns_topic_arn YourExistingTopicARN flag.

If you do not have an existing SNS topic configured on the existing CloudTrail, then the Terraform module automatically creates one, but you must manually attach the SNS topic to the existing CloudTrail.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see two integrations: AwsCfg for the Configuration integration, and AwsCtSqs for the CloudTrail integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Scenario 4 - Deploy New Consolidated CloudTrail and Configuration Assessment

Lacework supports the integration of consolidated CloudTrail deployments where multiple sub-accounts send CloudTrail logs to a main CloudTrail account.

This scenario enables an organization CloudTrail and a cross-account IAM role to give Lacework access to CloudTrail and integrates the AWS accounts into Lacework.

note

For consolidated CloudTrails, Lacework maps the account ID to the account alias for the root account only. Other account IDs are not mapped to their account aliases.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws       \
     --config --cloudtrail --noninteractive  \
     --aws_region RegionOfMainAccount        \
     --consolidated_cloudtrail               \
     --aws_subaccount SubAccount:RegionOfSubAccount
   • To integrate more sub-accounts, provide multiple --aws_subaccount flags.
   • The AWS sub-accounts names you provide must match the profile names in your ~/.aws/credentials file.

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

For more information on organization level CloudTrail deployments, see AWS documentation.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see at least two integrations (depending on how many --aws_subaccount flags you provided): one or more AwsCfg for the Config integration(s), and AwsCtSqs for the CloudTrail integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Scenario 5 - Integrate Existing Consolidated CloudTrail and Configuration Assessment

Lacework supports the integration of consolidated CloudTrail deployments where multiple sub-accounts send CloudTrail logs to a main CloudTrail account.

This scenario uses an existing consolidated CloudTrail, and deploys a cross-account IAM role to give Lacework access to CloudTrail and integrates the AWS accounts into Lacework. The cross-account role also provides Lacework access to assess cloud resource configurations.

note

For consolidated CloudTrails, Lacework maps the account ID to the account alias for the root account only. Other account IDs are not mapped to their account aliases.

About SNS Topics

AWS CloudTrail provides an option to create an SNS topic, which is required to integrate AWS environments with Lacework. The Lacework Terraform module for CloudTrail creates a new SNS topic by default. The SNS topic must be created in the same region as the existing CloudTrail, and it must be manually attached to the CloudTrail by logging in to the AWS console, navigating to CloudTrail, and then selecting the new SNS topic.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws       \
     --config --cloudtrail --noninteractive  \
     --aws_region RegionOfMainAccount        \
     --consolidated_cloudtrail               \
     --existing_bucket_arn BucketARN         \
     --aws_subaccount SubAccount:RegionOfSubAccount

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

If you have an SNS topic configured on the existing CloudTrail, specify it using the --existing_sns_topic_arn YourExistingTopicARN flag.

If you do not have an existing SNS topic configured on the existing CloudTrail, then the Terraform module automatically creates one, but you must manually attach the SNS topic to the existing CloudTrail.

For more information on organization level CloudTrail deployments, see AWS documentation.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see at least two integrations (depending on how many --aws_subaccount flags you provided): one or more AwsCfg for the Configuration integration(s), and AwsCtSqs for the CloudTrail integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Scenario 6 - AWS Organizations Using AWS Control Tower

note

The Terraform solution for Control Tower supports CloudTrail only. To use Terraform to create a Configuration integration for multiple accounts, see Scenario 7 - Configure Multiple AWS Accounts. To use Control Tower to create a Configuration integration, see AWS Control Tower Integration Using CloudFormation.

Lacework supports the integration of consolidated CloudTrail for AWS Organizations using AWS Control Tower (or similar deployments) that split the S3 bucket for the consolidated CloudTrail and the subscribed SNS topic.

This scenario uses an existing consolidated CloudTrail in an S3 bucket, deploys a cross-account IAM role to the log_archive account to give Lacework access to that S3 bucket, deploys an SQS queue for the existing SNS topic in the audit account and finally, integrates the AWS accounts into Lacework.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws controltower \
     --log_archive_account profile:AWSRegion        \
     --audit_account profile:AWSRegion              \
     --sns_topic_arn TopicARN                       \
     --s3_bucket_arn BucketARN --noninteractive

   The profile for --log_archive_account and --audit_account must match the profile names in your ~/.aws/credentials file.

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

If your CloudTrail S3 logs are encrypted, specify the following specify the --bucket_sse_key_arn flag.

If you have an IAM role in your log_archive account that you want to use, specify the --iam_role_name RoleName and --iam_role_arn RoleARN flags. If you do not have an existing IAM role configured in your log_archive account, Terraform automatically creates one. This IAM role MUST be in the log_archive account, not the audit account.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

After Terraform finishes applying changes, use the Lacework CLI or log in to the Lacework Console to confirm the integration is working.

To validate the integration using the CLI, open a Terminal and run lacework cloud-account list. You should see AwsCtSqs for the CloudTrail integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Scenario 7 - Configure Multiple AWS Accounts

This scenario configures multiple AWS accounts for cloud resource configuration compliance only. You must have a corresponding AWS credentials file with the respective profiles listed in the example. For example, if your credentials file includes a profile named development, then use that name in the --aws_subaccount flag in the command.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws --config         \
     --noninteractive --aws_region RegionOfMainAccount  \
     --aws_subaccount SubAccount1:RegionOfSubAccount1   \
     --aws_subaccount SubAccount2:RegionOfSubAccount2   \
     --aws_subaccount SubAccount3:RegionOfSubAccount3

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see as many AwsCfg integrations as --aws_subaccount flags you provided plus the main account.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Scenario 8 - Integrate Existing CloudTrail Using S3 Bucket Notifications

In this scenario, Terraform configures a cross-account IAM role to provide Lacework access to an existing CloudTrail with Lacework and uses S3 Bucket notifications rather than CloudTrail SNS notifications. An SQS queue is created for Lacework, and you can optionally deploy an SNS topic for that SQS queue if one does not already exist.

notes

• If your existing S3 bucket is already sending messages to your existing SQS queue, the new S3 to SQS notification setup (for Lacework) is not possible because both notifications require the same suffix (not allowed by AWS). In this case, you can move to an SNS fanout.
• Terraform must be configured to run using the account that owns the S3 bucket used with the CloudTrail.

Run the Lacework CLI

1. Run the following CLI command:

   lacework generate cloud-account aws  \
     --cloudtrail --noninteractive      \
     --aws_region AWSRegion             \
     --existing_bucket_arn BucketARN    \
     --use_s3_bucket_notification

   The Terraform files are created in the ~/lacework/aws directory.

2. Navigate to the ~/lacework/aws directory.

3. Run terraform plan and review the changes that will be applied.

4. Once satisfied with the changes that will be applied, run terraform apply to execute Terraform.

note

If creating the main.tf file manually, you can use Terraform inputs to customize Lacework Terraform modules. See the documentation on the Terraform Registry for the complete list of inputs for each module.

Validate the Configuration

To confirm that the Cloud Account integrations are working, use the Lacework CLI or log in to the Lacework Console.

To validate the integration using the CLI, run the lacework cloud-account list command. You should see AwsCtSqs for the CloudTrail integration.

To validate the integration using the Lacework Console, log in to your account and go to Settings > Integrations > Cloud Accounts.

Supplemental - For New or Existing CloudTrail with KMS Encrypted Buckets

Lacework supports reading from KMS-encrypted CloudTrail buckets by configuring the cross-account role to give Lacework access to the KMS key.

When the below inputs are added to your Terraform plan, your CloudTrail and S3 are configured to use the provided KMS key, and your cross-account role is updated to allow Lacework to read the KMS key.

Input	Details
bucket_sse_algorithm	For KMS, specify aws:kms
bucket_sse_key_arn	Specify the ARN of your KMS key. (Access to this key is granted to the Lacework IAM cross-account role.)

Example

module "aws_cloudtrail" {
  source  = "lacework/cloudtrail/aws"
  version = "~> 2.0"

  ... More code here ...

  bucket_sse_algorithm    = "aws:kms"
  bucket_sse_key_arn      = "arn:aws:kms:example-region-1:123456789098:key/111aa2bb-333c-4d44-5555-a111bb2c33dd"
}

AWS Security Token Service Limitations

The Lacework AWS module fails due to STS limitations. See AWS STS documentation for more information.

Using aws-vault, for example, requires passing the --no-session flag. See aws-vault documentation for more information.