-
Notifications
You must be signed in to change notification settings - Fork 512
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 route53LoggingDisabled.rego to ignore private zones #626
Update route53LoggingDisabled.rego to ignore private zones #626
Conversation
Thanks for the PR! The commit include changes to go.sum and go.mod, was that intentional? if not, perhaps rebase? |
Codecov Report
@@ Coverage Diff @@
## master #626 +/- ##
==========================================
- Coverage 78.13% 78.08% -0.06%
==========================================
Files 103 104 +1
Lines 2570 2596 +26
==========================================
+ Hits 2008 2027 +19
- Misses 420 422 +2
- Partials 142 147 +5
|
…/github.com/matt-slalom/terrascan into route53-private-dns-zone-cannot-use-logging
Ooops. My bad. Should be fixed now, @amirbenv |
pkg/policies/opa/rego/aws/aws_route53_query_log/route53LoggingDisabled.rego
Outdated
Show resolved
Hide resolved
Kudos, SonarCloud Quality Gate passed! |
The AWS module route53LoggingDisabled erroneously requires CloudWatch logging for a private Route 53 zone. Per the documentation, query logging only works when the Route53 hosted zone is public.
See https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_query_log
and
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html?console_help=true#query-logs-configuring