Serverless Tf

Abstract

1. Introduction

serverless.tf has started as an organic response to the accidental complexity of many existing tools used by serverless developers.

serverless.tf is not an official AWS or HashiCorp product, and is not to be confused with the Serverless Framework.

This project is in the beta. Going through the development process with Betajob's products, and with external customers, serverless.tf's concepts will be verifying and updating.

2. Objective

serverless.tf is an opinionated open-source framework for developing, building, deploying, and securing serverless applications and infrastructures on AWS using Terraform.

This project demonstrates how Terraform, Serverless can be applied to a real-world Blockchain & Cloud Computing problem.

4. Technology Stack

• Serverless application frameworks (Serverless Framework, AWS Chalice, Zappa) to develop, test, and deploy code and serverless infrastructure resources.
• Infrastructure management (Terraform, AWS CloudFormation) manages traditional resources which are not related to serverless, and sometimes to create resources for serverless applications, too.
• Application deployment (Shell scripts, Makefile, AWS CodeDeploy, AWS CLI) to orchestrate non-trivial builds of dependencies and do deployments, also.

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• See the project README for exact requirements
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/antonbabenko/serverless.tf.git
cd serverless.tf

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add a CI/CD pipeline with GitHub Actions
• Deploy to a public test network or cloud free tier
• Add monitoring and cost alerts

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Why does this problem need a blockchain or cloud-native design?
2. Explain the smart contract / infrastructure components and how they interact.
3. How are gas costs or cloud costs kept under control?
4. How is the system secured (keys, IAM, access control)?
5. How would the solution scale to many more users?

9. Source Code & License

This project is developed by antonbabenko and published on GitHub under the Apache License 2.0. Please follow the license terms and credit the original author when you use or modify this code.