slug: amazon-cloudwatch
provider: Amazon CloudWatch
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Metrics
  spec_file: amazon-cloudwatch-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: '"Publish metric data points", "Get statistics for a metric", "List available metrics"'
  reason: Publishing and querying operational metrics is core observability management (logs, metrics,
    traces) for the running service.
- tag: Alarms
  spec_file: amazon-cloudwatch-alarms-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.82
  evidence: '"Create or update a metric alarm" ... "create alarms that send notifications, and automatically
    react to changes in your AWS resources"'
  reason: CloudWatch alarms are monitoring/observability alerting over metrics for running services, i.e.
    Observability Management (not financial-crime or business alerting). Some ambiguity vs IT Operations
    Monitoring (BC-600.40), but the vendor is explicitly an observability platform.
- tag: Dashboards
  spec_file: amazon-cloudwatch-dashboards-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: '"Create or update a dashboard", "List dashboards" within "a monitoring and observability
    service that collects metrics, logs, and events"'
  reason: Dashboards here are observability dashboards over metrics, part of making the running service
    understandable in production. Slightly thin, as dashboards could be read as BI reporting, but context
    is monitoring.