AWS re:Invent 2019: [REPEAT 1] CI/CD for serverless applications (SVS336-R1)

As developers have migrated to building serverless applications, they often wonder what has to change about their CI/CD workflows. The answer, not much. In this session, we break down how to think about CI/CD when building with serverless technologies such AWS Lambda and Amazon API Gateway. We cover using technologies like AWS Serverless Application Model (AWS SAM) to build CI/CD pipelines for serverless applications. We also demonstrate how you can take advantage of technologies like canary deployments, pre-traffic hooks, post-traffic hooks, and alerts to perform safe deployments of your serverless applications.

[@niloy369]

"Production doesn't look anything like staging" - it's rare to hear talks like that and these things are relatable

[@kopias]

Oh man, dude is killing it. Really funny and insightful! Thank you!

[@ThubaMamba]

Such amazing energy. Thank you for the talk.

[@BilalAhmed-nt9gi]

2:47 and already thumbs up this dude

[@letme4u]

wonderful talk

[@RafaganAbreu]

Amazing and funny presentation!

[@shenth27]

Guy is awesome.

[@MOHANRAJ-tc2rh]

I like this guy

[@joggyjames]

i love this guy

[@Cs-gf3xe]

29:09 I'm curious about how to "Mocked/stubbed integration tests" with deployed lambda. Anybody knows good library or framework to do it? Thanks!!

[@jean-marcvanie6291]

Thank you so much. I have a problem. Given a serverless application built with the AWS console, is it possible to retrieve the Terraform or SAM IAC and then build my infrastructure as code in an other AWS account?

[@EricJohnson-lr2tl]

Until now, this was not. But take a look at the Application Composer.

[@yangzhihong521]

very good

[@onedayoneday1]

What is the difference between CDK and SAM?

[@EricJohnson-lr2tl]

They are both Infrastructure as Code frameworks. SAM uses YAML as a language while CDK uses languages like Python, Java, Typescript, etc. Both output to CloudFormation in the end.