This is a sample template for look-ma-no-server


Setup process

Creating the project and its dependencies

In this example we use DotNet Core CLI to bundle our project with its dependencies:

dotnet publish src/HelloWorld

Local development

Invoking function locally through local API Gateway

sam local start-api

SAM Local is used to emulate both Lambda and API Gateway locally and uses our template.yaml to understand how to bootstrap this environment (runtime, where the source code is, etc.) - The following excerpt is what the CLI will read in order to initialize an API and its routes:

        Type: Api # More info about API Event Source:
            Path: /hello
            Method: get

If the previous command run successfully you should now be able to hit the following local endpoint to invoke your function http://localhost:3000/hello

Packaging and deployment

AWS Lambda C# runtime requires a flat folder with all dependencies including the application. SAM will use CodeUri property to know where to look up for both application and dependencies:

        Type: AWS::Serverless::Function
            CodeUri: src/HelloWorld/bin/Debug/netcoreapp2.0/publish            

First and foremost, we need an S3 bucket where we can upload our Lambda functions packaged as ZIP before we deploy anything - If you don't have a S3 bucket to store code artifacts then this is a good time to create one:

aws s3 mb s3://BUCKET_NAME

Next, run the following command to package our Lambda function to S3:

sam package \
    --template-file template.yaml \
    --output-template-file packaged.yaml \

Next, the following command will create a Cloudformation Stack and deploy your SAM resources.

sam deploy \
    --template-file packaged.yaml \
    --stack-name look-ma-no-server \
    --capabilities CAPABILITY_IAM

See Serverless Application Model (SAM) HOWTO Guide for more details in how to get started.

After deployment is complete you can run the following command to retrieve the API Gateway Endpoint URL:

aws cloudformation describe-stacks \
    --stack-name look-ma-no-server \
    --query 'Stacks[].Outputs'


For testing our code, we use XUnit and you can use dotnet test to run tests defined under test/

dotnet test test/HelloWorld.Test


AWS CLI commands

AWS CLI commands to package, deploy and describe outputs defined within the cloudformation stack:

aws cloudformation package \
    --template-file template.yaml \
    --output-template-file packaged.yaml \

aws cloudformation deploy \
    --template-file packaged.yaml \
    --stack-name look-ma-no-server \
    --capabilities CAPABILITY_IAM \
    --parameter-overrides MyParameterSample=MySampleValue

aws cloudformation describe-stacks \
    --stack-name look-ma-no-server --query 'Stacks[].Outputs'

Bringing to the next level

Here are a few ideas that you can use to get more acquainted as to how this overall process works:

  • Create an additional API resource (e.g. /hello/{proxy+}) and return the name requested through this new path
  • Update unit test to capture that
  • Package & Deploy

Next, you can use the following resources to know more about beyond hello world samples and how others structure their Serverless applications: