# 1. EC2 인스턴스 ID 조회 (ASG 교체 대비 — 매번 다시 조회 필수)
INSTANCE_ID=$(aws ec2 describe-instances \
  --filters  " Name=tag:Environment,Values=production "   \
             " Name=instance-state-name,Values=running "   \
  --query  ' Reservations[0].Instances[0].InstanceId '   --output text)

# 2. DB 연결 정보 확인 (컨테이너 내부)
aws ssm send-command --instance-ids $INSTANCE_ID \
  --document-name  " AWS-RunShellScript "   \
  --parameters  ' commands=[ " docker exec kobic-server cat config/production.yaml | grep -A6 \ " ^database:\ " " ] ' 

 # 3. postgres 이미지 pre-pull (이미지 다운로드에 시간 걸리면 send-command 타임아웃)
aws ssm send-command --instance-ids $INSTANCE_ID \
  --document-name  " AWS-RunShellScript "   \
  --parameters  ' commands=[ " docker pull postgres:15-alpine " ] ' 

 # 4. psql 쿼리 실행
aws ssm send-command --instance-ids $INSTANCE_ID \
  --document-name  " AWS-RunShellScript "   \
  --parameters  ' commands=[ " docker run --rm --network host -e PGPASSWORD= < password >   postgres:15-alpine psql -h  < db-host >   -U postgres -d serverpod -c \ " < SQL > \ " " ] '

CMD_ID=$(...)  # send-command 반환값

until aws ssm get-command-invocation \
  --command-id $CMD_ID --instance-id $INSTANCE_ID \
  --query  ' Status '   --output text | grep -qE  " ^(Success|Failed)$ " ; do
  sleep 3
done

aws ssm get-command-invocation --command-id $CMD_ID \
  --instance-id $INSTANCE_ID \
  --query  ' [Status,StandardOutputContent] '   --output text

RedisError(WRONGPASS invalid username-password pair or user is disabled)

# SSM 파라미터 최종 변경일
aws ssm describe-parameters \
  --parameter-filters  " Key=Name,Values=/kobic/staging/redis/auth-token "   \
  --query  ' Parameters[0].[LastModifiedDate,Version] '   --output text

# ElastiCache AUTH 최종 변경일
aws elasticache describe-replication-groups \
  --replication-group-id kobic-staging \
  --query  ' ReplicationGroups[0].AuthTokenLastModifiedDate '   --output text

# 1. SSM에서 AUTH 토큰 조회
TOKEN=$(aws ssm get-parameter \
  --name /kobic/staging/redis/auth-token --with-decryption \
  --query  ' Parameter.Value '   --output text)

# 2. ElastiCache AUTH ROTATE
aws elasticache modify-replication-group \
  --replication-group-id kobic-staging \
  --auth-token  " $TOKEN "   \
  --auth-token-update-strategy ROTATE \
  --apply-immediately

# 3. 완료 확인 (PendingAuthTokenStatus: None, Status: available)
aws elasticache describe-replication-groups \
  --replication-group-id kobic-staging \
  --query  ' ReplicationGroups[0].{Status:Status,PendingAuthTokenStatus:PendingModifiedValues.AuthTokenStatus} ' 

 # 4. 컨테이너 재시작 — 필수 (기존 connection 캐시가 old token 유지)
aws ssm send-command --instance-ids  < INSTANCE_ID >   \
  --parameters  ' commands=[ " docker restart kobic-server " ] '

# 1. RDS 인스턴스 상태 확인
aws rds describe-db-instances \
  --db-instance-identifier kobic-staging \
  --query  ' DBInstances[0].{Status:DBInstanceStatus,Storage:AllocatedStorage,MaxStorage:MaxAllocatedStorage,FreeStorage:FreeStorageSpace} ' 

 # 2. FreeStorageSpace 메트릭 확인 (최근 1시간)
aws cloudwatch get-metric-statistics \
  --namespace AWS/RDS \
  --metric-name FreeStorageSpace \
  --dimensions Name=DBInstanceIdentifier,Value=kobic-staging \
  --start-time $(date -u -v-1H +%Y-%m-%dT%H:%M:%S) \
  --end-time $(date -u +%Y-%m-%dT%H:%M:%S) \
  --period 300 --statistics Minimum \
  --output table

# 3. 스토리지 사용 원인 분석 (DB 접속 후)
SELECT pg_size_pretty(pg_database_size( ' serverpod ' )) as db_size;

-- 테이블별 용량 확인
SELECT schemaname, tablename,
       pg_size_pretty(pg_total_relation_size(schemaname|| ' . ' ||tablename)) as total_size
FROM pg_tables
WHERE schemaname =  ' public ' 
 ORDER BY pg_total_relation_size(schemaname|| ' . ' ||tablename) DESC
LIMIT 20;

-- WAL 사이즈 확인
SELECT pg_size_pretty(pg_wal_size()) as wal_size;

# 긴급 스토리지 확장 (즉시 적용, 다운타임 없음)
aws rds modify-db-instance \
  --db-instance-identifier kobic-staging \
  --allocated-storage 200 \
  --max-allocated-storage 500 \
  --apply-immediately

# 확장 진행 상태 확인 (storage-optimization 상태가 됨)
aws rds describe-db-instances \
  --db-instance-identifier kobic-staging \
  --query  ' DBInstances[0].DBInstanceStatus '

-- replication slot 상태 확인
SELECT slot_name, slot_type, active,
       pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn)) as retained_wal
FROM pg_replication_slots;

-- 비활성 slot 삭제 (ClickHouse ClickPipe 연결 끊긴 경우)
SELECT pg_drop_replication_slot( ' slot_name_here ' );

# CodeDeploy Deployment Group의 ASG 목록 확인
aws deploy get-deployment-group \
  --application-name kobic-app \
  --deployment-group-name kobic-staging-dg \
  --query  ' deploymentGroupInfo.autoScalingGroups[].name ' 

 # 실제 존재하는 ASG 확인
aws autoscaling describe-auto-scaling-groups \
  --query  ' AutoScalingGroups[?contains(AutoScalingGroupName, `kobic`)].AutoScalingGroupName '

# 올바른 ASG만 포함하도록 Deployment Group 업데이트
aws deploy update-deployment-group \
  --application-name kobic-app \
  --current-deployment-group-name kobic-staging-dg \
  --auto-scaling-groups  " kobic-staging-asg "    # 현재 유효한 ASG만 지정

# 1. Colima 강제 종료
colima stop --force

# 2. 락 파일 제거
rm -f ~/.colima/default/diffdisk  # 또는 해당 프로파일 경로
rm -f ~/.lima/colima/diffdisk

# 3. QEMU 프로세스 정리
pkill -f qemu-system

# 4. 재시작
colima start

colima delete
colima start --cpu 4 --memory 8 --disk 60

GitHub Actions → Docker Build → ECR Push → CodeDeploy → ASG Instance

{env}-{shortSha}-{timestamp}
예: production-8023d1ba-20260418005915
    staging-87eec5a2-20260418084056

# 1. 최신 CodeDeploy 배포 ID 조회
aws deploy list-deployments \
  --application-name kobic-app \
  --deployment-group-name kobic-production-group \
  --max-items 1 \
  --query  ' deployments[0] '   --output text

# 2. 배포 상태 확인 (Succeeded 인지)
aws deploy get-deployment --deployment-id  < id >   \
  --query  ' deploymentInfo.{Status:status,CompleteTime:completeTime} ' 

 # 3. 현재 서비스 중인 EC2 인스턴스 조회 (Blue/Green이면 새 ASG)
aws autoscaling describe-auto-scaling-groups \
  --query  ' AutoScalingGroups[?contains(AutoScalingGroupName, `production`)].{Name:AutoScalingGroupName,ID:Instances[0].InstanceId} ' 

 # 4. 실행 중 컨테이너 이미지 확인 (SSM send-command)
aws ssm send-command --instance-ids  < id >   \
  --document-name  " AWS-RunShellScript "   \
  --parameters  ' commands=[ " docker ps --format \ " { { .Image } }   { { .Status } } \ "   | grep kobic " ] '   \
  --query  ' Command.CommandId '   --output text

# 5. 결과 확인 (명령 실행 후 ~6초 대기)
aws ssm get-command-invocation \
  --command-id  < command-id >   --instance-id  < id >   \
  --query  ' StandardOutputContent '   --output text

# 최근 30분 IAP 관련 로그
aws ssm send-command --instance-ids  < id >   \
  --document-name  " AWS-RunShellScript "   \
  --parameters  ' commands=[ " docker logs $(docker ps --format \ " { { .ID } } \ "   | head -1) --since 30m 2 > & 1 | grep -E \ " \\[IAP\\]|App Store\ "   | tail -40 " ] '

1. RDS 상태 확인 (storage-full이 가장 흔한 원인)
   ↓
2. EC2/ASG 인스턴스 상태 확인
   ↓
3. Target Group 헬스체크 확인
   ↓
4. ALB 접근 로그 확인
   ↓
5. CodeDeploy 배포 상태 확인
   ↓
6. CloudWatch 로그 확인

# RDS 상태
aws rds describe-db-instances \
  --query  ' DBInstances[*].{ID:DBInstanceIdentifier,Status:DBInstanceStatus,Storage:AllocatedStorage} '   \
  --output table

# ASG 인스턴스 상태
aws autoscaling describe-auto-scaling-groups \
  --query  ' AutoScalingGroups[?contains(AutoScalingGroupName,`kobic`)].{Name:AutoScalingGroupName,Desired:DesiredCapacity,Instances:Instances[*].{ID:InstanceId,Health:HealthStatus } } '   \
  --output json

# Target Group 헬스
aws elbv2 describe-target-health \
  --target-group-arn  < target-group-arn >   \
  --output table

# 최근 배포 상태
aws deploy list-deployments \
  --application-name kobic-app \
  --deployment-group-name kobic-staging-dg \
  --max-items 3 \
  --query  ' deployments '