Support for provisioned throughput in aws_msk_cluster

[ryan-dyer-sp]

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_msk_cluster is missing support for the provisioned throughput storage functionality

New or Affected Resource(s)

aws_msk_cluster

Potential Terraform Configuration

broker_node_group_info {
instance_type = var.instance_type
ebs_volume_size = var.ebs_volume_size
ebs_provisioned_throughput = X # if defined, enabled provisioned throughput with corresponding value.
}

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

https://aws.amazon.com/about-aws/whats-new/2022/01/amazon-msk-scale-storage-1000-broker/
https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/kafka@v1.17.4/types#BrokerEBSVolumeInfo

[gregswift]

Would the expectation of supporting this be full provision and re-configure/provision at a later time?

[AdamTylerLynch]

I'm going to pick this issue up.

[AdamTylerLynch]

Would the expectation of supporting this be full provision and re-configure/provision at a later time?

My intended implementation is to allow existing clusters to upgrade their storage to provisioned storage without resource recreation (destroy/create).

[github-actions]

This functionality has been released in v4.15.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.