{
  "id": 2425721,
  "title": "I Deployed Google's Online Boutique on AWS EKS — Full Production Setup, Zero App Code Changes",
  "url": "https://urgent.news/2026/08/21/i-deployed-googles-online-boutique-on-aws-eks-full-production-setup",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-21T19:17:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/vijaya_bollu/i-deployed-googles-online-boutique-on-aws-eks-full-production-setup-zero-app-code-changes-4aal"
  },
  "original_language": "en",
  "account": "Google's Open Boutique is an 11-service e-commerce demo that runs on Google Kubernetes Engine (GKE). The goal was to build a complete production AWS platform around it without altering the application code. Terraform, EKS, ECR, IAM, Helm, and GitHub Actions were used to achieve this.\n\nSeven Terraform files were created, each responsible for a specific task: VPC, EKS, ECR, IAM, remote state storage, and output values. The VPC was deployed in 13 seconds, followed by IAM roles in under a second each. The EKS control plane took about 10 minutes to set up. In total, 110 resources were created using a single `terraform apply` command.\n\nThe Node instance type selected was t3.small, the smallest option that could comfortably run all 11 services free-tier eligible. IAM design was scoped per pod using IRSA (Identity-Based Roles for Services), ensuring each pod only had the necessary permissions. The CI/CD pipeline was triggered by pushes to the main branch, version tags, or manual workflow dispatch. It utilized AWS Actions to configure AWS credentials via OIDC and pull images from ECR without any static AWS keys.\n\nHelm was used to deploy the services to EKS, with each service carrying its own resource request and limit. Temporary credentials were generated for each job, eliminating the need for long-term access keys and reducing the risk of credential leakage. The result was an operational online boutique running on AWS EKS, with no changes to the original application code.\n\nKey takeaways include the importance of scoped IAM per pod, considering free-tier restrictions when choosing instance types, implementing keyless CI/CD to prevent credential exposure, and leveraging small instance types for lightweight microservices.",
  "summary": "The Setup Google's Online Boutique is an open-source 11-service e-commerce demo — Go, Python, Node.js, C#, and Java, all communicating over gRPC. It ships designed for GKE. The task here: build a complete production AWS platform around it — Terraform, EKS, ECR, IAM, Helm, GitHub Actions — without changing a single line of the application source. The application layer stays exactly as Google…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}