Any guide for AWS AppSync GraphQL resolvers using multiple data sources (databases + 3rd party apis) ? I’m making a serverless ecommerce solution wherein each microservice may have its own database like PIM on Aurora PostgreSQL, Orders on DynamoDB, Payments on Document DB or Dynamo

guys, I’m starting to use SSM to handle my secrets on a side-project I’ve been working on and would like to hear what would be the best practice between: • let the secrets only on SSM and get them on my code whenever I need; • add the secrets to the Lambdas on a release step on my CI; I think the first step would be more secure, even though it might do lots of calls to SSM during an execution of a Lambda (which I don’t know if it’s performative or not). If anyone has another way to use SSM I’d also like to hear it :)

Hello, I've got a question regarding SST working side-by-side with existing SLS resources. So we want to release our current SST infrastructure to replace SLS, but we want to keep some of the existing resources untouched (like DynamoDB as an example) but still be able to update or edit some stuff if needed. What would be the best approach for this? Since in Dev we want to have everything deployed fresh via SST and be separated by stages, but in Prod we want to keep some of the existing stuff as it is but still have it available in our SST code. Is there any "best practice" approach to achieve this in one code base? Or is it literally a matter of

if

statements to check stage and region (for example). I've already implemented some CDK

.fromArn

(example) methods which import existing resources, but I'm curious what would be the best approach to this. Thanks

Error in the guide: https://docs.serverless-stack.com/constructs/Script#params. The last sentence needs to add .params:

Then in the function, 

event*.params*.key

 would give you 

Value

.

Is there a repo somewhere with all the code of a finished app from the guide? To see what the final output looks like?

I just created severless stack project by running this command npx create-serverless-stack@latest notes after I run this command npx sst start I did not change any code even then I am getting this error shown in the image plz guide ma why it is happening

Hey everyone! I find that a significant source of confusion around

sst

, when I’ve introduced it to others, is the lack of clarity between Serverless-Stack, the platform/framework (I’ll refer to as

sst

), and the Serverless-Stack Guides, which I assume pre-dates sst. It’s jarring because the branding between SST and the guides are, presumably, one in the same. But they seem to be positioned as guides for building sst apps, though there’s a large number of non-sst articles. For someone without extensive Serverless Framework experience, and a bit of sst experience, it can be very confusing when building a new stack. It seems odd that there are non sst articles that are seemingly promoted as sst guides, but most importantly, there’s almost no context to what the guides are promoting. The recent reorganization of the articles help, but it’s still confusing. I bring this up because I’m curious if this has been discussed / mentioned, is it being actively considered, and could you use help with this? I’m a big fan of sst, and I would be happy to apply my experience in branding, optimizing user-experience, etc. But I want to know if this resonates with anyone else, whether or not I can be of any help, and whether I’m missing any information. Thanks all!

I want to use Sequelize instead of dynamo DB in the serverless stack. I explore google but did not find any article which explain it. Please guide me ho to implement it.

Would it make sense to have the listed the AWS services used on the Serverless Examples? I think it would be quite interesting for newcomers as AWS requires some time and patience to figure out what services to use and what not - and the examples could help with that pretty well, by giving practical examples to explore and "just work" out of the box.

I am trying to create a user but getting an error shown in the image. I am following the notes app tutorial. Can someone guide me on what I am doing wrong?

@Frank @Gregory Houtteman Dear Sir, this time I am getting the following error Authenticating with User Pool Getting temporary credentials Making API request getaddrinfo ENOTFOUND sgkvf7rz4h.execute-api.us-east-1.amazonaws.comsrc Can you guide me on why it's happening

I am trying to find the solution to this error from google but unfortunately could not. Please help.

you can't have 2 endpoints that look the same. In this case

PATCH /{user_id}

is the same as

PATCH /${_id}

As in, api gateway uses those names to map the path parameters, but when you have 2 endpoints with the path parameter in the same location in the url it won't know which lambda to pick

I would appreciate a guide that lightly touches on handling different levels of users. For example admin, superuser, customer. I could see how this is maybe our of scope

Hi guys, There seems to be a scrollbar issue in the docs. I noticed it here: https://docs.serverless-stack.com/constructs/Auth It scroll back up when you try to scroll it down. macOS 12.2.1 Chrome 99.0.4844.51 (Official Build) (x86_64)

Hi All, I started working on the guide and installed the first step

npx create-serverless-stack@latest notes

and cd into notes and did Npm run stack . I am getting the following error

Failed to parse generated manifest.json [Error: ENOENT: no such file or directory, open 'C:\whatsapp\notes\node_modules\@serverless-stack\cli\assets\debug-stack\cdk.out\manifest.json'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\whatsapp\\notes\\node_modules\\@serverless-stack\\cli\\assets\\debug-stack\\cdk.out\\manifest.json'
}
Deploying stacks
Failed to parse generated manifest.json [Error: ENOENT: no such file or directory, open 'C:\whatsapp\notes\node_modules\@serverless-stack\cli\assets\debug-stack\cdk.out\manifest.json'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\whatsapp\\notes\\node_modules\\@serverless-stack\\cli\\assets\\debug-stack\\cdk.out\\manifest.json'
}

Failed to deploy the debug stack

Followed up in #help https://serverless-stack.slack.com/archives/C01JG3B20RY/p1647881635954779

How do I query a table using global Indexes?

@Frank there is an issue in the sst ebook on page 143... the sample favicon does not load in the pdf:

Right-click to download the following image. Or head over to this link to download it — [{{
'../../assets/scratch-icon.png' | absolute_url }}]({{ '../../assets/scratch-icon.png' | absolute_url }})

Hello! I've a stack deployed using the Serverless Framework, which I'm looking to migrate to Serverless Stack in its entirety (ie, move the resource/output definitions to SST). I couldn't find anything on the website to indicate if this is possible; is it? If so, is there a guide/post I could peruse?

Hiya. I've recently been working off this guide to get JWT auth working with my stack, and had some troubles getting the front-end to communicate with the modified api. It would've been great to have the necessary front-end modifications as part of that guide, as tracking down the info elsewhere was a nightmare. In the end it was as simple as passing `headers.Authorization: `Bearer ${(await Auth.currentSession()).getIdToken().getJwtToken()}`` with the

<http://API.post|API.post>

(as otherwise configured in the main guide). It looks like you can also remove the

identityPoolId

from

Amplify.configure.Auth

. It's the sort of feature you'd expect amplify to make easy, but the issue hasn't had any movement in a while https://github.com/aws-amplify/amplify-cli/issues/3390, which makes workarounds tough to figure out.

Seems

fields: {
        userId: sst.TableFieldType.STRING,
        noteId: sst.TableFieldType.STRING,
      },

TableFieldType doesn't seem to exist anymore?

Is there a Typescript edition of the guide available or in the works? I'm new to SST so something as simple as

constructor(scope: <http://sst.App|sst.App>, id: string, props?: sst.StackProps)

took me a little bit of searching to find. I found the answer and learned so that's great but having the information in the same location as the learning resource helps to keep focus with less context switching.

Is there any way to support migration files written in TS instead of JS ?

sneak peak of upcoming example 👀

Sort of random question - in the Guide, as it demonstrates extending the Stack construct, is appears that each stack module instantiation from index.js includes an "id" property in props i.e "auth", "api", etc. but inside the stack definition, rather than use that passed id property, it is hardcoded again in the individual SST calls i.e. this.api = new sst.Api(this, "api", {}) and this.auth = new sst.Auth(this, "auth", {}) Is there a reason that the id property isn't used? Am I missing a convention or something?

Hey guys, I've been looking though the site and I swear there was a whole section about how best to deal with secrets access and lambdas... Like an "easiest, better, best" thing. Am I going crazy?

Cognito + GitHub OAuth ⚡️

Gonna do an SST deep dive at my company. Because Serverless is new to them, SLS and SST are hard to disambiguate. I pointed one to the Guide, which actually made the confusion worse, since it starts SST and evolves SLS. I have a hunch reality went the other direction, and Guide is catching up. My recommendation: make it crystal clear the "situation". Eg, Guide is catching up, we're keeping the value docs for posterity mid transition, tread with salt. Easiest solution: just when SLS starts, have a

warning

block/page that just says explicitly the situation: this guide is about SST, we're moving away from SLS, once upon a time blah blah, keeping this for value (it is valuable)

New example published👇🏻 https://serverless-stack.com/examples/how-to-add-google-login-to-your-cognito-user-pool.html