Terraform sample solution to deploy a cloud-native application on AWS

Cloudposse have a huge list of open-sourced Terraform modules for AWS.

Those modules can be used as plug-and-play to create and manage various AWS resources for an application.

For this sample solution, below modules are used :

Label

VPC

Subnet

EFS

EKS cluster

EKS workers

Elasticsearch

NOTE : This sample solution includes an additional module called "my-app-eks-setup" that is used to setup and configure Kubernetes after EKS cluster is deployed, and then install Helm charts on top of that.

In the terraform code for deploying a complete application on AWS, these modules are executed (parallel or sequential, based on their dependencies) from a "root module" (for ex. "my_app.tf").

High-level flow of the modules deployment :

NOTE : This diagram is mainly focused on Kubernetes and Helm configuration and deployments. Hence, does not include common modules and resources like Label, VPC, subnets, security groups, IAM roles etc.

In the my_app.tf module, which is the "root module" that executes other modules need to have module "my-app-eks-setup" to execute the above mentioned flow in addition to other modules :

provider "aws" {
  ...
}
module "label" {
  ...
}
module "vpc" {
  ...
}
module "eks-cluster" {
  ...
}
.....
.....
locals {
  kubeconfig_filename          = "${path.module}/kubeconfig${var.delimiter}${module.eks_cluster.eks_cluster_id}.yaml"
}
module "my-app-eks-setup" {
  source                        = "/path/to/module/my-app-eks-setup"
  namespace                     = "${var.namespace}"
  
  # EKS cluster name and endpoint
  cluster_name                  = "${module.cluster_label.id}"
  cluster_endpoint              = "${module.eks_cluster.eks_cluster_endpoint}"
  
  kubeconfig                    = "${module.eks_workers.kubeconfig}"
  kubeconfig_filename           = "${local.kubeconfig_filename}"
  cluster_ca_certificate        = "${base64decode(module.eks_cluster.eks_cluster_certificate_authority_data)}"
  # If generated token is used for Kubernetes and/or Helm providers
  #token                         = "${module.eks_cluster.aws_authenticator_token}"
  aws_iam_role                  = "${module.eks_workers.worker_role_arn}"
  
  # Elasticsearch domain endpoint
  domain_endpoint               = "${module.elasticsearch.domain_endpoint}"
  
  # Helm chart params for efs-provisioner
  efs_id                        = "${module.efs.id}"
  region                        = "${var.region}"
}
.....

More information

Deploying a cloud-native application on AWS using Terraform

License

The MIT License (MIT). Please see License File for more information.