Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement]: Support for Amazon MSK Tiered storage #27540

Closed
prithvi514 opened this issue Oct 28, 2022 · 4 comments · Fixed by #27546
Closed

[Enhancement]: Support for Amazon MSK Tiered storage #27540

prithvi514 opened this issue Oct 28, 2022 · 4 comments · Fixed by #27546
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/kafka Issues and PRs that pertain to the kafka service.
Milestone

Comments

@prithvi514
Copy link
Contributor

prithvi514 commented Oct 28, 2022

Description

Amazon MSK now supports tiered storage with S3 backend.
Terraform aws_msk_cluster should provide an option to pass [--storage-mode <value>] to the MSK cluster create call.

Affected Resource(s) and/or Data Source(s)

  • aws_msk_cluster

Potential Terraform Configuration

broker_node_group_info {
    instance_type = "kafka.m5.large"
    client_subnets = [
      aws_subnet.subnet_az1.id,
      aws_subnet.subnet_az2.id,
      aws_subnet.subnet_az3.id,
    ]
    storage_info {
      ebs_storage_info {
        volume_size = 1000
      }
      storage_mode = "TIERED"
    }
}

References

https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-msk-offers-low-cost-storage-tier-scales-virtually-unlimited-storage/
https://docs.aws.amazon.com//cli/latest/reference/kafka/create-cluster.html

Would you like to implement a fix?

No response

@prithvi514 prithvi514 added enhancement Requests to existing resources that expand the functionality or scope. needs-triage Waiting for first response or review from a maintainer. labels Oct 28, 2022
@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/kafka Issues and PRs that pertain to the kafka service. label Oct 28, 2022
@bschaatsbergen
Copy link
Member

bschaatsbergen commented Oct 30, 2022

@jar-b jar-b removed the needs-triage Waiting for first response or review from a maintainer. label Oct 31, 2022
@github-actions github-actions bot added this to the v4.40.0 milestone Nov 11, 2022
@github-actions
Copy link

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

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/kafka Issues and PRs that pertain to the kafka service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants