Also seems like it used Port 60000 as the default port to serve Prisma on, I don’t know if I will need to change that in the future but just trying to get it running for now. Thanks in advance!

I’m running a prisma server connected to postgres on fargate using the cf template. I don’t think I had to modify the fargate.yml at all since you can change the inputs once you upload the file to cf.

@carlo the only diffs are on line 35 and line 46- https://www.diffchecker.com/MZVt39vv

have you tried uploading the original yaml file? you should be able to change the dbconnector there

did you have to change any of the Env Vars? I noticed that the env vars didn’t have spaces in between the characters when it was generated while running the cloudformation stack so I did edit those. Do you just have the

PRISMA_CONFIG

with a bunch of vars in it?

yes, don’t edit the env vars after cf creates your task definition

I have not tried uploading the original

the formatting gets lost when you do

ok, it just seemed incorrect as it was something like

port: 60000managementApiSecret:

yea i haven’t found a way to set multiline env vars through fargate, the only option i see is through cf

do you think I should create a whole new stack or just swap the file in my existing stack?

i’m not too familiar with cf so i would just start with a new stack

ok cool I’ll try that

1.24

ok I’ll try that version too, thanks a lot for your help btw! 🙂

no problem!