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

[New Resource]: Support for ElastiCache Reserved Nodes #28060

Open
mousavian opened this issue Nov 29, 2022 · 3 comments · May be fixed by #29832
Open

[New Resource]: Support for ElastiCache Reserved Nodes #28060

mousavian opened this issue Nov 29, 2022 · 3 comments · May be fixed by #29832
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service.

Comments

@mousavian
Copy link

mousavian commented Nov 29, 2022

Description

Like EC2 and RDS, Amazon's ElastiCache also allows the purchase of reserved nodes which are used if compatible ElastiCache nodes are spun up. It'd be great if the AWS provider supported the creation of these!

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

Data Sources:

  • aws_elasticache_reserved_cache_node_offering

Resources:

  • aws_elasticache_reserved_cache_node

Potential Terraform Configuration

data "aws_elasticache_reserved_cache_node_offering" "redis_micro" {
  db_instance_class   = "cache.t1.micro"
  duration            = 31536000
  offering_type       = "No Upfront"
  product_description = "redis"
}

resource "aws_elasticache_reserved_cache_node" "example" {
  offering_id    = data.aws_rds_reserved_instance_offering.redis_micro.offering_id
  reservation_id = "optionalCustomReservationID"
  node_count     = 3
}

References

Would you like to implement a fix?

Yes

@mousavian mousavian added the needs-triage Waiting for first response or review from a maintainer. label Nov 29, 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/elasticache Issues and PRs that pertain to the elasticache service. label Nov 29, 2022
@ewbankkit ewbankkit added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 29, 2022
@kseniyashaydurova
Copy link

Hi! Is it planned any progress on this?

@mousavian mousavian linked a pull request Mar 7, 2023 that will close this issue
@swarner1033
Copy link

Could this be actioned considering that a fix has been written? #29832
This would be very useful as its easy to make mistakes in the console when purchasing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants