- Newest
- Most votes
- Most comments
Hello,
Currently when CloudFormation requires an REPLACEMENT of a resource, there is no workaround for getting around the replacement of the resource.
For the specific AWS::ElastiCache::ReplicationGroup resource, this resource in the past did not support updating the parameter ReplicasPerNodeGroup via console as well. Upon which the cloudformation resource was designed initially.
That being said the Cloudformation service team is aware of this behavior change for the ReplicasPerNodeGroup parameter via the console and are working towards releasing a fix so that you can update ReplicasPerNodeGroup via Cloudformation without a replacement of the cluster in the same way you are able to do it via the console.
I do not have an ETA when this would be released however as soon as it gets released, it should be publicly announced in either one of the following links:
AWS Blog - https://aws.amazon.com/blogs/aws/ AWS New - https://aws.amazon.com/new/
Relevant content
- asked 10 months ago
- Accepted Answerasked 2 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 months ago
- Why can't I view the EventBridge trigger in my Lambda function that my CloudFormation stack created?AWS OFFICIALUpdated 2 months ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago
Searching for a solution for this, I found my own question.
If I change the replica count using the console to the desired amount and then update the CloudFormation to reflect this change, will it be applied without try to do any change additional change or does it enters in drift ?
Thanks.