CloudWatch
Metrics publish/query, alarms, composite alarms.
Quick start
import boto3
cw = boto3.client("cloudwatch", endpoint_url="http://localhost:4566",
region_name="us-east-1",
aws_access_key_id="test", aws_secret_access_key="test")
cw.put_metric_data(Namespace="App", MetricData=[{"MetricName":"hits","Value":1}])
Supported operations
20 operations exposed by this service as of MiniStack 1.3.14. Extracted directly from the handler dispatch in the source module.
DeleteAlarms
DeleteDashboards
DescribeAlarmHistory
DescribeAlarms
DescribeAlarmsForMetric
DisableAlarmActions
EnableAlarmActions
GetDashboard
GetMetricData
GetMetricStatistics
ListDashboards
ListMetrics
ListTagsForResource
PutCompositeAlarm
PutDashboard
PutMetricAlarm
PutMetricData
SetAlarmState
TagResource
UntagResource
CloudFormation
The CloudFormation engine provisions these resource types via this service:
AWS::CloudWatch::Alarm
See CloudFormation engine for intrinsic support and lifecycle details.
Known limitations
- AlarmActions (SNS/Lambda) are stored but never fired on state transition.
- Composite alarm evaluation is stubbed — alarms stay INSUFFICIENT_DATA.
- Metric store is not AccountScopedDict — data can bleed across accounts.
Source
ministack/services/cloudwatch.py:300-360
Read the source to verify the ops list above — dispatch tables and handler functions are the ground truth.