AWS MemoryDB for Redis Resources

[kolanos]

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 has recently announced MemoryDB for Redis and it is already GA. Would be great if terraform-provider-aws supported this service. Appears to have a lot of overlap with ElastiCache Redis.

I didn't see an issue for this service, so wanted to make sure one was created to track progress.

New or Affected Resource(s)

• TBD

Potential Terraform Configuration

TBD

References

• Announcement
• Blog post

[ewbankkit]

Requires AWS SDK v1.40.26:

• build(deps): bump github.com/aws/aws-sdk-go from 1.40.24 to 1.40.26 #20632

[grepsedawk]

Appears to have a lot of overlap with ElastiCache Redis.

Definitely a lot of overlap here.
MemoryDB is used for persistance, Elasticache is used for ephemeral

[alexgavrisco]

@ewbankkit @anGie44 Given that MemoryDB is already available in multiple regions, do you have a guesstimate on the timeline for this feature?

[lemon-li]

any progress ?

[grepsedawk]

Bumping this issue won't get you anywhere. If you want this dropped make a PR.

[kaelo-dev]

Does anyone know if Terraform supports MemoryDB For Redis yet?

[grepsedawk]

@kaelo-dev the issue is still open and the aren't any merged PRs, I'd say it probably isn't complete yet.
But you can always check the docs to see if it's been added.

[HugoICSilva]

Any news regarding MemoryDB for Redis in TF?
BR

[grepsedawk]

Bumping this issue won't get your anywhere, don't be rude.
If you want this feature, make a pull request.

[roberth-k]

I'll pick this up.

Looking at the API documentation, there's a lot that can be ported from ElastiCache with some modernisation. I'm planning to trickle this as separate resource PR-s as follows:

• aws_memorydb_subnet_group. This also delivers some of the underlying utility boilerplate, such as tagging functions.
• aws_memorydb_parameter_group
• aws_memorydb_user, which is required for aws_memorydb_acl.
• aws_memorydb_acl
• With the above four in place, aws_memorydb_cluster, but excluding restore from snapshot.
• aws_memorydb_snapshot
• Restore from snapshot support in aws_memorydb_cluster.

I can submit PR-s for a few of the prerequisite resources in before holidays, but the aws_memorydb_cluster would have to wait until next year.

[roberth-k]

With the exception of aws_memorydb_snapshot and sweepers, the service is available as of 3.71.0.

[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.