Create AWS EKS deployment scripts

[UJ2202]

User Story

As a DevOps engineer, I want AWS EKS deployment scripts so that I can deploy CMBCluster on Amazon Web Services with the same functionality as the current GCP deployment.

Description

Create comprehensive AWS EKS deployment scripts that mirror the functionality of the existing GCP deployment, including cluster setup, networking, storage, and application deployment.

Current GCP Implementation Analysis

Based on scripts/setup-cluster.sh analysis:

• GKE Cluster: Private cluster with VPC, subnets, NAT gateway
• Storage: Cloud Storage buckets for database and user data
• Networking: Custom VPC with secondary ranges for pods/services
• Registry: Artifact Registry for container images
• Security: IAM service accounts, firewall rules
• Monitoring: Ingress controller, cert-manager

AWS Equivalent Services

• EKS (Elastic Kubernetes Service) → GKE
• S3 (Simple Storage Service) → Cloud Storage
• ECR (Elastic Container Registry) → Artifact Registry
• VPC (Virtual Private Cloud) → VPC
• IAM → Cloud IAM
• ALB/NLB → Google Load Balancer

Technical Requirements

Create AWS deployment scripts with:

• EKS cluster creation with private nodes
• VPC and subnet configuration
• S3 buckets for database and user storage
• ECR repository setup
• IAM roles and service accounts
• ALB Ingress Controller installation
• cert-manager for SSL certificates
• Workload Identity equivalent (IRSA - IAM Roles for Service Accounts)

Scripts to Create

1. scripts/aws/setup-cluster.sh

   • EKS cluster creation
   • VPC and networking setup
   • S3 bucket creation
   • ECR repository setup
   • IAM configuration

2. scripts/aws/deploy.sh

   • Helm chart deployment with AWS values
   • Application deployment to EKS
   • DNS and ingress configuration

3. scripts/aws/cleanup.sh

   • Resource cleanup and tear-down
   • S3 bucket management
   • EKS cluster deletion

Acceptance Criteria

• EKS cluster deploys successfully with proper networking
• S3 buckets are created and configured correctly
• ECR repository stores container images
• IAM roles provide appropriate permissions
• ALB Ingress Controller functions properly
• cert-manager issues SSL certificates
• CMBCluster application deploys and runs on EKS
• User environments can be created and accessed
• Storage mounting works with S3
• All scripts are well-documented and tested

Key Differences from GCP

• Authentication: IRSA instead of Workload Identity
• Storage: S3 instead of Cloud Storage
• Networking: ALB instead of Google Load Balancer
• Registry: ECR instead of Artifact Registry
• DNS: Route 53 integration options

Configuration Parameters

• AWS region and availability zones
• EKS cluster version and node groups
• VPC CIDR blocks and subnet ranges
• S3 bucket naming and policies
• ECR repository configuration
• IAM role definitions

Testing Requirements

• Functional testing of complete deployment
• Validation of all AWS services integration
• Comparison with GCP deployment features
• Documentation of any feature differences
• Performance testing on EKS

Related to

Epic #22 - Multi-Cloud Support

Definition of Done

• Complete AWS deployment scripts are functional
• CMBCluster deploys successfully on EKS
• Feature parity with GCP deployment is achieved
• Documentation covers AWS deployment process
• Scripts are tested and validated

[ArsalanAnwer0]

Hi! I'd like to work on this issue. I'll create AWS EKS deployment scripts that mirror the existing GCP deployment functionality. My approach will be:

1. Analyze the current GCP implementation in scripts/setup-cluster.sh
2. Create scripts/aws/setup-cluster.sh for EKS cluster, VPC, S3, ECR, and IAM setup
3. Develop scripts/aws/deploy.sh for application deployment with AWS-specific configurations
4. Build scripts/aws/cleanup.sh for resource tear-down
5. Implement IRSA for workload identity, ALB Ingress Controller, and cert-manager integration
6. Test the complete deployment to ensure feature parity with GCP
7. Document the AWS deployment process and any differences from GCP

Could you please assign this to me? Thanks!

[UJ2202]

Hi Arsalan, Good to know you are interested in contributing to the project,it will be exciting to work with you. Please fork the repository and after doing the changes please raise a pull request we will merge it with main branch after reviewing the code. Reagrds, Ujjwal

…

On Wed, 1 Oct, 2025, 23:45 Arsalan, ***@***.***> wrote: *ArsalanAnwer0* left a comment (CMBAgents/cmbcluster#24) <#24 (comment)> Hi! I'd like to work on this issue. I'll create AWS EKS deployment scripts that mirror the existing GCP deployment functionality. My approach will be: 1. Analyze the current GCP implementation in scripts/setup-cluster.sh 2. Create scripts/aws/setup-cluster.sh for EKS cluster, VPC, S3, ECR, and IAM setup 3. Develop scripts/aws/deploy.sh for application deployment with AWS-specific configurations 4. Build scripts/aws/cleanup.sh for resource tear-down 5. Implement IRSA for workload identity, ALB Ingress Controller, and cert-manager integration 6. Test the complete deployment to ensure feature parity with GCP 7. Document the AWS deployment process and any differences from GCP Could you please assign this to me? Thanks! — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3G4E62ATE36JCUXAGPMIDT3VQK4HAVCNFSM6AAAAACHVLOWT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNJXGU2DCOBQHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>