# Updating ElasticCache Memcached instances **URL:** \ **Category:** Rack (Version 2)\ **Created:** [March 2, 2020, 10:45pm UTC](https://community.convox.com/t/updating-elasticcache-memcached-instances/711 "2020-03-02T22:45:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![scott](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@scott](https://community.convox.com/u/scott)\ **Post date:** [March 2, 2020, 10:45pm UTC](https://community.convox.com/t/updating-elasticcache-memcached-instances/711/1 "2020-03-02T22:45:11Z")
I am trying to update from t2.micro’s to t3.micro’s for my Memcached session storage. When I do I get `UPDATE_FAILED CacheCluster Scaling is not supported for engine memcached (Service: AmazonElastiCache; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 9a3be0f3-2ddc-4daf-a6c8-5101670bbd6b)`. It looks like Redis can do an in place upgrade but Memcached cannot. Can it be changed so that Convox will destroy and re-create the node when changing Memcached nodes? ---
**Author:** ![matt](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/matt/32/55_2.png) [@matt](https://community.convox.com/u/matt)\ **Post date:** [August 24, 2020, 7:07pm UTC](https://community.convox.com/t/updating-elasticcache-memcached-instances/711/2 "2020-08-24T19:07:54Z")
I also ran into this issue, changing from Memcached version 1.4 to 1.5. ---
**Author:** ![scott](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@scott](https://community.convox.com/u/scott)\ **Post date:** [August 24, 2020, 7:20pm UTC](https://community.convox.com/t/updating-elasticcache-memcached-instances/711/3 "2020-08-24T19:20:15Z")
I just finished switching the last thing that was still using Memcached (sessions) to Redis and moved on. Memcached isn’t a super active project compared to Redis so it doesn’t surprise me that AWS barely cares about it.