-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update AWS Terraform Modules to configure consolidated CT #32
Comments
afiune
added a commit
that referenced
this issue
Jun 29, 2020
Closes #32 Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
afiune
added a commit
that referenced
this issue
Jun 29, 2020
Closes #32 Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
afiune
added a commit
that referenced
this issue
Jun 30, 2020
Closes #32 Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
afiune
added a commit
that referenced
this issue
Jun 30, 2020
Closes #32 *Enable New Consolidated CloudTrail Configuration* This example enables a new Consolidated CloudTrail and IAM Role for Lacework, then configures both integrations with Lacework, finally, it configures a new CloudTrail in an AWS sub-account that points to the main CloudTrail. ```hcl provider "lacework" { alias = "main" } provider "aws" { alias = "main" } module "main_cloudtrail" { source = "github.com/lacework/terraform-provisioning/aws/modules/cloudtrail" providers = { aws = aws.main lacework = lacework.main } consolidated_trail = true } provider "aws" { alias = "sub_account" } resource "aws_cloudtrail" "lw_sub_account_cloudtrail" { provider = aws.sub_account name = "lacework-sub-trail" is_multi_region_trail = true s3_bucket_name = module.main_cloudtrail.bucket_name sns_topic_name = module.main_cloudtrail.sns_arn } ``` Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
afiune
added a commit
that referenced
this issue
Jun 30, 2020
Closes #32 **Enable New Consolidated CloudTrail Configuration** This example enables a new Consolidated CloudTrail and IAM Role for Lacework, then configures both integrations with Lacework, finally, it configures a new CloudTrail in an AWS sub-account that points to the main CloudTrail. ```hcl provider "lacework" { alias = "main" } provider "aws" { alias = "main" } module "main_cloudtrail" { source = "github.com/lacework/terraform-provisioning/aws/modules/cloudtrail" providers = { aws = aws.main lacework = lacework.main } consolidated_trail = true } provider "aws" { alias = "sub_account" } resource "aws_cloudtrail" "lw_sub_account_cloudtrail" { provider = aws.sub_account name = "lacework-sub-trail" is_multi_region_trail = true s3_bucket_name = module.main_cloudtrail.bucket_name sns_topic_name = module.main_cloudtrail.sns_arn } ``` Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
afiune
added a commit
that referenced
this issue
Jun 30, 2020
Closes #32 **Enable New Consolidated CloudTrail Configuration** This example enables a new Consolidated CloudTrail and IAM Role for Lacework, then configures both integrations with Lacework, finally, it configures a new CloudTrail in an AWS sub-account that points to the main CloudTrail. ```hcl provider "lacework" { alias = "main" } provider "aws" { alias = "main" } module "main_cloudtrail" { source = "github.com/lacework/terraform-provisioning/aws/modules/cloudtrail" providers = { aws = aws.main lacework = lacework.main } consolidated_trail = true } provider "aws" { alias = "sub_account" } resource "aws_cloudtrail" "lw_sub_account_cloudtrail" { provider = aws.sub_account name = "lacework-sub-trail" is_multi_region_trail = true s3_bucket_name = module.main_cloudtrail.bucket_name sns_topic_name = module.main_cloudtrail.sns_arn } ``` Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Useful information to accomplish this task:
https://www.padok.fr/en/blog/terraform-aws-accounts#:~:text=You%20can%20now%20apply%20the,actions%20on%20the%20others%20accounts!
padok.frApply the same Terraform on multiple AWS accountsYou want to apply the same terraform code to several Amazon Web Services (AWS) accounts? Learn how to use IAM to change the terraform provider parameter
https://www.terraform.io/docs/configuration/providers.html#alias-multiple-provider-instances
Terraform by HashiCorp
Providers - Configuration Language - Terraform by HashiCorp
Providers are responsible in Terraform for managing the lifecycle of a resource: create, read, update, delete.
https://www.terraform.io/docs/providers/aws/index.html
Terraform by HashiCorpProvider: AWS - Terraform by HashiCorpThe Amazon Web Services (AWS) provider is used to interact with the many resources supported by AWS. The provider needs to be configured with the proper credentials before it can be used.
Solution Example
JIRA: ALLY-90
The text was updated successfully, but these errors were encountered: