messages-mover

This lambda basically moves messages from Source Queue to Target Queue without doing any process on the messages.

Local development:

check local folder

Deploy to your account:

Check deploy.sh file

Pipeline:

Check Jenkinsfile, this needs to be inhanced and maybe the code can be moved to make file.

Auto-generated Readme:

This is a sample template for messages-mover - Below is a brief explanation of what we have generated for you:

.
├── README.md                   <-- This instructions file
├── sqs_msgs_mover                 <-- Source code for a lambda function
│   ├── app.js                  <-- Lambda function code
│   ├── package.json            <-- NodeJS dependencies
│   └── tests                   <-- Unit tests
│       └── unit
│           └── test_handler.js
└── template.yaml               <-- SAM template

Requirements

AWS CLI already configured with at least PowerUser permission
NodeJS 8.10+ installed
Docker installed

Setup process

Installing dependencies

In this example we use npm but you can use yarn if you prefer to manage NodeJS dependencies:

cd sqs_msgs_mover
npm install
cd ../

Local development

Invoking function locally through local API Gateway

sam local start-api

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

SAM CLI 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:

...
Events:
    MoveMessages:
        Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
        Properties:
            Path: /run
            Method: get

Packaging and deployment

AWS Lambda NodeJS 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:

...
    FirstFunction:
        Type: AWS::Serverless::Function
        Properties:
            CodeUri: sqs_msgs_mover/
            ...

Firstly, we need a 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 \
    --s3-bucket REPLACE_THIS_WITH_YOUR_S3_BUCKET_NAME

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

sam deploy \
    --template-file packaged.yaml \
    --stack-name messages-mover \
    --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 messages-mover \
    --query 'Stacks[].Outputs'

Testing

We use jest for testing our code and it is already added in package.json under scripts, so that we can simply run the following command to run our tests:

cd sqs_msgs_mover
npm run test

Appendix

AWS CLI commands

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

sam package \
    --template-file template.yaml \
    --output-template-file packaged.yaml \
    --s3-bucket REPLACE_THIS_WITH_YOUR_S3_BUCKET_NAME

sam deploy \
    --template-file packaged.yaml \
    --stack-name messages-mover \
    --capabilities CAPABILITY_IAM \
    --parameter-overrides MyParameterSample=MySampleValue

aws cloudformation describe-stacks \
    --stack-name messages-mover --query 'Stacks[].Outputs'

NOTE: Alternatively this could be part of package.json scripts section.

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:

AWS Serverless Application Repository

safaa-alnabulsi / sam-serverless-workshop