-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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]: Add support for ElastiCache Serverless #34590
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
On the purpose, it would be nice to implement a new resource as proposed in the followings: Requested Resource(s) and/or Data Source(s)
Potential Terraform Configurationresource "aws_vpc" "example" {
cidr_block = "10.0.0.0/16"
}
resource "aws_subnet" "example" {
vpc_id = aws_vpc.example.id
cidr_block = "10.0.1.0/24"
tags = {
Name = "my-subnet"
}
}
resource "aws_elasticache_subnet_group" "example" {
name = "my-cache-subnet"
subnet_ids = [aws_subnet.example.id]
resource "aws_elasticache_user" "default" {
user_id = "defaultUserID"
user_name = "default"
access_string = "on ~app::* -@all +@read +@hash +@bitmap +@geo -setbit -bitfield -hset -hsetnx -hmset -hincrby -hincrbyfloat -hdel -bitop -geoadd -georadius -georadiusbymember"
engine = "REDIS"
passwords = ["password123456789"]
}
resource "aws_elasticache_user_group" "example" {
engine = "REDIS"
user_group_id = "userGroupId"
user_ids = [aws_elasticache_user.default.user_id]
lifecycle {
ignore_changes = [user_ids]
}
}
## Redis cluster
resource "aws_elasticache_serverless" "example" {
cluster_id = "cluster-example" #mandatory
engine = "redis" #mandatory | or "memcached"
description = "Description"
security_group_ids = ["sg-0exxxxxyyyyzzz"]
encryption = "aws/elasticache" # or KMS ARN
user_group = aws_elasticache_user_group.example.user_group_id
subnet_group_name = aws_elasticache_subnet_group.example.name
automatic_backup = false
usage_limits = {
memory = 100 #GB
compute = 10000 #ECPUs
}
tags = {
Name = "my-serverless-cache"
}
} |
I have looked at the changes needed and picked it up. Will update in this forum. |
Done with the resource creation, writing some acpt tests. Will aim for this weeks release for sure. |
I ran some tests and can see the config working on the console....last bits and pieces to tidy up. Getting some panic errors which I hope will be fixed tody |
Most tests work now, just some minor tidy ups and some documentation to go. Nearly there... |
ACCP tests are all fine. Ran a few more today and all are working as intended. Getting ready for the PR now! |
Please track this PR for more details -- #34951 |
This functionality has been released in v5.32.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! |
Hello, |
It seems that the resource "aws_elasticache_serverless_cache" "example" {
engine = "memcached"
name = "example"
}
output "example_endpoint_address" {
value = aws_elasticache_serverless_cache.example.endpoint.0.address
} I'm not sure if this data structure could look different with different configurations (e.g. multiple maps with different |
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. |
Description
As announced by AWS, there is now a serverless option of ElastiCache. This issue is to request adding support for it.
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
No response
References
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: