Hi there, We are evaluating spicedb in my team and I have managed to successfully run spicedb locally connecting to local postgres running in docker container. I am now trying to deploy this to our AWS ECS fargate task. I am trying to run spicedb as a container in the same ECS task my application is running on. I have run the migrate head command so the migration seems to have run but it has not created the metadata table so the container is throwing errors about ERROR: relation \"metadata\" does not exist (SQLSTATE 42P01)" . Not sure if I missed something in my setup. Thanks for your help.

Hey @vidzloop_25601, if the

metadata

table isn't there it would mean the migration hasn't run properly, have you checked the

spicedb migrate

logs, does it throw anything? Maybe try turning debug/trace logging with

--logLevel debug

/

--logLevel trace

? We haven't tried fargate ourselves, but the most likely scenario you would find is that cluster dispatch may not work (SpiceDB nodes won't be able to discover other nodes). Someone tried to contribute a Fargate guide which you can find here but it may be stale: https://github.com/authzed/examples/pull/5

also if you're just doing the ECS approach to evaluate that's fine, but I'd strongly recommend against it for prod - SpiceDB's horizontal scaling mechanisms assume that the containers will be running in a k8s-like environment where each container can learn about the others and make horizontal dispatches

SpiceDB has some limited support for XDS protocol to replace kuberesolver, but we don't have production experience with it. I'm not sure if ECS supports XDS in some shape or form

ECS doesn't which is the annoying thing

it sounds like that would require a custom build then

@vroldanbet We are keen to have a chat with you or some one from AuthZed about the serverless and other hosted options. How do we go about scheduling this?

@vidzloop_25601 please schedule a call with us via https://authzed.com/call