Terminal
Terminal/Skill
Grades an Amazon EKS cluster against best practices across nine pillars, returning PASS, FAIL and N/A scorecards with prioritized fixes.
By Amazon Web Services
Works with
npx skills add aws/tools-for-devops-agent --skill aws-eks-operations-reviewThis skill performs comprehensive graded operational reviews with 288 checks across 9 pillars. For quick health checks during active incidents, use incident investigation skills instead — this review is heavyweight and best suited for proactive assessments.
A full review is heavyweight and may require many read-only tool calls; duration varies with cluster size, API responsiveness, permissions, and telemetry availability. A targeted review grades only the named unit plus required AX evidence. The 49 discovery areas collect evidence; the 288 core rows are grading items across nine pillars plus AWS API/Insights. Per-unit counts and exact ID membership live in references/runtime/check-manifest.md; read them there each run.
use_kubectl: get, describe, logs, version, config current-context, cluster-info, top, and get --raw, one command per tool call. Results stay transient in conversation; never write them to a file, object store, or Amazon S3. Customer-account AWS reads use audited read-only DevOps Agent access, never local AWS CLI/boto3 credentials. Remediations are proposals for human approval, never mutations.Keep in current context only: confirmed identity/scope/window; 49 area statuses and bounded projections; source attempts; gate decisions; selected/completed units; exact verdicts; FAIL evidence, descriptive severity, canonical resource ID, fingerprint, and remediation route; reference-load audit; QA result; next unit. Update after every area/unit and discard raw output. Stop and report evidence/completed work/retry requirement if the Kubernetes tool is unavailable, identity differs from the confirmed target, initial access fails, more than 30% of a discovery phase fails, or mutation/safety is attempted. Later isolated denial/timeout/optional-CRD gaps are N/A unless that threshold is crossed. For production, confirm timing before the broad read sweep. Never fetch Kubernetes Secret values. EKS control-plane hosts/etcd are AWS-managed: use only customer-visible APIs, logs, metrics, and Kubernetes behavior.
Work these steps in order; never start a step before the previous one is recorded in the ledger.
Confirm cluster, region, account, context, environment, namespace scope, event window, and production sweep approval. If targets are ambiguous, stop for selection.
Collect available topology, dependencies, recent investigations, alarms, and environment facts with provenance. They prioritize work but never replace discovery or grading evidence.
Run cheap read probes (version -o json, current context, cluster info, nodes), cross-check S0, and apply stop rules. Load references/docs/minimum-rbac.md only for an access-policy question or denial.
Load references/runtime/discovery-manifest.md, then use use_kubectl to execute references/kubectl-discovery-commands.md (1–27) and references/kubectl-discovery-commands-deep-dive.md (28–49) in order. Every area gets one complete|partial|n/a status. Reuse only named transient fetches with matching identity/scope/provenance and run each dependent extraction; CRD-specific probes stay separate. Apply fleet tiers and the independent 500+ pod rule, which prohibits whole-cluster pod JSON. Retain bounded projections only in conversation; never store results in Amazon S3 or a file.
Load references/runtime/inventory-schema.md. When telemetry applies, load references/runtime/metrics-thresholds.md and attempt required 7-day node/pod utilization, restarts, EC2 health, EKS request, log-pattern, alarm, and CloudTrail signals. Missing telemetry yields N/A plus the visibility finding. Keep a bounded in-context snapshot only.
Load references/runtime/router.md and references/runtime/cluster-gates.md; record every decision, then drop both. Named requests grade named units; full/CWR grades all nine pillars plus AX. Upgrade/migration or Extended Support fires the Upgrade unit and k8s-deprecated-apis.md; Windows fires when windows_nodes>0; Hybrid when hybrid_nodes>0; AI/ML when GPU or Neuron nodes exist; the manifest owns their exact IDs and counts. Otherwise record an explicit false-gate line and do not load the conditional. Auto Mode, IPv6, Fargate, CNI, mixed-OS, and EKS Anywhere gates change applicability, never membership.
Load references/runtime/grading-guards.md once. For each routed unit: load only its canonical definition; grade every ID with evidence and applicable guards; commit exact rows/totals/finding inputs to the ledger before the next unit; then identify FAIL IDs. Only after FAIL verdicts exist, consult references/remediations/index.md, load the mapped shard/playbook, and complete each finding. Load a decision tree only after its Pending/OOM/latency/429 signal and before asserting cause. Fingerprint = SHA256(account_id|region|cluster_name|check_id|canonical_resource_id). Drop unit/remediation/raw data before continuing. If AWS reads fail, AX rows are N/A; load references/docs/minimum-rbac.md for the required IAM actions; if telemetry fails, dependent rows are N/A; if control-plane logging is disabled, record the visibility FAIL and still attempt public metrics.
Load control-plane-health/metric-sources.md, detect sources, record/drop. If logging is enabled, sequentially load/run/record/drop queries-cp01-cp09.md, queries-cp10-cp13.md, and queries-cp14-cp18.md; load queries-cp19-cp25-diagnostics.md only for a matching signal. Always attempt public control-plane metrics, then load thresholds.md and pillars/control-plane.md to grade all 20 rows. Use procedures.md or decision-trees/api-latency-429.md only for unhealthy/ambiguous results; load only failed signal-family remediation and FAIL-only alert copy. Empty query results remain unknown until source, stream, delay, filters, and window are verified.
Load references/runtime/qa-checklist.md, references/runtime/check-manifest.md, and, for full/CWR, references/runtime/common-checks-coverage.md. Reconcile 49 area statuses; load audit; exact selected IDs/counts; namespaces; conditionals/gates; source attempts/fallbacks; every FAIL block; alarms; the eight mandatory report sections and their order; and direct-response/no-file compliance. Complete QA in context. On failure, repair the named state/ID/reference and rerun; do not finalize.
Load references/runtime/report-contract.md only now; it is the sole delivery authority and outranks any other report-format skill or remembered layout. Emit the entire review as one complete Markdown message with these headings, in this exact order, none omitted, renamed, reordered, or deferred:
# EKS Operations Review — {cluster} header block; 2. ## 1. Executive summary; 3. ## 2. Cluster snapshot; 4. ## 3. Prioritized action plan — every FAIL, Critical→Low; 5. ## 4. Detailed findings — one block per FAIL; 6. ## 5. Scorecards — every selected ID with verdict and bounded evidence; 7. ## 6. Recommended alarms — required for IDR/CWR, otherwise one skipped line; 8. ## 7. What was not assessed — every N/A ID with its exact reason; 9. ## 8. Appendix — scope, discovery coverage, source attempts, gates, reference-load audit, QA PASS.Sections 1–7 are the review; the appendix is bookkeeping, never a substitute. A section with nothing to report still appears with an explicit None line. Never split the review across messages or deliverables; when the runtime assembles one cumulative artifact by ordered appends, its final state must contain every section. Customer-facing text excludes internal tools, employee aliases, and internal incident severity numbers.
pending-pods.md, oomkilled.md, or api-latency-429.md only after its matching signal.queries-cp19-cp25-diagnostics.md only for a matching Control Plane signal.Under context pressure, finish the current area/unit, update the ledger, compress PASS/N/A detail, and discard raw output. Compression shortens evidence text only; S8 sections 1–7 are never dropped, merged, or postponed. If safe continuation is impossible, emit a conversational checkpoint with the last completed state/unit, exact completed/unassessed coverage, QA state, and next unit. Resume from the incomplete state only when the conversation still retains the ledger; otherwise recollect required evidence. If more than 30% of discovery failed, investigate access, permissions, throttling, or scope before retrying.
Do not finalize partial discovery, substitute AX1 for Control Plane, interpret missing sources as health, load false-gate conditionals, load remediation early, render before QA, or emit an appendix-only report body. Every FAIL must quote evidence/source/window, explain impact and descriptive severity, include human-approved mapped steps and an authoritative AWS/Kubernetes link, and preserve fingerprint/resource ID. Unmapped facts are Observations.