The database migrations need to be applied to the Postgres db to create the tables and indexes for spicedb to work. SpiceDB doesn’t seem to provide an option to always run the migrations at startup, so I don’t believe there’s a way to avoid having to run

spicedb migrate

.

Gotcha. I wonder why I didn't have to run

spicedb migrate

when clicking through and creating a RDS instance though. Hm. In any case i'll add the command to the cloudformation template and revert. Thanks!

Did you create the RDS instance using a snapshot of the previous instance you ran spicedb migrate on when clicking through?

Nope had created it from scratch 🤔

yes this is suggesting the the database schema was never started with

migrate

. This is typically handled by the operator on Kubernetes. Does ECS have the equivalent of a

initContainer

? Then you could add the call to

spicedb migrate

there.