Another question, maybe for somebody who is intima...
# orm-help
h
Another question, maybe for somebody who is intimately familiar with AWS CloudFormation.... Using the Prisma-provided templates for spinning up database and fargate stacks, each of these templates automatically generates its own VPC to run in. Is it worth it to run your database and your prisma server in the same VPC and, if so, how does one hack the template to allow this?
the thinking here is to have a VPC for the staging environment, and a VPC for production, and run everything pertinent to those environments in their respective VPCs
d
It might be a good idea to have both in the same VPC, as it would (more easily) allow you to not expose the DB with a public IP, reducing potential attack surface. You unify the templates to achieve that, or (my recommended approach) is to make the VPC you want to deploy to a parameter for either one of the templates.
h
Thanks @dpetrick! That's kinda what I was thinking, too... and also that it should simplify the provisioning of other resources if there aren't a dozen VPCs floating around
One more question -- the VPCs provisioned in each template have different cidr blocks -- you see any problem with unifying those?
d
I see no issue in unifying the blocks.
h
👍