Eks

Abstract

1. Introduction

Implementation of EKS setup using Terraform. Terraform module located in terraform directory supports deployment to different AWS partitions. I have tested it with commercial and china partitions. I am actively using this configuration to run EKS setup in Ireland(eu-west-1), London(eu-west-2), North Virginia(us-east-1) and Beijing(cn-north-1).

I am utilising Flux2 to deploy all additional configurations. You can find them at https://github.com/marcincuber/kubernetes-fluxv2 I have built this as a separate repository to show how to develop a successful configuration for your own cluster using GitOps FluxCD and Helm.

2. Objective

AWS EKS - kubernetes project and terraform module

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

3. Key Features / Modules

• VPC Endpoints- S3, ECR, STS, APS, GuardDuty
• EKS Cluster
• EKS Node Group to run cluster critical services
• EKS Addons- coredns, kube-proxy, guardduty, aws-ebs-csi-driver, adot (requires cert-manger to be installed), kubecost, cloudwatch observability, snapshot-controller, identity agent, metrics server, and kube-state-metrics
• IAM Roles for worker nodes and Karpenter nodes
• Additional IAM Roles for operators- load-balancer-controller, external-dns, cert-manager, adot-collector
• SQS queue configuration to be used with Karpeneter while utilising Spot Instances.
• CloudWatch log groups used by container insights.

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/marcincuber/eks.git
cd eks

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 marcincuber 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.