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

AWS Elasticache - Global replication group is not supported for the node type #17768

Closed
OmarSalka opened this issue Feb 23, 2021 · 5 comments
Closed
Labels
service/elasticache Issues and PRs that pertain to the elasticache service.

Comments

@OmarSalka
Copy link

AWS Provider version = v3.29.1

Hi,

I am not able to create a Global Replication Group. I get the following error:

Error: error creating ElastiCache Global Replication Group: InvalidParameterValue: 
Global replication group is not supported for the node type.
status code: 400, request id: xxxxxxxxxxxxxxxxxxxxxxxxxx

But I am using a supported node type cache.t3.medium aaccording to the documentation

Here is the configuration for the primary replication group:

resource "aws_elasticache_replication_group" "ae1" {
  replication_group_id          = "ae1-elasticache-test
  replication_group_description = "ae1-elasticache-test replication group"
  engine                        = "redis"
  engine_version                = "6.0.5"
  node_type                     = "cache.t3.medium"
  number_cache_clusters         = 2
  port                          = 6379
  subnet_group_name             = "subnet-group"
  security_group_ids            = [aws_security_group.redis_sg.id]
  multi_az_enabled              = true
  automatic_failover_enabled    = true
}

Also here's the configuration for the global replication group:

resource "aws_elasticache_global_replication_group" "global" {
  global_replication_group_id_suffix = "elasticache-grg-test
  primary_replication_group_id       = aws_elasticache_replication_group.ae1.id
}
@ghost ghost added the service/elasticache Issues and PRs that pertain to the elasticache service. label Feb 23, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Feb 23, 2021
@OmarSalka
Copy link
Author

tried with a cache.m4.large node type and it's still returning the same error

@OmarSalka
Copy link
Author

I went to the console and tried doing it manually and noticed the list of node types that are supported are different from the documentation. If you could update the aws documentation that would be very much appreciated

image

@bflad
Copy link
Contributor

bflad commented Feb 24, 2021

Hi @OmarSalka 👋 This project is not maintained by AWS (FAQ), however, for this type of documentation update request you can click the "Feedback" link that is present on each of the AWS documentation pages. Please also note that there is a separate page that contains Global Datastores Prerequisites and Limitations and references the required node types, that maybe could be linked.

@OmarSalka
Copy link
Author

Thanks you for sharing that link with me!

@ghost
Copy link

ghost commented Mar 26, 2021

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Mar 26, 2021
@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
Development

No branches or pull requests

3 participants