https://github.com/juhalehtonen/terraform-lambda
https://github.com/juhalehtonen/terraform-lambda
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/juhalehtonen/terraform-lambda
- Owner: juhalehtonen
- Created: 2018-03-26T14:30:58.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-04-05T20:17:58.000Z (about 7 years ago)
- Last Synced: 2025-04-06T08:13:52.040Z (about 2 months ago)
- Language: HCL
- Size: 11.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Terraform with AWS Lambda
A simple Terraform configuration setup for AWS Lambda and a description of the proposed workflow.
## Before using
Keep in mind that this is an opinionated approach, as we ignore the built-in versioning and staged deployment mechanisms in AWS Lambda. Often these features are not necessary because changes can be tracked and deployed by keeping the Terraform configuration in a version-control repository.
If you think you will need to do something different or with a different architecture, you will need to adapt accordingly.
## How to use
Note that this currently only creates the Lambda and the required role to run it.
1. Install Terraform (On OSX you can just do `brew install terraform` if you trust Homebrew)
2. The first command to run for a new configuration -- or after checking out an existing configuration from version control -- is `terraform init`, which initializes various local settings and data that will be used by subsequent commands.
3. Copy `secrets.auto.tfvars.sample` to `secrets.auto.tfvars` and configure your AWS access key and secret in it. Do NOT touch the sample file itself, as it is committed to version control for example purposes only.
4. Adjust the variables in `terraform.tfvars` to determine which version of the Lambda function to deploy, and which S3 bucket to use.
5. Run `terraform plan` to refresh the current state and to generate an action plan based on the config.
6. Run `terraform apply` to apply the plan and create resources.
7. Wait as Terraform provisions AWS Lambda for you
## Destroy changes
1. Run `terraform plan --destroy` to see what will happen when you initiate destroy.
2. Run `terraform destroy` and type `yes` to destroy the specified resources.
## To-do
- What if we have secrets in our Lambda (e.g. Lambda doesn't encrypt at runtime)
- Check lambda-role.json, is it restrictive enough?
- Versioning, how to? S3? Lambda? Rely on TF state?