Curious, any plan to allow SST Topic construct to also accept subscriptions props like

filterPolicy

? Also along with it, support to add other kind of subscribers like SQS... I was hoping to migrate serverless framework pub/sub service with several filter policies to SST.

I have been using the API construct to define an api with two different types of authentication. For example, some endpoints have IAM, others require no auth. Is the API construct meant to enable this via

defaultAuthorizationType

?

I’m getting the following error

===============
 Deploying app
===============

Preparing your SST app
Transpiling source
Linting source
Deploying stacks

Error: The specified permissions are not supported.

Following this tutorial: https://serverless-stack.com/examples/how-to-add-cognito-authentication-to-a-serverless-api.html

Hey I just started testing

sst.Api

and one thing that I noticed was different is that I get a notice of the following for each route:

Transpiling Lambda code...
No package.json found in services/mobile-api/
No package.json found in services/mobile-api/
Debug session started. Listening for requests...

I do not see this while defining

sst.Function

s. Note: I use a single package.json in my root folder and many services below this, like

./services/a, ./services/b, ./services/c

Another question on the

Api

construct: I'm defining my full application spread out in multiple services, each with their own

sst-stack.js

file that is replacing my old

serverless.yml

files. I also have some common functions they use. In order to have all my routes use the same custom domain, it seems it would be smart to use a single Api and have each service add their routes to it. I didn't see any support for adding to the construct outside the constructor but wanted to check - is this supported? Does it sound like a reasonable idea? Does this move beyond your plans for SST and would be better handled in native CDK?

I am trying to access my region per the docs here: https://docs.serverless-stack.com/installation#project-config But I am running into this error Property 'region' does not exist on type 'IConstruct'. 23 REGION: this.node.root.region

which results in an error

TypeError: Cannot destructure property 'sqsQueue' of 'props' as it is undefined.
    at new Queue (/Users/sethgeoghegan/dev/signup-and-run/node_modules/@serverless-stack/resources/src/Queue.ts:23:7)

Is that to prevent too much deviation from how api gateway routes in production?

any plans to add removal policy option to sst.Table?

Is there any reason why you can’t auto reload on when this happens?

@Jay How is the way to go about using Python with SST? Is that possible? Or is SST more for JS?

Will you guys be adding a single page app construct?

How do you specify the JWT scope for a single route?

@Frank https://github.com/serverless-stack/serverless-stack/discussions/180 <-- is this on the roadmap anytime soon?

I saw the 0.9.12 lazily add subscribers addition 🎉. This would be a cool addition to the api construct. I know you could access the cdk HttpApi and add additional routes that way, but lazily adding routes the SST way would be a great addition to sst.Api!

seems like

this

isn't accepted as a construct

Is there any way to specify additional files to include when deploying? I need to make sure that

node_modules/.prisma

is zipped up

SST is not removing Cognito user pools on “sst remove” if there are users in the pool, is this expected behaviour?

When setting up custom domains with the API construct, is there a preferred method to handle subdomains that already exist?

Also doing my deploys/destroy outside of github actions would make sense

Hi everyone, quick question regarding hybrid apps on seed.run. I’m currently migrating my serverless framework (built using serverless-stack v3) to SST. I created a new service on seed for the SST service and have existing seed services for the serverless.yml services. The deploy succeeds but the SST service is being deployed to a different endpoint (I use

CfnOutput

to output the endpoint and see it in the logs) How do I get the SST service to deploy to the same endpoint as the serverless.yml services? The same one that seed.run returns after building. Thank you for your help!

hm I guess I only need this for non-local development where this isn't an issue

Is it possible to setup a custom authoriser for the API construct?

Is there a roadmap for the addition of REST APIs in SST?

I started doing the latter as I needed it for my system: https://github.com/ironbay/serverless-stack/commit/7c4403b69973caca3f74b1d6f747e70205066635#diff-afd94e9d7ffa6f7ab02a2[…]7428b7196d7c6e4f3ba5fffdR31

I was in contact with @Jay before (more than a year ago) via email regarding monorepo project structure with Serverless. According to the guide, "SST supports monorepo setups automatically". I was wondering how a monorepo setup looks like in SST. Is there an example repo?

Hello There’s some features either missing or not yet covered in the docs, e.g. how to configure the Lambda onError target to an SQS as DLQ; although it is possible to use actual CDK in this same config, so that may cover it; But was wondering if someone here can point me in the right direction

okay, I see that sst.Function makes sense, but wouldn’t it be possible to just add the debug stack to my existing cdk app? I don’t want to change every stack for SST

Is there a way to setup vscode to debug a lambda? Even if it times out in 30s (api gateway / appsync).

Hi all, if I'm correct using Lambda Layers isn't support yet by sst?