I’m using both of Prisma’s templates (
aurora.yml) to create my AWS infrastructure. They work really well, and made the setup a breeze. But, they leave me a little worried about performing upgrades. Normally, with a self-built architecture, I’d make changes to tasks and service definitions, etc. But I know that doing so will massively upset CloudFormation, as all changes should be done through CF ideally.
So I’m in a situation such as this: Prisma
v1.9 was just released, but my
fargate.yml file only went up to
v1.8.3 & so the deployment is also on
Assuming I’m upgrading a production environment, I clearly need to do the upgrade with as little downtime as possible (ideally, none).
What is the recommended way of performing these upgrades for both the Fargate and Aurora/RDS stacks?
So far I’ve managed to do the upgrade by:
- Grabbing the latest copy of the
- Doing an “Update Stack” operation
- Providing it with the newly updated template
- Changing the Prisma version selection in the drop-down
- Submitting the changes
It seems to have worked but, (if I’m honest) I’m not sure whether it caused any downtime, or what exactly happened as a result of it.
Under the hood I can see that a new task definition was created and the service was updated to point at this new definition.
But I’m not sure whether this will cause downtime? And whether it causes the Prisma deployment info to be lost? Ie. Do I need to re-
prisma deploy after an update such as this?
With the rapid release cycle of Prisma, I’d really like to make sure that I’ve got a handle on the update process, so that updates can be deployed shortly after they are released.