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

Elasticache Replication Group allows replication_group_id to be longer than aws will accept #8379

Closed
devinsba opened this issue Aug 22, 2016 · 2 comments · Fixed by #8381
Closed

Comments

@devinsba
Copy link

replication_group_id is limited to 20 characters by the provider but the AWS API only allows 16. These should really match to save users some frustration.

* aws_elasticache_replication_group.bar: Error creating Elasticache Replication Group: InvalidParameterValue: Replication group id should be no more than 16 characters.
    status code: 400, request id:
@stack72
Copy link
Contributor

stack72 commented Aug 22, 2016

Hi @devinsba

Apologies for the confusion here - this is very odd! The AWS documentation says the following:

--replication-group-id (string)

The replication group identifier. This parameter is stored as a lowercase string.
Constraints:
A name must contain from *1 to 20* alphanumeric characters or hyphens.
The first character must be a letter.
A name cannot end with a hyphen or contain two consecutive hyphens.

This documentation was what the resource was based on - i can update this now

Paul

@ghost
Copy link

ghost commented Apr 23, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants