Figure 1: PCIDSS Project: CICD Pipeline to Provision Infrastructure (Kubernetes Cluster & Addons) to AWS Cloud, highlighting the frontend and the backend repo.

AWS Architecture Overview — Deploying a High-Availability Kubernetes Cluster on AWS Using a 3-Tier Architecture

This architectural drawing summarises how to deploy a high-availability Kubernetes Cluster in the AWS environment using a 3-tier architecture.

🧱 1. Infrastructure as Code with Terraform

Everything starts with Terraform. We use it to define and provision all AWS infrastructure:

• Amazon EKS cluster (Kubernetes)
• Amazon RDS (for MySQL)
• Amazon S3 (for backups and assets)
• Amazon ECR (Docker image registry)
• Route 53 hosted zone
• IAM roles, security groups, VPC, subnets, and more

This ensures the entire infrastructure is version-controlled, reproducible, and scalable.

📦 2. GitHub and Docker

Our application code and infrastructure configurations live in GitHub repositories:

• When a developer pushes code, GitHub Actions is triggered:
  • It builds a Docker image of the application.
  • Pushes that image to Amazon ECR.
  • Updates Kubernetes manifests in the infrastructure repo.

🚀 3. ArgoCD – Continuous Deployment with GitOps

With ArgoCD running inside the EKS cluster, deployment becomes hands-free: