sst start is throwing an error but I can see debug resources are created.

npx create-serverless-stack@latest sst-lambda-validation

is what I used to create the project. and and then I simply ran

sst deploy

@Frank, Tagging you for visibility. It turns out that the issue that I was facing was caused by aws named profiles. I use a simple script in my .zshrc that helps me switch aws profile temporarily in the current terminal instance.

awsc () {
  export AWS_DEFAULT_PROFILE=$(grep -oE "(\[).+(\])" ~/.aws/credentials | tr -d '[]' | peco)
}

and on running

sst start

my infrastructure is deployed in the correct account. but for some reason. the polling that happens for checking stack status uses aws default profile and hence it didn't display deployment stats and throws errors in sst start. My question is: What is the easiest way of pointing an aws named profile to sst?