AWS Migration: t3.micro/small → m7i-flex.large for ML Workloads

• m6i.large — consistent baseline (100% CPU always available), no throttling, predictable latency
• m7i-flex.large — 5% faster at peak, but 40% baseline can cause queue buildup under steady API traffic
• Winner for API-heavy: m6i.large

• m7i-flex.large wins due to AMX acceleration and 2x memory bandwidth (DDR5)
• Estimated training speedup on RandomForest (1 GB dataset): ~15% faster at full burst
• At 40% baseline: ~2x slower — schedule ML jobs to avoid baseline throttling
• Winner for ML: m7i-flex.large

• Short, bursty jobs fit perfectly with m7i-flex burst model
• Long-running continuous tasks risk hitting the 40% baseline ceiling
• Winner for bursty Celery: m7i-flex.large

Your AWS credits will not be lost. Credits apply at the account level, not per instance. Both old and new instances consume credits from the same pool.

# Note down these before touching anything
# - Security group IDs
# - IAM role name
# - EBS volume IDs and sizes
# - Elastic IP allocation ID (if any)
# - Environment variables / .env files

tar -czf ~/backup.tar.gz /app
aws s3 cp ~/backup.tar.gz s3://your-bucket/backups/migration-$(date +%Y%m%d).tar.gz

aws ec2 describe-instances \
  --filters "Name=instance-type,Values=t3.micro" \
  --query 'Reservations[0].Instances[0].InstanceId' \
  --region us-east-1
# Output: i-0123456789abcdef0

aws ec2 stop-instances --instance-ids i-0123456789abcdef0 --region us-east-1
aws ec2 wait instance-stopped --instance-ids i-0123456789abcdef0 --region us-east-1

aws ec2 create-image \
  --instance-id i-0123456789abcdef0 \
  --name "t3-micro-backup-$(date +%Y%m%d)" \
  --description "Backup before m7i-flex migration" \
  --region us-east-1
# Output: { "ImageId": "ami-0abc123def456ghi" }

aws ec2 run-instances \
  --image-id ami-0abc123def456ghi \
  --instance-type m7i-flex.large \
  --key-name your-keypair-name \
  --security-group-ids sg-0123456789abcdef0 \
  --iam-instance-profile Name=your-iam-role \
  --region us-east-1 \
  --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=app-m7i-flex}]'

aws ec2 describe-instances \
  --filters "Name=tag:Name,Values=app-m7i-flex" \
  --query 'Reservations[0].Instances[0].PublicIpAddress' \
  --region us-east-1

ssh -i your-key.pem ec2-user@<new-public-ip>

# Confirm instance type
curl http://169.254.169.254/latest/meta-data/instance-type
# Should return: m7i-flex.large

# Check RAM
free -h
# Should show ~8GB

# Check services
docker ps                        # if using Docker
systemctl status your-app        # if using systemd
celery -A app inspect active     # if using Celery

# Test API
curl http://localhost:8000/health

# Disassociate from old instance
aws ec2 disassociate-address --association-id eipassoc-abc123 --region us-east-1

# Associate with new instance
aws ec2 associate-address \
  --instance-id i-new123456 \
  --allocation-id eipalloc-abc123 \
  --region us-east-1

# ⚠️ Only run this after 24+ hours of verified stable operation
aws ec2 terminate-instances \
  --instance-ids i-0123456789abcdef0 \
  --region us-east-1

# List your snapshots
aws ec2 describe-snapshots \
  --owner-ids self \
  --region us-east-1 \
  --query 'Snapshots[*].[SnapshotId,StartTime,Description]' \
  --output table

# Delete old ones you no longer need
aws ec2 delete-snapshot --snapshot-id snap-old123456 --region us-east-1

#!/bin/bash
set -e

INSTANCE_ID="i-0123456789abcdef0"   # Your t3.micro ID
REGION="us-east-1"
SECURITY_GROUP="sg-0123456789abcdef0"
IAM_ROLE="your-iam-role"
KEYPAIR="your-keypair-name"

echo "▶ Stopping old instance..."
aws ec2 stop-instances --instance-ids $INSTANCE_ID --region $REGION
aws ec2 wait instance-stopped --instance-ids $INSTANCE_ID --region $REGION
echo "✓ Instance stopped"

echo "▶ Creating AMI..."
AMI_ID=$(aws ec2 create-image \
  --instance-id $INSTANCE_ID \
  --name "migration-$(date +%Y%m%d-%H%M%S)" \
  --region $REGION \
  --query 'ImageId' \
  --output text)
echo "✓ AMI created: $AMI_ID"

echo "▶ Waiting for AMI to be available..."
aws ec2 wait image-available --image-ids $AMI_ID --region $REGION

echo "▶ Launching m7i-flex.large..."
NEW_INSTANCE=$(aws ec2 run-instances \
  --image-id $AMI_ID \
  --instance-type m7i-flex.large \
  --key-name $KEYPAIR \
  --security-group-ids $SECURITY_GROUP \
  --iam-instance-profile Name=$IAM_ROLE \
  --region $REGION \
  --query 'Instances[0].InstanceId' \
  --output text)
echo "✓ New instance: $NEW_INSTANCE"

aws ec2 wait instance-running --instance-ids $NEW_INSTANCE --region $REGION

NEW_IP=$(aws ec2 describe-instances \
  --instance-ids $NEW_INSTANCE \
  --query 'Reservations[0].Instances[0].PublicIpAddress' \
  --region $REGION \
  --output text)

echo ""
echo "✅ Migration complete!"
echo "   New instance: $NEW_INSTANCE"
echo "   Public IP:    $NEW_IP"
echo "   SSH:          ssh -i $KEYPAIR.pem ec2-user@$NEW_IP"
echo ""
echo "⚠️  Test for 24h, then terminate old instance:"
echo "   aws ec2 terminate-instances --instance-ids $INSTANCE_ID --region $REGION"

chmod +x migrate.sh
./migrate.sh

• Instance type confirmed as m7i-flex.large
• RAM shows ~8 GB (free -h)
• All services running (Docker / systemd / Celery)
• API endpoints respond correctly
• Celery tasks execute and complete
• Database connections established
• File uploads / downloads work
• Elastic IP / DNS routing updated
• No errors in logs for 24+ hours
• Old instance terminated

# In your infrastructure config folder
git init
git add .
git commit -m "Initial: t3.micro production config"

# After migration
git commit -m "Migrated t3.micro → m7i-flex.large for ML workloads"