Running SST in dev mode

[@ruchernchong]

Thank you for this! I never knew I should not use dev and deploy for the same stage. It ended up tearing down and spinning up my CloudFront (disabled for DEV env now) which takes AGES!

[@JokersLaught]

Thanks for the video. I’d like to see more advanced videos or building full example apps etc. 🙌🏼

[@jay_air]

Yup working on it!

[@scvramella]

Thanks Jay! One suggestion that I have is creating a golden sample for enterprise setups. As of now, SST has a great guide on how to set up an AWS account (Identity Center, SSO, etc.) and monorepos aggregating multiple services. That is great for most use cases, but many enterprise clients run their services on a multi-account setup (one account per team or service), and separate Github repos for each service. If you could document what is SST's recommended approach to those requirements, it would be great. A suggested scenario: typical e-commerce app with 2-3 separate services (nothing fancy on business code, it's just to have a basic structure), each deployed to a separate account, on their own Github repo, an account for shared resources (e.g. event bridge bus), sharing common code, etc. I think it'll help us developers to advocate SST even more internally at our companies, that tend to be more rigid in terms of how's everything structured. WDYT?

[@jay_air]

@@scvramella Yeah we want to cover more setups. So you have separate services that are deployed to separate accounts and come from their own repos? In this case this would be separate SST apps right?

[@scvramella]

@ Yeah, I had in mind separate SST apps, each representing an independent service. In the e-commerce example that I gave, you could have 2 SST apps - Orders and Deliveries. Each would have their own Github, and deploy to their own AWS accounts. I’m curious how you recommend that kind of setup, how to share infra (e.g. both services can share an event bus, or a DDB table, etc.), how to share common code. The e-commerce is just an hypothetical scenario, I’m more interested in the concept.

[@kambaalayashwanth123]

Thank you for this info, I faced this running deploy and dev on the same stage, wired behaviour

[@crampssss]

Hi @ 4:49 you mentioned that with `sst dev` the resources created would be teared down. When exactly does this happen? Cause when I exit out of `sst dev`, the resources I created are still there. There's no clean up happening.

[@alejandrombc]

How do I use the bastion to use another resources like elasticache?, it proxy all traffic to it?, or just specific ports? Is there an option to do the same with v2? (Without using client vpn 😢)

[@jay_air]

It should work for other resources too. Nah this is for v3 only.

[@alejandrombc]

​@@jay_air Thank you!. And how would you implement this for v2? (not necessarly with sst itself, but with normal aws resources to achieve the same behavior)

[@jay_air]

@@alejandrombc Well for the infrastructure you'd need an EC2 instance with a bastion host on it. But the CLI needs to create a network interface on the local machine to forward traffic there.

[@Boha362]

Wait. What about postgres?

[@jay_air]

In this example (and by default) Postgres is deployed even in dev mode. You can change this by passing in a `dev` prop. I might cover that setup separately.