Terraform Examples

Abstract

1. Introduction

This module manages CloudFront distributions, and these operations are generally very slow. Your terraform apply may take anywhere from 10 minutes up to 45 minutes to complete. Be patient: if they start successfully, they almost always finish successfully, it just takes a while.

Additionally, this module uses Lambda@Edge functions with CloudFront. Because Lambda@Edge functions are replicated, they can't be deleted immediately. This means a terraform destroy won't successfully remove all resources on its first run. It should complete successfully when running it again after a few hours, however.

This module manages CloudFront distributions, and these operations are generally very slow. Your terraform apply may take anywhere from 10 minutes up to 45 minutes to complete. Be patient: if they start successfully, they almost always finish successfully, it just takes a while.

2. Objective

Terraform samples for all the major clouds you can copy and paste. The future, co-created.

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

3. Key Features / Modules

• Managed identity for authentication instead of credentials
• Key vault references for accessing secrets from App Service
• Email alerts for errors and failed availability checks
• Random suffix for resources requiring globally unique name

4. Technology Stack

5. System Requirements

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

• Terraform CLI
• Cloud provider account (e.g. AWS) with CLI configured
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/futurice/terraform-examples.git
cd terraform-examples

1. Azure account and a service principal
2. Resource group
3. Terraform Azure Provider set up
4. Using Github actions
5. Using Azure DevOps pipelines
6. to set cloud run service to noauth, had to add Security Admin on camunda cloud run resource (NOT PROJECT level)
7. to set cloud run service to noauth, had to add Security Admin on camunda cloud run resource (NOT PROJECT level)

module "my_app" {
  # Required
  resource_group_name = "my-resource-group"
  alert_email_address = "example@example.com"

  # Optional (with their default values)
  name_prefix            = "azure-app-example--"
  app_service_name      = "appservice"
  app_insights_app_type = "other"
  app_service_plan_tier = "PremiumV2"
  app_service_plan_size = "P1v2"
}

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 futurice and published on GitHub under the MIT License. Please follow the license terms and credit the original author when you use or modify this code.