Skip to content

Comments

feat: Add AWS EKS deployment support (#23)#31

Open
ArsalanAnwer0 wants to merge 4 commits intoCMBAgents:mainfrom
ArsalanAnwer0:feature/aws-eks-deployment
Open

feat: Add AWS EKS deployment support (#23)#31
ArsalanAnwer0 wants to merge 4 commits intoCMBAgents:mainfrom
ArsalanAnwer0:feature/aws-eks-deployment

Conversation

@ArsalanAnwer0
Copy link

Summary

This PR implements full AWS EKS deployment support for CMBCluster, providing feature parity with the existing GCP deployment.

Changes

  • Created scripts/aws/setup-cluster.sh for EKS infrastructure provisioning
  • Created scripts/aws/deploy.sh for Helm-based application deployment
  • Created scripts/aws/cleanup.sh for complete resource teardown
  • Added .env.example.aws for AWS-specific configuration
  • Added comprehensive AWS deployment documentation
  • Updated main README to mention AWS support

AWS Services Implemented

  • EKS (Elastic Kubernetes Service) → GKE equivalent
  • S3 (Simple Storage Service) → Cloud Storage equivalent
  • ECR (Elastic Container Registry) → Artifact Registry equivalent
  • ALB (Application Load Balancer) → Cloud Load Balancer equivalent
  • IRSA (IAM Roles for Service Accounts) → Workload Identity equivalent
  • VPC with public/private subnets and NAT Gateway
  • AWS Load Balancer Controller for ingress
  • cert-manager for SSL certificates

Testing Checklist

  • Scripts execute without errors
  • EKS cluster provisions successfully
  • S3 buckets created with versioning
  • ECR repository created
  • IAM roles and IRSA configured correctly
  • ALB ingress controller installs
  • cert-manager installs
  • Application deploys to EKS
  • SSL certificates issue successfully

Related Issues

Closes #23

Documentation

  • Full deployment guide in scripts/aws/README.md
  • Environment configuration template provided
  • Cost estimates included
  • Troubleshooting section added

- Add setup-cluster.sh for EKS cluster provisioning with VPC, subnets, NAT gateway
- Add deploy.sh for Helm-based application deployment to EKS
- Add cleanup.sh for complete resource teardown
- Implement AWS service equivalents: EKS, S3, ECR, ALB, IRSA
- Configure AWS Load Balancer Controller for ingress
- Support cert-manager and Let's Encrypt SSL certificates
- Complete IAM role configuration with S3 and ECR permissions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Restructure scripts/ folder (create gcp/, aws/, common/ subdirs)

1 participant