sst: console: autodeploy logs take a long time to stream or don't come through at all
Two deploy examples:
l0dd1h1esbohravcn2arjbw9u1kzteihkarv2h6kdm6p51rw
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 22 (12 by maintainers)
Hi @jayair @fwang thanks for getting back. I noticed a more detailed error message in the console saying SST didn’t have permission to create resources:
We don't have the permissions to create the necessary resources in your AWS account. You can fix this by creating these manually and trying again.So I did some digging in CloudFormation and seems like the issue is due to my AWS Lambda Concurrent Executions applied account-level quota being set to 10 instead of the default 1000. Weird and not sure why it’s been set so low but will try to increase this quota and see if it solves the problem.
You can view the logs directly in the AWS Console by going to CodeBuild in
us-east-1.For me the issue was with trying to build a Remix project using Vite. Because I had a monorepo structure, the build command did not install the dependencies that sub-projects had defined. Configuring workspaces in
package.jsonresolved the issue.