slsmanager 0.1.4

A basic tool that simplifies the deployment of AWS lambda functions

Serverless Manager

A basic Python Tool that simplifies the deployment of multiple AWS Lambda functions directly from an AWS CodeCommit Repository.

Set Up

• Set up an IAM user on your AWS console

  • You require the following permissions:
  • Store the Access Key ID and the Secret Access Key
  • Generate the git credentials for the user. (Security Credentials -> HTTPS Git Credentials)

• Create a CodeCommit Repository and clone it to your directory using the Git Credentials.

• Create a CodeBuild Project

  • Set the source provider to CodeCommit and the repository to the newly created CodeCommit repository
  • Pick the branch you will be pushing to.
  • In buildspec, choose “Use a buildspec file” and leave the filename empty (Since the default is buildspec.yml
  • Create the project
  • Edit the environment variables and add the following variables:
  • The ENV_NAME_ variables refer to the different environments you would be deploying. For instance, I have 3 environments: dev, prod and uat. This allows us to deploy the lambda function at different stages (Creating a different function for each stage)

• Create a CodePipeline

  • Source provider: AWS CodeCommit
  • Repo Name: Source repo
  • Build Provider: AWS CodeBuild
  • Project Name: Name of Codebuild Project
  • Skip deploy stage since we are using the Serverless Framework to deploy our functions
  • Create the Pipeline

• Install serverless-manager and place it in the directory with your handlers

Using the tool

• I have a file called handlerFun1.js. It contains the function firstFun() which I would like to deploy.
• Run serverless manager on your terminal and follow the instructions:
  • Here, I created a service called "CodeCommitTest"
  • I set the AWS-region to us-east-2 (which is what my AWS console is set to).
  • The stage sets the serverless stage property.
  • The ENV_NAME is the last part of the ENV_NAME_ environment variables (which we set earlier). This will be reflected in the final name of your function on your console.
  • Module name follows the convention dir/filename.function
  • The function name is the name of the final lambda function (and is set in serverless.yml)
  • By default, the only file added to the current lambda function is the handler file provided in the module name. If you would like to include other files in the final lambda function that is deployed, you may edit the newly generated serverless.yml and add the required files to the functions/your_function/package/patterns
  • You may also edit/add any other properties in serverless.yml
  • Finally, the tool generates a buildspec.yml file for your function.
    • If you want to deploy all lambda functions present in serverless.yml you can press 'a' in the final step. Otherwise, press 'n'.
  • Once you have completed all your steps, you will see 2 new files serverless.yml (Which lists all the properties required to deploy using the Serverless Framework and buildspec.yml (Which instructs CodeBuild to deploy the function(s) using the given files and properties.