New resource: aws_cloudwatch_query_definition

[mwarkentin]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS just added Saved Queries for AWS Cloudwatch Logs Insights. It would be nice to be able to manage and programatically generate saved queries using Terraform.

New or Affected Resource(s)

• aws_cloudwatch_query_definition

Potential Terraform Configuration

resource "aws_cloudwatch_query_definition" "lambda_latency" {
  "logGroupNames": [
    "/aws/lambda/foo",
    "/aws/lambda/bar",
  ],
  "name": "/lambda/latency/foo_bar",
  "queryString": <<EOF
filter @type = "REPORT"
| stats avg(@duration), max(@duration), min(@duration) by bin(5m)
EOF
}

References

• https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-cloudwatch-logs-insights-now-allows-you-to-save-queries/
• https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutQueryDefinition.html
• https://awscli.amazonaws.com/v2/documentation/api/latest/reference/logs/put-query-definition.html

[nerixim]

SDK support is available since v1.30.23 https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md#release-v13023-2020-05-07

SDK Reference

[ghost]

This has been released in version 3.35.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!