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

Why is vpcFlowLogsNotEnabled determined to be a violation? #352

Closed
hiromasatakakuma opened this issue Oct 14, 2020 · 0 comments · Fixed by #475
Closed

Why is vpcFlowLogsNotEnabled determined to be a violation? #352

hiromasatakakuma opened this issue Oct 14, 2020 · 0 comments · Fixed by #475
Assignees

Comments

@hiromasatakakuma
Copy link

hiromasatakakuma commented Oct 14, 2020

  • terrascan version: 1.1.0
  • Operating System: macOS

Description

When I define a aws_vpc and aws_flow_log, vpcFlowLogsNotEnabled gives a level medium violation.

What I Did

$ cat vpc.tf
resource "aws_vpc" "example" {
   cidr_block = "xxx.xx.xxx.xxx/xx"
}

resource "aws_flow_log" "example" {
  log_destination      = data.aws_s3_bucket.example.arn
  log_destination_type = "s3"
  traffic_type         = "ALL"
  vpc_id               = aws_vpc.example.id
}

$ terrascan scan -t aws -f vpc.tf
results: results:
   violations:
   --rule_name: vpcFlowLogsNotEnabled
     description: Ensure VPC flow logging is enabled in all VPCs
     rule_id: AWS.VPC.Logging.Medium.0470
     severity: MEDIUM
     category: Logging
     resource_name: example
     resource_type: aws_vpc
     file: vpc.tf
     line: 1
   count:
     low: 0
     medium: 1
     high: 0
     total: 1
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 a pull request may close this issue.

3 participants