Justin M. Keyes

That suggests a CLI application (e.g. `irb`) enabled [bracketed-paste mode](https://cirw.in/blog/bracketed-paste), but is not actually handling the control codes (which are added by your terminal, not SSM). I wouldn't think SSM...

/runintegrationtests

related: https://github.com/aws/aws-toolkit-vscode/issues/2430

Sounds similar to https://github.com/aws/aws-toolkit-jetbrains/issues/784 and https://github.com/aws/aws-toolkit-jetbrains/issues/642 . The plumbing for Rider might be different, but perhaps the same root cause: need explicit host instead of "localhost"? Related PR: https://github.com/aws/aws-toolkit-jetbrains/pull/1402

Are you able to export the project to a jar? That's an Eclipse feature, so if it's failing then that would prevent Lambda upload .

consider adding your upvote 👍 to the main description so it will be counted when comparing requests in this project.

Thanks for the report! Currently the Toolkit doesn't support layers in SAM templates. We might need to set up path mapping for the layer: https://github.com/aws/aws-toolkit-jetbrains/issues/3261

> you have to use a full absolute path, unfortunately, as buildArguments do not understand the vscode variables @pbarvinko this should be fixed since [1.23](https://github.com/aws/aws-toolkit-vscode/blob/master/CHANGELOG.md#1210-2021-03-17) , can you confirm? >...

Are all of these conditions true? : 1.`lib/` is a direct child of the current VSCode workspace 2. `lib/lambdas/helloworld/hello.js` exists 3. `handler()` is an **exported** function in `hello.js` (e.g. `exports.handler...

Based on your screenshot, I think you need: "lambdaHandler": "lib/lambdas/hello/hello.handler" instead of "lambdaHandler": "lib/lambdas/helloworld/hello.handler"