Containers and Serverless are two key modern application development models which enterprises are widely adopting in the age of cloud computing. I almost said it like its black or white, but Containers and Serverless are so intertwined, it’s more like 51 shades of grey. The cardinal rule when you go serverless is that you never provision clusters, never pay for idle time, application is auto scalable, and high available by default. While Kubernetes is leading the Container adoption, AWS is pushing the envelope on Serverless computing to whole new level with its plethora of Serverless offerings to address every aspect of computing. There is no easy way to build serverless apps on AWS than using AWS Serverless Application Model (AWS SAM). Recently we were building a .NET Core app in visual studio using labmda, api gateway and s3 without realizing that we were using SAM underneath it. Digging deep into SAM made me realize that its doing whole lot than what it looks on the surface. Every application teams considering to go serverless on AWS might want to give SAM quick spin to understand its rapid application development capabilities. I hope to provide you quick primer on AWS SAM through this post.