prisma/prisma-templates

Prisma templates for major cloud providers

prisma-templates

Prisma templates for major cloud providers.

WIP.

How to connect the Prisma CLI to your custom server

• Install the Prisma CLI, e.g.: npm install -g prisma
• Run prisma init and choose Other server, then enter the URL to your server.
• When you prisma deploy a service, select the name you chose for the entry above. Your service will now be deployed to your server.

prisma-templates's Issues

support for google compute engines

Hey

This is really a very nice stuff. How much we could expect it for google compute engines or cloud functions??

Thanks in advance!

Https

It seems that this template by default configures only an http endpoint for your load balancer. That is no fun. I'm not an expert in Cloudformation, so it's hard for me to try updating it. Perhaps someone who is an expert wants to help me update the Cloudformation to use https?

Data Import with `prisma import --data ./database.zip`

I get a 504 Gateway timeout when importing a prisma database (exported from local) into the AWS Fargate server using these templates.

The command is prisma import --data ./database.zip

Is that something that should be possible with this setup?

Thanks!

Wrong security group for Fargate?

I can see that there is a Security Group called FargateContainerSecurityGroup being created. However it's never used! Instead, it seems as though https://github.com/prismagraphql/prisma-templates/blob/master/aws/fargate.yml#L294 assigns the Load Balancer SG to the Fargate service?

Multi Container Fargate Support

Multi-container fargate support had a coming soon in the readme. I wanted to open this issue to track progress/discussion around multi-container fargate support. I know very little about aws, fargate or cloud formation but will try to test some things in the coming days.

Two VPCs for one app seems overkill

Between this Fargate config and the MySQL template, hosting your own Prisma instance on AWS requires you to create two new VPCs. That seems unnecessary, especially since Amazon caps your account at 5 VPCs total per region by default.

The easiest thing would be to add some conditions in to both templates and let you specify an existing VPC and subnet. The better solution IMO is to merge the two templates and put everything into one VPC. It would also cut down on a bunch of copy and paste between the two configs.

I'm happy to handle rejigging the templates and testing it out. Just want to make sure there wasn't a rationale behind the setup.

CREATE_FAILED

Hi

I am trying to create a stack and I am getting the following error:
Unable to assume the service linked role. Please verify that the ECS service linked role exists. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException;

I am just starting to learn about Prisma and AWS so any help would be appreciated

Thanks

Found the solution, just run
aws iam create-service-linked-role --aws-service-name ecs.amazonaws.com

503 Service Temporarily Unavailable when using Fargate

So I keep following all the instructions here ... it gets created successfully, but whenever I access the externalUrl I get a 503 service temp unavail error.

I'm using an already existing Postgres database hosted on AWS, instead of using the templates. The logs show a connection error with the db. Is there a reason you guys haven't created a aws/postgres.yml version yet? I'm not too familiar with Fargate (yet), so any help with how to connect Prisma to my existing db while using Fargate would be very appreciated.

Thanks in advance for the help!

Btw - would be really great if you guys (the Prisma team) could create a more simple way to deploy Prisma Server on AWS. Maybe could add something to the cli?

AWS Fargate template fails with prisma v1.16+

Error

You receive a error during the iam role creation of 400, cannot create iam role for ecs.

Steps to recreate

Go through the tutorial @ https://www.prisma.io/docs/1.8/tutorials/deploy-prisma-servers/aws-fargate-joofei3ahd#2.-deploying-a-prisma-server-to-fargate

There is currently no documentation updates for this deployment for versions past v1.8

Possible Solutions

Update the fargate.yml file to correctly associate iam roles via security group
or
Make note on the fargate yml file or prisma template readme on what version the template no longer works. As of right now, it only mentiones version 1.6 as being the earliest acceptable version. 1.19 is listed as an acceptable version option inside of the fargate template.

Management API Authentication settings not working

What I faced

I set managementApiSecret, however I got the error below.

Warning: Management API authentication is disabled. To protect your management server you should provide one (not both) of the environment variables 'CLUSTER_PUBLIC_KEY' (asymmetric, deprecated soon) or 'PRISMA_MANAGEMENT_API_JWT_SECRET' (symmetric JWT).

And I tried to deploy prisma service without secret key, and deployment succeeded.

Possible Causes

The management api secret is loaded from PRISMA_MANAGEMENT_API_JWT_SECRET .

https://github.com/prismagraphql/prisma/blob/b58e9f7c8bd58619f7df343dfea83590f5216ca3/server/libs/prisma-config/src/main/scala/com/prisma/config/ConfigLoader.scala#L67

but cloud formation template sets secret key as MANAGEMENT_API_SECRET .

https://github.com/prismagraphql/prisma-templates/blob/master/aws/fargate.yml#L274

Vulnerability: Management API Security is Disabled

There is currently a mistake in the template that is causing managementApiSecurity to be disabled. The fix is contained in this pull request #18