- 最新
- 投票最多
- 评论最多
It appears to be inaccurate CFN documentation for ClusterMode:
The schema resource type AWS::ElastiCache::ReplicationGroup handles looks like using lower case values "enabled or disabled" instead of documented "Enabled or Disabled".
I tested using lower case "enabled" in template allows required update of other properties to be invoked, for instance Tags:
MyCfnReplicationGroup:
Type: AWS::ElastiCache::ReplicationGroup
Properties:
...
ClusterMode: enabled
Engine: redis
EngineVersion: "6.2"
...
Tags:
- Key: TestTagChange
Value: changed
We experienced the same event and responded with the following alternative solution.
Remove (or comment out) the ClusterMode property from the template. When we updated the stack, we confirmed that the other properties could be updated. Note that removing (or commenting out) the ClusterMode property does not change the value of the ClusterMode setting.
I contacted AWS support and they said this is an issue on the infrastructure side.
We have received a report of a CloudFormation issue where, when updating a resource in AWS::ElastiCache::ReplicationGroup, the said error is unexpectedly output even though the ClusterMode property has not been changed.
We have shared a temporary solution, but we encourage you to check with AWS Support for the latest information.
In my case, I am using a custom L2 construct for elasticache. I needed to set automatic failover to true as it had been mistakenly set to true. I tried to set the automatic failover to true, but I ended up with the Elasticache: Cluster mode updates are not supported while attempting to update additional properties
error. This response popped up when I googled the error. I updated the cluster mode from the documented Disabled to disabled and deployed that change. Then I updated the automatic failover from false to true and it deployed fine.
I just wanted to make sure there was some google search that might help those struggling with CDK. They're probably using the aws_elasticache module. They might have updated the opensource cdk-redisdb module like I had to do. alternatively, they might be using the L1 construct CfnReplicationGroup in CDK.
相关内容
- AWS 官方已更新 9 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
I had the same issue. The value was set to 'Disabled' when the resource was created. When I tried to modify the resource I got the error noted in op. After changing the value to 'disabled', my update went through. Thanks!