Run kong migrations with AWS ECS

We are doing setup kong as part of task definition (using AWS ECR).
So when we do deliver new image tag it can have migrations (which we can not run by simple rewriting entrypoint, because kong container default entrypoint already setup to be observing requests).
Also when we create task definition - we have to put some health-checkers, because of other kong’s container dependencies.
What is the best approach to run migrations in containerised kong setup on aws?
How to avoid downtimes in that case (database obviously on RDS)?


1 Like