You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running terrascan scan -t aws -v results in resources being flagged as having violations, even though I've suppressed the correct rule on the resource.
What I Did
Here is an example of the resource and the comment:
Description : Ensure Target Group use HTTPs to ensure end to end encryption
File : service_environment\application_load_balancer.tf
Module Name : root
Plan Root : service_environment
Line : 11
Severity : MEDIUM
Rule Name : targetGroupUsingHttp
Rule ID : AC_AWS_042
Resource Name : target_group
Resource Type : aws_lb_target_group
Category : Infrastructure Security
I'm fairly certain I've got the correct rule ID, because if I suppress the rule for the entire scan using --skip-rules, it ignores the violation as expected.
The text was updated successfully, but these errors were encountered:
Hey @quietkatalyst , thanks for raising this issue. This inconsistency was due to non standard reference_id pattern. With PR #786 we have moved to standard Rule IDs. We encourage everyone to use the newly added id for skipping and scanning policies.
In your case the corresponding id is AC_AWS_0492. Also, I noticed you have used " around the rule id, which is invalid. I tested the following for skipping the rule and it worked.
Hi there! Sorry I left this unanswered for so long, I was in the middle of moving. I upgraded to version 1.8.1, gave your changes a shot, and they worked! Thanks so much for the response, I really appreciate it.
Description
Running
terrascan scan -t aws -v
results in resources being flagged as having violations, even though I've suppressed the correct rule on the resource.What I Did
Here is an example of the resource and the comment:
Here is the terrascan violation:
I'm fairly certain I've got the correct rule ID, because if I suppress the rule for the entire scan using
--skip-rules
, it ignores the violation as expected.The text was updated successfully, but these errors were encountered: