I remember a while back there was an issue with setting log retention values in defaultFunctionProps (or maybe in other ways too) i.e.

app.setDefaultFunctionProps({
  logRetention: logs.RetentionDays.ONE_WEEK,
  ..
})

Since then we haven't tried setting the log retention but I just tried it again on v0.53.4 and I still see an error:

The following resource(s) failed to create: [omwGetAllResourceConfigsLogRetention87CC9E7D, (and many others)]. 

Received response status [FAILED] from custom resource. Message returned: A conflicting operation is currently in progress against this resource. Please try again

Is this a known issue and is there a way around it?

Are there any plans for an integration test environment? Would be great to support a development flow using an integrated environment rather than unit tests. Would be a game-changer. I'm sure it could be put together with existing tools, but to have it out of the box 🕺

Sst is really nice for me, but I'm wondering if there are any plans to support other clouds too? Since it works specifically with Cloudformation templates.

Can someone take a look at: https://github.com/serverless-stack/serverless-stack/pull/1114 We’re having to have a floating change in our sst.jsons since our personal dev envs are in different regions than the upstream one

I'm interested in how people might approach this. We are using Thundra APM tracing via in a provided lambda layer. This also makes available the @thundra/core library. We would like to use the thundra object to do some custom tagging in the code and since it's in the layer the lambda doesn't need to include this as a dependency. However, it is needed for building the lambda in Seed. Typically you'd add the library to devDependencies. However, since We have NODE_ENV set to production for the lambda the devDependencies are excluded from the build. So, at the moment we have it as a dependency to make the build in Seed succeed. How can we allow the build to succeed without bundling or installing the library? This feels like a newbie question, so maybe there's something obvious/simple I'm missing!

If I don’t pass anything on

environment

, should it read it from the

.env

file defined in SST?

Looks like the ENV-VARS with

registerSiteEnvironment

are defined AFTER building the app with

npm run build

… why is that?

Cloud formation expects it to exists, so maybe not so much sst but I was able to deploy by setting

accessLog

to false. I might have missed something, but accessLogs were not being created by default before. This is an easy work around because I was already managing the access log for the Api outside of the SST's construct.

Is there a way to find SST created resources across different regions? I am looking to spin down some resources occurring cost that I don’t believe I am using anymore.

I know @Mischa Spiegelmock was looking for ESM support not sure who else - I personally want this as well. Turns out I was able to get it working with some fairly minimal changes to SST. We'd likely require a

bundle.esm

flag to be turned on to true and from there I need to package aws-lambda-ric in 2 different modes both for esm and cjs. The rest of SST can be left as is for now. Anyone else looking for ESM support?

Hey all, I'm new to SST, looks awesome! We're thinking of using it on our next project as we want to use CDK but it feels like quite a leap from the comfort zone that is Serverless Framework 😉 Also the local debugging feature looks amazing! I guess my only concerns are it's not yet "production ready" (though I imagine will probably be fine!) and good ol'vendor lock-in. Obviously it's built on CDK but I'm wondering - is it possible to "eject" from SST (i.e. revert to pure CDK somehow) if SST turns out to not be a fit for us down the line or if (in the unlikely event) SST was disbanded?

Just created an issue, should be a fairly quick fix: https://github.com/serverless-stack/serverless-stack/issues/1151 Perhaps I am missing something, but this is causing me some testing headaches.

Anybody using sst in a turborepo monorepo, where they're also leveraging Next.js sites (as adjacent packages) with

NextjsSite

? Would

sst.json

live at the repo root?

How the lambda bundle process works? What is pushed to s3 as our lambda? What dependencies?

Seeing error running 0.54.2

@thdxr I noticed that when the connection drops and the listener get’s connected again the functions don’t work properly, it appears like the functions don’t exist

any plans to allow deployment of a single function to a stage via the CLI?

why is this:

this.addOutputs({
      "ApiEndpoint": "https://"+ api.restApi.restApiId + "-" + process.env.VPC_ENDPOINT + ".execute-api." + this.region + ".<http://amazonaws.com/|amazonaws.com/>" + this.stage
    });

resulting in more than 1 output?

Outputs:
    apiApiEndpoint71625CD3: https://<rest-api-id>.<http://execute-api.us-east-1.amazonaws.com/stage/|execute-api.us-east-1.amazonaws.com/stage/>
    ApiEndpoint: https://<rest-api-id>-<my-vpc-endpoint>.<http://execute-api.us-east-1.amazonaws.com/stage|execute-api.us-east-1.amazonaws.com/stage>

I don't know what is creating

apiApiEndpoint71625CD3

Hey guys, I’m using

DockerImageFunction

from CDK. How can I give it permissions to write into Dynamo table? This is really easy with SST Function construct, but not sure how to do it with CDK constructs.

Why am I getting this in my console output

Warning: Ignoring extra certs from `/etc/pki/tls/certs/ca-bundle.crt`, load failed: error:02001002:system library:fopen:No such file or directory

Does anyone have an example of conditionally created resources laying around? Something like creating an RDS DB or VPC in stage/prod, but not development

Just wanted to call attention to this, in case the SST guys hadn't seen: https://aws.amazon.com/blogs/developer/increasing-development-speed-with-cdk-watch/ SST has several features not included, but it seems AWS is starting to think along these lines in a small way.

Getting some odd behavior from SST

Api

today, wondering if I am alone... https://github.com/serverless-stack/serverless-stack/issues/1163

👋 My colleague is having problems with

pdfkit

library and esbuild - has anyone had similar problems and solution for this? Thanks!

`Error: ENOENT: no such file or directory, open '/Users/.../pms-integrations-v2/services/hsk/.build/src/cron/data.trie'

https://github.com/foliojs/pdfkit/issues/990 https://stackoverflow.com/questions/67234055/pdfkit-on-js-ts-lambda-with-cdk-error-enoent-no-such-file-or-directory-open

would be happy to get some sort of feedback, any feedback, on these proposed changes: • https://github.com/serverless-stack/serverless-stack/pull/1154 • https://github.com/serverless-stack/serverless-stack/pull/1156 even if it’s “stop opening these stupid PRs”

Sharing this concern here also, due this might be interesting for SST use-cases too.

I'd like to be able to specify different esbuild configuration per function. This is so we can apply a 3rd party esbuild plugin (Thundra) differently depending on the function. At present, the bundle.plugins property takes an import path. This means I need a different esbuild.js for each function. I'm wondering if there's a better way to pass an array of configured esbuild plugin objects to the bundle.plugin property

Hey guys, I’m using

DockerImageFunction

construct from CDK into my SST stack. How can I test this locally? Can I run the docker image locally? and how I can connect to Dynamo and others? is that possible from LOCAL?

I'm trying to run

sst deploy

and the process hangs at the point where it bundles the first function in the stack. Setting up

sst deploy

within a debug launch config I can see that it gets to this point in Functions.js:

else {
            const bundled = core_2.Runtime.Handler.bundle({
                id: logicalId,
                root: root.appPath,
                handler: handler,
                runtime: runtime.toString(),
                srcPath: srcPath,
                bundle: props.bundle,
            });

We've tried this on a couple of different machines, one Windows and one Mac with the same result. I can run

sst start

successfully so it seems like a bundling problem, which the point of hanging would imply too. sst-debug.log looks like this when running deploy from a debugger - output is pratically identical doing a straight

sst deploy

(last line is a console log in the stack)

[2021-12-23T12:40:17.939] [DEBUG] default - SST: 0.54.4
[2021-12-23T12:40:17.942] [DEBUG] default - CDK: 1.132.0
[2021-12-23T12:40:17.945] [INFO] default - Using stage: pjn-dev
[2021-12-23T12:40:17.948] [INFO] default - [90mPreparing your SST app[39m
[2021-12-23T12:40:18.181] [DEBUG] core - synth {
  output: '.build/cdk.out',
  app: 'node .build/run.js',
  rollback: true,
  roleArn: undefined,
  verbose: 0,
  noColor: false
}
[2021-12-23T12:40:18.392] [TRACE] cdk - Debugger attached.

[2021-12-23T12:40:20.742] [TRACE] cdk - Debugger attached.

[2021-12-23T12:40:42.010] [TRACE] cdk - Running locally? false

We're running sst v0.54.4. Any thoughts?