Skip to content
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

Fix: Use list(string) for var.policy #124

Closed
wants to merge 2 commits into from
Closed

Conversation

korenyoni
Copy link
Member

@korenyoni korenyoni commented Dec 28, 2021

Copy link

@bridgecrew bridgecrew bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bridgecrew has found infrastructure configuration errors in this PR ⬇️

@@ -9,6 +9,9 @@ locals {
s3_replication_rules = var.replication_rules == null ? var.s3_replication_rules : var.replication_rules

public_access_block_enabled = var.block_public_acls || var.block_public_policy || var.ignore_public_acls || var.restrict_public_buckets

# Try to return the first element, if that doesn't work, try the tostring approach
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MEDIUM   Ensure CloudWatch logs are encrypted at rest using KMS CMKs
    Resource: aws_cloudwatch_log_group.app | ID: BC_AWS_LOGGING_21

Description

AWS CloudWatch Logs is a web service that stores logs from various AWS services, including Lambda function runs and ECS tasks. AWS Key Management Service (KMS) is a managed service that helps create and control the encryption keys used to encrypt account data. It uses Hardware Security Modules (HSMs) to protect the security of encryption keys. CloudWatch logs can be configured to leverage server-side encryption (SSE) and KMS customer created master keys (CMK) to further protect log data.

We recommend you configure CloudWatch log groups to use SSE-KMS to provide additional confidentiality controls on log data. A given user must have S3 read permission on the corresponding log bucket and must be granted decrypt permission by the CMK policy.

Dependent Resources



Calculating...

🎉   Fixed by commit 90366da - Use list(string) for var.policy.

@@ -9,6 +9,9 @@ locals {
s3_replication_rules = var.replication_rules == null ? var.s3_replication_rules : var.replication_rules

public_access_block_enabled = var.block_public_acls || var.block_public_policy || var.ignore_public_acls || var.restrict_public_buckets

# Try to return the first element, if that doesn't work, try the tostring approach
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MEDIUM   Ensure CloudWatch logs are encrypted at rest using KMS CMKs
    Resource: aws_cloudwatch_log_group.app | ID: BC_AWS_LOGGING_21

Description

AWS CloudWatch Logs is a web service that stores logs from various AWS services, including Lambda function runs and ECS tasks. AWS Key Management Service (KMS) is a managed service that helps create and control the encryption keys used to encrypt account data. It uses Hardware Security Modules (HSMs) to protect the security of encryption keys. CloudWatch logs can be configured to leverage server-side encryption (SSE) and KMS customer created master keys (CMK) to further protect log data.

We recommend you configure CloudWatch log groups to use SSE-KMS to provide additional confidentiality controls on log data. A given user must have S3 read permission on the corresponding log bucket and must be granted decrypt permission by the CMK policy.

🎉   Fixed by commit 90366da - Use list(string) for var.policy.

@mergify
Copy link

mergify bot commented Jan 16, 2022

This pull request is now in conflict. Could you fix it @korenyoni? 🙏

@Nuru
Copy link
Contributor

Nuru commented Feb 22, 2022

Closing in favor of adding source_policy_documents in #131

@Nuru Nuru closed this Feb 22, 2022
@Nuru Nuru mentioned this pull request Feb 22, 2022
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

length of privileged_principal_arns not determinable before apply
3 participants