Amazon EKS upgrade triage

EKS Extended Support Exit Planner

Runs locally in this browser for the MVP; do not paste AWS credentials, kubeconfigs, or production secrets.

Working planner

Paste EKS fleet evidence

0 characters Pasted evidence stays in browser memory. Copied artifacts are redacted.

Optional manual cluster row

Support timeline

Embedded EKS minor-version windows

Cluster findings

Detected, inferred, and missing evidence

Cluster Region / account Version Support status Deadline Severity Why it matters Next action
Run a scan to populate cluster findings.

Multi-account fleet workbook

Owner-led action groups

Run a scan to group local cluster evidence into owner, environment, version-band, and first-action rows.

Detected accounts
0
Owners
0
Environments
0
Action groups
0

Swipe the table horizontally to inspect accounts, regions, and open gaps.

Owner Environment Version band First action Clusters Accounts Regions Open gaps
No workbook rows yet. Paste or load fleet evidence, then scan.

Planning ledger only. Account IDs, ARNs, bearer tokens, emails, and obvious secret-like values are redacted from copied workbook outputs.

Missing evidence

Follow-up inventory gaps

Ordered upgrade plan

Next work sequence

    Copyable artifact preview

    Upgrade handoff text

    Run a scan to generate redacted EKS upgrade triage text.

    Consultant report preview

    Client-ready EKS upgrade triage report

    Unavailable until the planner has usable cluster findings.

    Run a scan with EKS cluster and Kubernetes version evidence to generate the consultant-ready report.