• Infrastructure as Code (IaC): using Terraform, you get an infrastructure that’s smooth and efficient
• State management: Terraform saves the current infrastructure state, so you can review further changes without applying them. Also, state can be stored remotely, so you can work on the infrastructure in a team
• Scalability and flexibility: the infrastructure built based on this boilerplate can be expanded and updated anytime
• Comprehensiveness: you get scaling and monitoring instruments along with the basic infrastructure. You don’t need to manually modify anything in the infrastructure; you can simply make changes in Terraform as needed and deploy them to AWS and Kubernetes
• Control over resources: the IaC approach makes the infrastructure more observable and prevents waste of resources
• Clear documentation: your Terraform code effectively becomes your project documentation. It means that you can add new members to the team, and it won’t take them too much time to figure out how the infrastructure works

• Safe and polished: we’ve used these solutions in our own large-scale, high-load projects. We’ve been perfecting this infrastructure building process for months, making sure that it results in a system that is safe to use, secure, and reliable
• Saves time: you can spend weeks doing your own research and making the unavoidable mistakes to build an infrastructure like this. Instead, you can rely on this boilerplate and create the infrastructure you need within a day
• It’s free: we’re happy to share the results of our work

This repository contains terraform modules and configuration of the Mad Devs team for the rapid deployment of a Kubernetes cluster, supporting services, and the underlying AWS infrastructure.

In our company’s work, we have tried many infrastructure solutions and services and traveled the path from on-premise hardware to serverless. As of today, Kubernetes has become our standard platform for deploying applications, and AWS has become the main cloud.

It is worth noting here that although 90% of our and our clients’ projects are hosted on AWS and AWS EKS is used as the Kubernetes platform, we do not insist, do not drag everything to Kubernetes, and do not force anyone to be hosted on AWS. Kubernetes is offered only after the collection and analysis of service architecture requirements.

And then, when choosing Kubernetes, it makes almost no difference to applications how the cluster itself is created—manually, through kops or using managed services from cloud providers—in essence, the Kubernetes platform is the same everywhere. So the choice of a particular provider is then made based on additional requirements, expertise, etc.

We know that the current implementation is far from being perfect. For example, we deploy services to the cluster using terraform: it is rather clumsy and against the k8s approache, but it is convenient for bootstrapping because, by using state and interpolation, we convey proper IDs, ARNs, and other attributes to resources and names or secrets to templates and generated values from them for the required charts all within terraform.

There are more specific drawbacks: the data "template_file" resources that we used for most templates are extremely inconvenient for development and debugging, especially if there are 500+ line rolls like terraform/layer2-k8s/templates/elk-values.yaml. Also, despite helm3 got rid of the tiller, a large number of helm releases still at some point leads to plan hanging. Partially, but not always, it can be solved by terraform apply -target, but for the consistency of the state, it is desirable to execute plan and apply on the entire configuration. If you are going to use this boilerplate, it is advisable to split the terraform/layer2-k8s layer into several ones, taking out large and complex releases into separate modules.

You may reasonably question the number of .tf files. This monolith certainly should be refactored and split into many micro-modules adopting terragrunt approach. This is exactly what we will do in the near future, solving along the way the problems described above.

You can find more about this project in Anton Babenko stream:

• Boilerplate for a basic AWS infrastructure with EKS cluster
  • Advantages of this boilerplate and IaC
  • Why you should use this boilerplate
  • Description
  • Table of contents
  • FAQ: Frequently Asked Questions
  • Architecture diagram
  • Current infrastructure cost
  • Namespace structure in the K8S cluster
  • Useful tools
  • Useful VSCode extensions
  • AWS account
    • IAM settings
    • Setting up awscli
  • How to use this repo
    • Getting ready
      • Secrets
      • Domain and SSL
    • terragrunt
      • Apply infrastructure by modules with terragrunt
      • Target apply by terragrunt
      • Destroy infrastructure by terragrunt
  • What to do after deployment
    • Additional components
  • TFSEC
  • Contributing

FAQ: Frequently Asked Questions and HOW TO

This diagram describes the default infrastructure:

• We use three availability Zones
• VPC
  • Three public subnets for resources that can be accessible from the Internet
    • Elastic load balancing - entry point to the k8s cluster
    • Internet gateway - entry point to the created VPC
    • Single Nat Gateway - service for organizing access for instances from private networks to public ones.
  • Three private subnets with Internet access via Nat Gateway
  • Three intra subnets without Internet access
  • Three private subnets for RDS
  • Route tables for private networks
  • Route tables for public networks
• Autoscaling groups
  • On-demand - a group with 1-5 on-demand instances for resources with continuous uptime requirements
  • Spot - a group with 1-6 spot instances for resources where interruption of work is not critical
  • CI - a group with 0-3 spot instances created based on gitlab-runner requests; located in the public network
• EKS control plane - nodes of the k8s clusters’ control plane
• Route53 - DNS management service
• Cloudwatch - service for obtaining the metrics about resources’ state of operation in the AWS cloud
• AWS Certificate manager - service for AWS certificate management
• SSM parameter store - service for storing, retrieving, and controlling configuration values
• S3 bucket - this bucket is used to store terraform state
• Elastic container registry - service for storing docker images

The cost is indicated without counting the amount of traffic for Nat Gateway Load Balancer and S3

This diagram shows the namespaces used in the cluster and the services deployed there

• tfenv - tool for managing different versions of terraform; the required version can be specified directly as an argument or via .terraform-version
• tgenv - tool for managing different versions of terragrunt; the required version can be specified directly as an argument or via .terragrunt-version
• terraform - terraform itself, our main development tool: tfenv install
• awscli - console utility to work with AWS API
• kubectl - conssole utility to work with Kubernetes API
• kubectx + kubens - power tools for kubectl help you switch between Kubernetes clusters and namespaces
• helm - tool to create application packages and deploy them into k8s
• helmfile - "docker compose" for helm
• terragrunt - small terraform wrapper providing DRY approach in some cases: tgenv install
• awsudo - simple console utility that allows running awscli commands assuming specific roles
• aws-vault - tool for securely managing AWS keys and running console commands
• aws-mfa - utility for automating the reception of temporary STS tockens when MFA is enabled
• vscode - our main IDE

Optionally, a pre-commit hook can be set up and configured for terraform: pre-commit-terraform, this will allow formatting and validating code at the commit stage

• editorconfig
• terraform
• drawio
• yaml
• embrace
• js-beautify
• docker
• git-extension-pack
• githistory
• kubernetes-tools
• markdown-preview-enhanced
• markdownlint
• file-tree-generator
• gotemplate-syntax

We will not go deep into security settings since everyone has different requirements. However, there are the simplest and most basic steps worth following to move on. If you have everything in place, feel free to skip this section.

It is highly recommended not to use a root account to work with AWS. Make an extra effort of creating users with required/limited rights.

To start using this project you need to make several small preparation steps.

Some local variables expect AWS Secrets Manager secret with the pattern /${local.name_wo_region}/infra/layer2-k8s.

The secret /${local.name_wo_region}/infra/layer2-k8 must be created before running terraform apply. Which parameters should be placed in the SM secret for services is discussed in the FAQ.

You will need to purchase or use an already purchased domain in Route53. After that set domain_name and zone_id variables in variables.tf, tfvars files of env.yaml if you use terragrunt.

By default, the variable create_acm_certificate is set to false. Which instructs terraform to search ARN of an existing ACM certificate. Set to true if you want terraform to create a new ACM SSL certificate.

We've also used terragrunt to simplify s3 bucket creation and terraform backend configuration. All you need to do is to set s3 bucket name in the TF_REMOTE_STATE_BUCKET env variable and run terragrunt command in the terragrunt/demo/us-east-1 directory:

$ export TF_REMOTE_STATE_BUCKET=my-new-state-bucket
$ cd terragrunt/demo/us-east-1
$ terragrunt run-all init
$ terragrunt run-all apply

By running this terragrunt will create s3 bucket, configure terraform backend and then will run terraform init and terraform apply in layer-1 and layer-2 sequentially.

Terragrunt version pinned in terragrunt.hcl file.

Go to layer folder terragrunt/demo/us-east-1/aws-base or terragrunt/demo/us-east-1/k8s-addons and run this command:

terragrunt apply

Module k8s-addons depends on aws-base.

Go to layer folder terragrunt/demo/us-east-1/aws-base and run this command:

terragrunt apply -target=module.eks

The -target is formed from the following parts resource type and resource name. For example: -target=module.eks, -target=helm_release.loki_stack

To destroy everything at once, run this command from terragrunt/demo/us-east-1/ folder:

terragrant run-all destroy

The k8s-addons depends on aws-base, so k8s-addons will be destroyed automatically first.

If you want to destroy modules manually, then destroy k8s-addons first, ie run this command from terragrunt/demo/us-east-1/k8s-addons folder:

terragrunt destroy

Clear all buckets before destroying.

• After applying this configuration, you will get the infrastructure described and outlined at the beginning of the document. In AWS and within the EKS cluster, the basic resources and services necessary for the operation of the EKS k8s cluster will be created.

  • You can get access to the cluster using this command:

    aws eks update-kubeconfig --name maddevs-demo-use1 --region us-east-1

• If you use default configuration and want to serve traffic for a main domain (example.com) by an application deployed into a k8s cluster, youn need to manually create DNS record in Route53 with type A + Alias

• DNS record *.example.com created automatically and points to Load Balancer in front of k8s cluster.

This boiler installs all basic and necessary components. However, we also provide several additional components. Both layers have such components. To enable them in:

• terraform/layer1-aws: search ***_enable variables and set them to true
• terraform/layer2-k8s: check helm-releases.yaml file and set enabled: true or enabled:false for components that you want to deploy or to unistall

Notes:

• To use pure terraform
• Gitlab-runner
• Monitoring

TFSEC: Notes related to tfsec ignores

If you're interested in contributing to the project:

• Start by reading the Contributing guide
• Explore current issues.