Cloudformation-coverage-roadmap: AWS::Logs::QueryDefinition

[nonspecialist]

Scope of request

Support for PutQueryDefinition was added to Logs Insights recently, and it would be useful to be able to manage these definitions via CFN so that they can be deployed to multiple environments consistently.

Proposing AWS::Logs::QueryDefinition as the resource type for this.

3. Expected behavior

• on Create, a new Query Definition should be saved, creating optional Folder structures as required. The Query Definition should be identified by a Name, which will be the unique key for saved query definitions. When creating, specification of a log group name that doesn't exist should NOT be an error.
• on Update, existing Query Definitions with changed attributes will be updated; query definitions whose names have changed will result in the removal of the original query definition and the creation of a new query definition with the new name.
• on Delete, query definitions should be removed

4. Suggest specific test cases

• update to a query definition where the log group no longer exists (should not fail)
• drift detection should check name, log groups, and query definition string

5. Helpful Links to speed up research and evaluation

API doc at https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutQueryDefinition.html
Mentioned in Terraform issues at https://github.com/terraform-providers/terraform-provider-aws/issues/13223

6. Category (required) - Will help with tagging and be easier to find by other users to +1

1. Management (CloudWatch)

7. Any additional context (optional)

N/A

[MarcelloLins]

This would be a fantastic gain for any service operators. Having the queries stored on CloudWatch, and the ability to deploy that as a CFN stack / substack would be super nice.