hey all, my company's got metaflow deployed via cl...
# ask-metaflow
f
hey all, my company's got metaflow deployed via cloudformation. looking at the published cloudformation template, it references python 3.7 and postgres 11. we got an email from AWS notifying us that we should upgrade. python 3.7 was EOL earlier this year, AWS is ending support for 3.7 lambdas on Nov 27, and it won't be possible to update those lambdas after Jan 25. they recommend updating to 3.11. AWS will be ending support for postgres 11 RDS in February. they recommend upgrading to postgres 14. taking a wild guess that yeeting 3.11 and 14 into the CFN is not a great strategy. my question: is there a recommended upgrade path?
a
With python version it should actually just work (tm). For RDS need to test, in the past they had some issues with updating through cloudformation but i think they were fixed. Worst case you can upgrade RDS from console and edit template later to match, so that cloudformation wouldn't try to do anything to it.
API/Compatibility wise it should just work, i.e. there is nothing in Postgres 14 thatd make it incompatible with metaflow code
f
Thanks very much for the reassurance. Will attempt tomorrow and report back.
so here is my experience: • can't do a major version upgrade to databases via CFN • postgres 14 does not work with
db.t2.small
for some reason so i: 1. made a snapshot 2. upgraded the instance to
db.t3.small
via the console 3. upgraded to version 14 via the console a. our db version was 11.19, and that can only be upgraded to 14.7 4. changed
EngineVersion
to
14
in the CFN template 5. updated the stack using the template a. this resulted in another upgrade, to 14.8, which, fine dunno if that writeup is helpful at all or if it's obvious to somebody who is better-versed in infra than me 😅 . at the very least if the template is changed to 14, the instance class needs to be changed too. happy to make that PR if helpful.