(aws-route53): add logging configuration method
See original GitHub issueAs far as I know, the domain registration in AWS needs to be a manual step via the UI. That’s fine, however we would like then to make sure via CDK that the logging is properly configured for the HostedZone, but the HostedZone only allows the queryLogsLogArn to be done inside a constructor - so we have a chicken-egg problem.
Could a method for configuring the loggingGroup be added for a HostedZone retrieved by fromLookup
?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Managing Resolver query logging configurations
Configuring (Resolver query logging) · Expand the Route 53 console menu. · Within the Resolver menu, choose Query logging. · In the Region...
Read more >Configuring an Amazon AWS Route 53 Log Source by using ...
Configuring Public DNS Query Logging ; From the Amazon Route 53 navigation pane, select Hosted zones. ; From the Hosted zone details section,...
Read more >Configuring an Amazon AWS Route 53 log source by using an ...
You can collect AWS Route 53 Resolver query logs from multiple accounts or regions in an Amazon S3 bucket. Configure a log source...
Read more >Log and Explore DNS Traffic Using Amazon Route 53 ...
The recently released Route 53 Resolver Query Logs allows customers to gather instance-level detail on DNS query be Customers typically ...
Read more >Amazon Route 53 Configuration Changes | Trend Micro
"DeleteQueryLoggingConfig" - Deletes a configuration for DNS query logging. After you delete a configuration, Amazon Route 53 stops sending ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s fair that the RFC doesn’t specifically call out Route53 HostedZone QueryLoggingConfig; however, I’d much rather have one issue to track the overall desire to be able to mutate imported resources than one per resource/property combination. It’s much harder for us to track impact of hundreds of feature requests with little/no interaction than a single RFC with tens/hundreds of 👍s. The foundational work to allow users to import existing resources into a CDK-owned Stack, and then be able to adjust properties of those resources, is going to be the same for Route53 Hosted Zones, Athena Work Groups, ECS Clusters, etc. Once we’ve done it for one, all should be supported (or easily incrementally added).
Correct. What we don’t support is modifying imported resources, as I said above. You can import a HostedZone today; you just can’t change its QueryLoggingConfig. Similarly, you can import a Bucket today, but you can’t adjust the bucket encryption.
Thanks for detailed explanation. The only comment I have is that… I don’t think that RFC 👍 works - it’s there for 2 years and only 1 👍🏻 - I’m sure that there are a lot of other use cases needing this 😃