helloworld-lambda-demo

Basic lambda function deployment using terraform. This lambda function queries the below endpoint and publishes the latest blocks to an sns topic. https://blockchain.info/blocks/1620819099272?format=json

Prerequisites

• AWS account with local credentials configure ~/.aws/credentials
• aws cli installed and configured on your local environment.
• Terraform 0.14.7+ installed on your local workstation.
• npm installation(node package manager) done on your local workstation

Create and push lambda artifact to an s3 bucket

Follow below steps to create a lambda artifact and push it to an s3 bucket

• Parameters required

  • s3 bucket name - this should be a globally unique s3 bucket name - default(helloworld-lambda-example-32431)

• Run below command to create an s3 bucket and push lambda artifact to it

  • sh upload-artifact.sh

This s3 bucket name will be required when deploying lambda function in the next step.

Deploy lambda function to aws using terraform

Follow below steps to deploy lambda function to aws

• Parameters required

  • S3 bucket name for lambda artifact(this bucket is created in above step)
  • Email address sns topic subscription(this email address will be subscribe to sns topic created)

• Move to terraform directory and initialize terraform

  • cd terraform
  • terraform init

• Run terraform plan to have glance at what resources will be created

  • terraform plan

• Run terraform apply to deploy lambda function to aws

  • terraform apply

Note

All aws resources will be created in us-east-1 region

Known Issue

Lambda was unable to decrypt the environment variables because KMS access was denied This is a known issue as shown in below link. You get this error when you deploy the lambda function for the first time and try to run it.

serverless/examples#279

Workaround

You can just do a simple modification to the lambda as shown below and redeploy the lambda to get rid of this error.

• Modify lambda.tf file and change the timeout value to a different value
  • timeout = 80 --> timeout = 100
• Redeploy the lambda using terraform apply
• This should fix the KMS access denied