Skip to content

Instantly share code, notes, and snippets.

@ranman
Last active November 11, 2017 16:36
Show Gist options
  • Select an option

  • Save ranman/1a43a950b476888ccb10a6b51db01411 to your computer and use it in GitHub Desktop.

Select an option

Save ranman/1a43a950b476888ccb10a6b51db01411 to your computer and use it in GitHub Desktop.

Hi Chris + Ajay,

Just wanted to share 3 quick reasons why I still don’t use SAM and why it’s not a self-contained solution (for me).

  1. Unable to embed my code directly in the template.

CloudFormation Example:

HitWebHookFunction:
  Type: AWS::Lambda::Function
  Properties:
    Handler: lambda_function.lambda_handler
    Code:
      ZipFile: !Sub | CODE GOES RIGHT HERE

SAM Example:

HitWebHookFunction:
  Type: AWS::Serverless:Function
  Properties:
    CodeURI: LINK TO S3 BUCKET GOES HERE

The key issues with the SAM approach are that I have to now have separate s3 buckets and separate deployments for every region I want this template to run in. It makes a simple task much harder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment