Menü
Deep network diagnosis for AWS/EKS: VPC CNI, load balancers, DNS
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | ops-network-diagnosis |
| description | Deep network diagnosis for AWS/EKS: VPC CNI, load balancers, DNS |
| triggers | ["network issue","네트워크 오류","연결 문제","connectivity","DNS failure"] |
| model | sonnet |
| allowed-tools | ["Bash","Read","Grep"] |
Deep network diagnostics for VPC CNI, load balancers, and DNS in EKS environments.
Route to appropriate reference for detailed commands and decision trees.
Test connectivity end-to-end after applying fixes.
graph TD
A[Network Issue Reported] --> B{Pod-to-Pod works?}
B -->|No| C{Same node?}
C -->|Yes| D[Check CNI plugin / iptables]
C -->|No| E{Same subnet?}
E -->|Yes| F[Check Security Groups / NACLs]
E -->|No| G[Check VPC routing / peering]
B -->|Yes| H{Service DNS resolves?}
H -->|No| I[Check CoreDNS pods / config]
H -->|Yes| J{External access works?}
J -->|No| K[Check NAT Gateway / IGW]
J -->|Yes| L[Check Load Balancer / Ingress]
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
dial tcp: i/o timeout | Security group blocks port | Add inbound rule for target port |
no route to host | Missing VPC route | Check route table for destination CIDR |
NXDOMAIN on service | CoreDNS not running | kubectl rollout restart -n kube-system deploy/coredns |
connection refused | Service port mismatch | Verify targetPort matches container port |
| IP exhaustion warnings | Subnet CIDR too small | Enable prefix delegation or add subnets |
504 Gateway Timeout | Target group unhealthy | Check health check path and security groups |
# Check available IPs per subnet
aws ec2 describe-subnets --filters "Name=vpc-id,Values=$VPC_ID" \
--query 'Subnets[].{SubnetId:SubnetId,AZ:AvailabilityZone,AvailableIPs:AvailableIpAddressCount,CIDR:CidrBlock}'
# Check ENI allocation per node
kubectl get nodes -o json | jq '.items[] | {name:.metadata.name, enis:.status.addresses | length}'
# Enable prefix delegation
kubectl set env daemonset aws-node -n kube-system ENABLE_PREFIX_DELEGATION=true
# Pod-to-pod
kubectl exec -it <pod1> -- curl -s <pod2-ip>:<port>
# Pod-to-service
kubectl exec -it <pod> -- curl -s <service>.<namespace>.svc.cluster.local:<port>
# DNS resolution
kubectl exec -it <pod> -- nslookup <service>.<namespace>.svc.cluster.local
# External connectivity
kubectl exec -it <pod> -- curl -s -o /dev/null -w "%{http_code}" https://aws.amazon.com
## Network Diagnosis Report
**Issue**: [Brief description]
**Layer**: L3/L4/L7/DNS
**Severity**: P1/P2/P3
### Findings
- [Finding 1 with evidence]
- [Finding 2 with evidence]
### Root Cause
[Explanation with supporting data]
### Resolution
1. [Step with command]
2. [Verification command + expected output]
### Prevention
- [Recommended configuration change]
references/vpc-cni-troubleshooting.md — IP management, ENI, prefix delegationreferences/load-balancer-troubleshooting.md — ALB/NLB setup, target healthreferences/dns-troubleshooting.md — CoreDNS, Route 53, resolution issuesCollaborate with other AI agents (Kiro CLI, the peer host CLI, and Agy) for a second opinion. Multi-AI review of code/architecture, decision support when you're unsure, and ADR co-authoring, plus autonomous consensus/harness pipelines. The current host chairs and synthesizes the final answer. 멀티 AI 협업: 리뷰, 의사결정 보조, ADR 협업.
Claude plans and verifies, Kiro CLI implements on its own flat-rate subscription credits — a cost-savings implementation-delegation workflow, not a second opinion (see co-agent for that). Kiro implements inside an isolated git worktree; only the captured, scope-guarded diff ever reaches the main tree. Triggers on 'kiro한테 시켜서 구현', 'kiro로 구현', 'kiro한테 구현 위임', 'delegate implementation to kiro', 'kiro implement this'. For read-only review of a diff, use the /kiro:review command instead — this skill is write-capable (it commits) and deliberately does NOT own review triggers.
AWS Workshop Studio 프로젝트 구조 생성 및 콘텐츠 작성 스킬. "워크샵 만들어", "workshop init", "랩 작성" 요청 시 활성화
After creating a PR, poll for AI and human review feedback, auto-fix issues, and push (max 3 iterations)
Create a single-page, responsive online brochure (landing page) for an AWS solution, product, or platform as one self-contained HTML file — editorial design, hero + value + features + embedded architecture diagram + CTA, deployed publicly via GitHub Pages. Use whenever the user wants a brochure, landing page, marketing one-pager, product overview page, solution showcase, '온라인 브로셔', '브로셔 만들어', '랜딩 페이지', '소개 페이지', or wants to present a cloud product's value and architecture on the web — even if they don't say the word 'brochure'. Not for slide decks (use reactive-presentation) or multi-page docs sites (use gitbook).
Create dynamic animated SVG diagrams with SMIL animations for AWS architecture traffic flow, service interactions, and deployment pipelines. Use when creating animated or dynamic diagrams.