lefnire / sst-aurorav2 Goto Github PK

Start with sst/sst#2506

This sets up Aurora Serverless v2. Because v2 costs $40/m minimum per cluster, it provides 3 possible options:

This assumes you have a local Postgres installation (eg Docker). It will skip creating the common stack resources (VPC, RDS, etc)

npm run dev

Nice & simple. Free.

This creates a common stack for all development environments. A single common stack which is shared across everything that's not literally named prod. So staging|dev|test|user1|user2|etc will all be piggy-backing on the same VPC and Aurora Serverless v2 Cluster. To differentiate between the environments, a separately-named dbName (which is myapp${stage} by default) is used. This means you incure a minimum of $40/m for all environments.

npm run deploy:common
npm run deploy:staging
# npm run dev

When it's show-time, you launch a single common stack, which is only ever used by prod (ie it's not actually a common stack, just consistency).

npx sst deploy --stage commonprod
npx sst deploy --stage common

Now it's $80/m minimum. $40 for prod, $40 for everything else.

On local-only you can access your DB the usual way. For RDS DBs (staging, prod, etc) you'll need either (a) SSM (I haven't figured this out yet, could someone chime in?); (b) ClientVPN or (c) Bastion host. ClientVPN is a no-go. It costs $5/day even when turned off, and is freakishly difficult to use. I know from experience. So bastion host it is. To set this up:

1. Enter your public IP in sst.config.ts.
2. Create a keypair in AWS EC2 console. Download for use later. Copy its name in sst.config.ts
3. Ask GPT how to "how do I SSH tunnel with DataGrip" or whatever DB client you use.
4. When you're done, stop your instance in EC2 console for better security; turn it on again later. In fact, you might want to set myIp = null in sst.config.ts and re-deploy, to delete the bastion host; you can spin it up again later easily.