Any ideas?
# orm-help
h
Any ideas?
If it helps at all, I have the database successfully running on aurora
n
do your Prisma logs reveal any problem?
503, sounds like you're not talking to the right endpoint though, or your server is not accessible from outside or something like that
h
I think that's pretty close to the mark. I'm following the tutorial here: https://blog.graph.cool/how-to-deploy-a-prisma-cluster-to-aws-fargate-using-docker-cloudformation-293aa8727b89
using the prisma template for CloudFormation
but my prisma version is 1.8
n
ahh ok
h
and there is a discrepancy in the template vs the walk-through
walk-through mentions public RSA, but the template has
managementApiSecret
I can imagine that your observations have to do with the discrepancies between the tutorial and the template
h
Kinda thinking so, too... and, probably because of that, I was getting 'access denied' when activated ELB logging
lemme give this new one a shot -- thanks! 😄
n
hmm I don't know about the elb logs though
ok sure! 🙂 Hope this gets you through, but let me hear otherwise
h
will do!
👌 1
Copy code
Creating stage default for service default !

ERROR: GraphQL Error (Code: 503)

{
  "error": "<html>\r\n<head><title>503 Service Temporarily Unavailable</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>503 Service Temporarily Unavailable</h1></center>\r\n</body>\r\n</html>\r\n",
  "status": 503
}
Does the load balancer just take a while to come available?
n
can you navigate to your
<http://server-endpoint.com/management|server-endpoint.com/management>
?
is that up?
h
that's the ecs stack's public URL, correct? No, it's the same error
n
well, the CLI is running against that endpoint
just to try, does
<http://server-endpoint.com/cluster|server-endpoint.com/cluster>
work?
h
same thing - 503
n
ok this feels like a network misconfiguration, but I am not savvy enough with EC2 to say more 😛
h
no worries! I think that I'll give it a second -- after my initial query about 503 response above, the response eventually changed to a 504 gateway timeout error
so i think there may be some waiting that needs to happen for that URL
n
ah one thing, can you access the docker logs for the prisma container?
that might reveal a connection error or something else that can point in the right direction
h
👌