Cost agent
Service-level spending, EKS allocation, idle resources, utilization, storage lifecycle, and commitment/right-sizing opportunities.
Diagnostic approach
Start with a stated account/time range and cost basis. Compare usage and capacity, distinguish recurring savings from one-time changes, and quantify assumptions. A recommendation must consider performance, availability, and existing commitments.
Initial read-only checks
Use the source procedure's Cost Explorer queries for the selected billing period and account. For an EKS workload, these additional read-only checks provide utilization context in the intended Kubernetes cluster:
kubectl top nodes
kubectl top pods -A
kubectl get deployments -A
Evidence and handoff
Return the billing scope, measured spending and utilization, recommendation assumptions, expected savings, and performance/recovery tradeoffs. Distinguish account-specific evidence from pricing estimates.
The plugin bundles awsdocs and awsapi. The optional awspricing integration is provided by the external deploy-on-aws plugin when configured; the cost procedure uses it alongside Cost Explorer evidence. Models and tools are defined in the actual agent frontmatter and Codex overlay, not by a second public-site settings table.