EKS to Amplify Migration Guide

💰 Cost Analysis

Your current EKS setup is significantly over-engineered for static website hosting. Here's the cost breakdown:

❌ Current EKS Setup

$123-143

per month

EKS Control Plane: $73/month
Fargate Pods: $30-50/month
Application Load Balancer: $20/month
Data Transfer: $5-10/month

✅ AWS Amplify

$1-5

per month

Static Hosting: $1-3/month
CloudFront CDN: $1-2/month
SSL Certificate: Free
Route 53: $0.50/month

                    💡 Savings: 95% cost reduction! You'll save approximately $118-138 per month by migrating to Amplify.
                

🔄 Migration Steps

1 Extract Website Content

I've already extracted your HTML content from the Kubernetes ConfigMap and created local files.

2 Create Git Repository

# Create a new directory for your website
mkdir mcp-amplify-website
cd mcp-amplify-website

# Initialize git repository
git init
git add .
git commit -m "Initial commit: MCP website migration to Amplify"

# Create GitHub repository and push
gh repo create mcp-amplify-website --public
git remote add origin https://github.com/YOUR_USERNAME/mcp-amplify-website.git
git push -u origin main
                    

3 Set Up AWS Amplify

Connect your GitHub repository to AWS Amplify for automatic deployments.

☁️ AWS Amplify Setup

Option 1: Using AWS Console

Step-by-Step Console Setup

Go to AWS Amplify Console
Click "New app" → "Host web app"
Select "GitHub" as source
Authorize AWS Amplify to access your GitHub
Select your repository and branch
Configure build settings (auto-detected for static sites)
Review and deploy

Option 2: Using AWS CLI

CLI-Based Setup

# Create Amplify app
aws amplify create-app \
  --name "mcp-website" \
  --description "MCP Documentation Website" \
  --repository "https://github.com/YOUR_USERNAME/mcp-amplify-website" \
  --platform "WEB" \
  --iam-service-role-arn "arn:aws:iam::ACCOUNT:role/amplifyconsole-backend-role"

# Create branch
aws amplify create-branch \
  --app-id "YOUR_APP_ID" \
  --branch-name "main" \
  --description "Main production branch"

# Start deployment
aws amplify start-job \
  --app-id "YOUR_APP_ID" \
  --branch-name "main" \
  --job-type "RELEASE"
                    

Custom Domain Setup

Configure Your Domain

# Add custom domain to Amplify app
aws amplify create-domain-association \
  --app-id "YOUR_APP_ID" \
  --domain-name "mcpkubernetes.cloudopsinsights.com" \
  --sub-domain-settings '{
    "prefix": "",
    "branchName": "main"
  }'

# Update Route 53 DNS records (Amplify will provide CNAME values)
aws route53 change-resource-record-sets \
  --hosted-zone-id "YOUR_HOSTED_ZONE_ID" \
  --change-batch file://dns-changes.json
                    

🧹 EKS Cleanup

⚠️ Important: Only proceed with cleanup after verifying your Amplify site is working correctly.

1 Delete Application Resources

# Delete the ingress (this will remove the ALB)
kubectl delete ingress nginx-ingress -n fargate-demo

# Delete the service
kubectl delete service fargate-demo-service -n fargate-demo

# Delete the deployment
kubectl delete deployment fargate-demo-app -n fargate-demo

# Delete ConfigMaps
kubectl delete configmap mcp-html-content -n fargate-demo
kubectl delete configmap nginx-config -n fargate-demo

# Delete the namespace
kubectl delete namespace fargate-demo
                    

2 Remove AWS Load Balancer Controller

# Uninstall AWS Load Balancer Controller
helm uninstall aws-load-balancer-controller -n kube-system

# Delete the IAM service account
eksctl delete iamserviceaccount \
  --cluster=demo \
  --namespace=kube-system \
  --name=aws-load-balancer-controller
                    

3 Delete EKS Cluster

# Delete the entire EKS cluster
eksctl delete cluster --name demo --region us-east-1

# This will automatically delete:
# - EKS cluster
# - Fargate profiles
# - Node groups
# - Associated VPC and subnets
# - Security groups
# - IAM roles
                    

4 Clean Up Route 53 (Optional)

# If you want to remove old DNS records
aws route53 change-resource-record-sets \
  --hosted-zone-id "YOUR_HOSTED_ZONE_ID" \
  --change-batch '{
    "Changes": [{
      "Action": "DELETE",
      "ResourceRecordSet": {
        "Name": "mcpkubernetes.cloudopsinsights.com",
        "Type": "CNAME",
        "TTL": 300,
        "ResourceRecords": [{"Value": "OLD_ALB_DNS_NAME"}]
      }
    }]
  }'
                    

🎯 Migration Benefits

                    Why This Migration Makes Sense:
                    Cost Efficiency: 95% cost reduction for static content
Performance: Global CDN with edge caching
Simplicity: No container orchestration complexity
Scalability: Automatic scaling for traffic spikes
Security: Built-in DDoS protection and WAF
Maintenance: Zero infrastructure maintenance
CI/CD: Automatic deployments from Git

                

🚀 EKS to Amplify Migration Guide