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]: r/aws_elasticache_serverless_cache: Support minimum cache usage limits #36624

Closed
jar-b opened this issue Mar 28, 2024 · 5 comments · Fixed by #36766
Closed

[Enhancement]: r/aws_elasticache_serverless_cache: Support minimum cache usage limits #36624

jar-b opened this issue Mar 28, 2024 · 5 comments · Fixed by #36766
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues.
Milestone

Comments

@jar-b
Copy link
Member

jar-b commented Mar 28, 2024

Description

AWS now supports setting minimum usage limits for Elasticache serverless caches. Specifically, the cache_usage_limits.data_storage and cache_usage_limits.ecpu_per_second blocks can now include an optional minimum argument.

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

  • aws_elasticache_serverless_cache

Potential Terraform Configuration

resource "aws_elasticache_serverless_cache" "example" {
  # other configuration
  
  cache_usage_limits {
    data_storage {
      minimum = 1000
    }
    ecpu_per_second {
      minimum = 1000
    }
  }
}

References

Would you like to implement a fix?

None

@jar-b jar-b added the enhancement Requests to existing resources that expand the functionality or scope. label Mar 28, 2024
@github-actions github-actions bot added the service/elasticache Issues and PRs that pertain to the elasticache service. label Mar 28, 2024
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.

@jar-b jar-b added good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed service/elasticache Issues and PRs that pertain to the elasticache service. labels Mar 28, 2024
@speedhs
Copy link

speedhs commented Mar 30, 2024

Hey! I would like to read about this and contribute a solution. Can you assign it to me

Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.46.0 milestone Apr 12, 2024
Copy link

This functionality has been released in v5.46.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!

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 May 20, 2024
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. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues.
Projects
None yet
2 participants