Is it possibile to make a condition on which client redirect to local environment or which redirect to remote environment? When development is made by two developers the local live development could be messy. Could be nice to find some solution to isolate the redirection.

every dev should have their own stage.

On my side I rename the stack in

sst.json

- slight pain but it works.

no need to do that, just pass the --stage option, this ensures you are not limited to a stage per branch.

I found information on: https://docs.serverless-stack.com/live-lambda-development#using-within-a-team I’m evaluating which approach to use between: • Different Stage: I like this way to be quick although I don’t like to have many stack related to different stage on same aws account (I use AWS organization for dev account and prod account) • Different Stage on different account: It is nice to have a dedicated account but as guide say it is cumbersome to manage. Anyone would share his experience with the second approach?

I recently cam across something called AWS Organisations - https://aws.amazon.com/organizations/ Maybe this could help for the second approach. I prefer the first approach.

I use an AWS account per dev

Yes it is nice to mange different account, you can also create an organization unit to organize account of same project, but I think it is too much to handle also every single developer, every account generate a own bill.

Yeah it's their scratch environment where they can do anything, all rolled up into the AWS org

@gio are the two developers working on different stacks in the same app? And you want some stacks to redirect to 1 dev’s machine, and the rest stacks to redirect to the other dev’s machine?

There are two developers on same stack, my initial idea was to keep only two stages (dev and prod), when starting locally sst (on dev stage) every users still continue to use remote lambdas except for the user which run sst and on demand other users that want be redirected on local instance (i didn’t spend time to understand how make this mechanism, maybe based on cognito sub?). Anyway it seems complex and could cause many problems on dev environment.

Ah I see. Yeah it’d make sense everyone have their own stage in this case.