Can I resize the Turbot ElastiCache nodes?

Yes, it is possible to resize the ElastiCache nodes used by Turbot in the master account, though ElastiCache only natively supports scaling up. For instance, you can resize from cache.m3.medium to cache.m4.large, but cannot scale back down to the cache.m3.medium afterward. In order to scale down, additional steps will need to be taken.

Scaling Up

Please note that while the cache nodes are scaling up, which can take 15-20 minutes, the cache may be unavailable for brief periods of time, which may impact Turbot’s availability.

  1. Follow the steps for Running the Upgrade in Turbot Version Upgrade, except in step 6, instead of uploading a template, select Use current template.
  2. On the Specify Details screen, update ElastiCacheNodeType to the desired cache node size.
  3. Start the stack update and wait until the CloudFormation stack is finished updating. This may take 15-20 minutes and while the ElastiCache nodes are being modified, the cache may be unavailable.
  4. After the update is complete, verify the Turbot console is available, the stack is in the UPDATE_COMPLETE state, and the ElastiCache replication group is in the available status.

Scaling Down

Scaling down is more complicated, as ElastiCache does not allow this through cluster modifications. Instead, a separate ElastiCache replication group will need to be created manually in the same VPC as the original replication group with the Turbot-Console-CacheSecurityGroup security group attached. After this replication group is available, its endpoints will need to be set in the CloudFormation template.

  1. Follow the steps for Running the Upgrade in Turbot Version Upgrade, except in step 6, instead of uploading a template, select Use current template.
  2. On the Specify Details screen, set ElastiCacheCreation to “false”.
  3. Still on the Sepcify Details screen, set ElastiCachePrimaryEndpoint and ElastiCacheSlaveEndpoints. Please note that ElastiCacheSlaveEndpoints is a comma delimited list, e.g., “tucj4boqhcx5ede-001.kfag2k.0001.use1.cache.amazonaws.com,tucj4boqhcx5ede-002.kfag2k.0002.use1.cache.amazonaws.com”. Do not include the ports in the endpoints.
  4. Start the stack update and wait until the CloudFormation stack is finished updating. This may take 15-20 minutes as the Turbot web and workers are re-launched with the new ElastiCache replciation group endpoints.
  5. After the update is complete, verify the Turbot console is available, the stack is in the UPDATE_COMPLETE state, and the ElastiCache replication group is in the available status.

After switching Turbot to use the manually created replication group, if you would like Turbot to use a CloudFormation managed replication group again, re-run the stack update, setting ElastiCacheCreation back to “true” and the ElastiCacheNodeType to the desired cache node size.

Was this article helpful?
0 out of 0 found this helpful