Serverless Stack

I’m wondering about initially just migrating the functions and then when I have more time think through an eventual full-migration strategy.

Hi <@U01REA1NTM1>, SST is built on top AWS CDK, it can’t deploy resources from a `serverless.yml` file

`sst deploy`  will only deploy your sst-defined stack so you need to use a combination with `sls deploy`  as well. I did it like that, moving definition of a few functions at a time, and now I have ~80% of my functions and infra in SST

Doing it like that also mean that you are not rushing headlong into a decision to do one way or the other. You're able to take SST out for a spin, and can decide for yourself if it's a good match or now.

IMHO it's awesome however! :wink:

That’s great. So in theory I can deploy everything (once for serverless, and then once for sst) and then sst-start will just setup the lambda to local live dev proxy?

One thing to remember. After you're done with `sst start` , you need to run `sst deploy` if you want to redirect execution back to AWS. `start` will redirect traffic to your local machine and `deploy` will set it back.

So don't run `sst start` with your production account!

I’m currently using seed to deploy my prod stage

That does make we wonder though... will seed know to deploy both serverless and sst?

You’d need to add 2 services on Seed, one for `serverless.yml` and one for `sst.json`

Is there a reason I couldn’t eventually port my dynamo database over as well?

Just noticed in the guide it said it wasn’t possible. Maybe I misunderstood. 

You have to create a new Table, and migrate the content over.

You can’t move a Table from existing CloudFormation stack created by Serverlss Framework to a new CloudFormation stack created by SST