Add support for redshift cluster usage limits

[aristocrates]

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

Add support for Redshift Spectrum and Concurrency Scaling usage limits. Currently modifying this limit requires using the AWS console or the AWS API directly.

New or Affected Resource(s)

• aws_redshift_cluster_usage_limit (and/or usage_limit attribute as block for aws_redshift_cluster)

Potential Terraform Configuration

resource "aws_redshift_cluster_limit" "cluster_spectrum_limit" {
  cluster_identifier = aws_redshift_cluster.cluster_name.cluster_identifier # required
  feature_type       = "spectrum" | "concurrency-scaling" # required
  limit_type         = "time" | "data-scanned" # required
  amount             = type long int # required
  period             = "daily" | "weekly" | "monthly" # optional, default monthly
  breach_action      = "log" | "emit-metric" | "disable" # optional, default log

  tags = {
    # ...
  }
}

or

resource "aws_redshift_cluster" "cluster_name" {
  # ...
  usage_limit {
    # args
  }
}

There can be multiple usage limits of either or both type (spectrum and concurrency scaling) for the same cluster.

There seems to be an account level limit on how many redshift usage limits can exist per type per cluster, but I haven't found any docs indicating what the default is or if there are hard upper limits to the number of limits.

References

• Add support for Concurrency Scaling and Spectrum usage limits terraform-aws-modules/terraform-aws-redshift#41
• https://aws.amazon.com/about-aws/whats-new/2020/04/announcing-cost-controls-for-amazon-redshift-spectrum-and-concurrency-scaling/
• https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-usage-limits.html
• I quickly checked a git log -p -S spectrum and found 9a88bb5 removing/de-vendoring vendor/github.com/aws/aws-sdk-go/service/redshift/api.go that seems to reference making these API operations (CreateUsageLimit, DescribeUsageLimits, ModifyUsageLimit, DeleteUsageLimit), it didn't look like those were ever exposed via a resource. git log -p -S CreateUsageLimit also dug up 557b5fd which bumped aws/aws-sdk-go to v1.30.12 (while vendored), that version added support for redshift cluster usage limits https://github.com/aws/aws-sdk-go/releases/tag/v1.30.12 - current version used here is v1.40.21 (build(deps): bump github.com/aws/aws-sdk-go from 1.40.20 to 1.40.21 in /awsproviderlint #20549)

[github-actions]

This functionality has been released in v4.16.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. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.