AWS Observability and Cost Readiness

When to use

Invoke when making an AWS workload or account observable and cost-governed for production — metrics/logs/traces, SLO dashboards and alarms, budgets, anomaly detection, FinOps tagging, and commitment posture — or auditing an inherited account that is unmonitored or financially opaque.

Do not use for: AWS Organizations/account topology or the mandatory tag-policy enforcement (use aws-account-and-organization-topology); VPC/IAM/KMS foundation (use aws-network-and-identity-foundation); compute selection and deployment (use aws-workload-runtime-and-deployment); multi-region/DR (use aws-dr-and-multi-region-readiness); IaC module/state/plan/apply mechanics (the terraform Family H skills).

Inputs

Required:

• A deployed runtime from aws-workload-runtime-and-deployment (the compute/LB/data this skill instruments) within the account topology.
• Approved architecture/operations decisions on the observability substrate, alert destinations, and runbook hooks, or explicit confirmation they are intentionally deferred.

Optional: