lex-provisioner

Requirements

• AWS CLI already configured with at least PowerUser permission
• Python 3 installed
• Docker installed
• Python Virtual Environment

Setup process

Install tox

pip install tox

Testing locally

Requires python 3.7.2 virtualenv. I use direnv and layouts to set this up.

tox -r

Building the project

AWS Lambda requires a flat folder with the application as well as its dependencies. When you make changes to your source code or dependency manifest, run the following command to build your project local testing and deployment:

sam build

If your dependencies contain native modules that need to be compiled specifically for the operating system running on AWS Lambda, use this command to build inside a Lambda-like Docker container instead:

sam build -u # --use-container
sam build -u --skip-pull-image # once you've run it once to get the container

By default, this command writes built artifacts to .aws-sam/build folder.

Local development

Invoking function with create and delete event

sam local invoke -e fixtures/test-create.json
sam local invoke -e fixtures/test-create.json -n fixtures/test-env.json # override env vars option

sam local invoke -e fixtures/test-delete.json -n fixtures/test-env.json # delete option 

test.json is an example event. test-env.json is a sample json file to override env vars which may be necessary to not fail on callback of confirmation urls in cfn

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

Packaging and deployment

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 \
    --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 sam-app \
    --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 sam-app \
    --query 'Stacks[].Outputs'

Testing

We use Pytest and pytest-mock for testing our code and you can install it using pip: pip install pytest pytest-mock

Next, we run pytest against our tests folder to run our initial unit tests:

python -m pytest tests/ -v

Or

tox

Or to run a single test:

tox -- tests/unit/test_app.py::test_delete_bot_called

NOTE: It is recommended to use a Python Virtual environment to separate your application development from your system Python installation.

Appendix

Python Virtual environment

In case you're new to this, python3 comes with virtualenv library by default so you can simply run the following:

1. Create a new virtual environment
2. Install dependencies in the new virtual environment

python3 -m venv .venv
. .venv/bin/activate
pip install -r requirements.txt

NOTE: You can find more information about Virtual Environment at Python Official Docs here. Alternatively, you may want to look at Pipenv as the new way of setting up development workflows

AWS CLI commands

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

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

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

aws cloudformation describe-stacks \
    --stack-name sam-app --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:

• AWS Serverless Application Repository
• Chalice Python Serverless framework
• Sample Python with 3rd party dependencies, pipenv and Makefile: sam init --location https://github.com/aws-samples/cookiecutter-aws-sam-python