CloudWatch Metric Stream, Review Cost
Metric streams bill per metric update streamed, so a stream configured for all namespaces bills for every metric the account produces whether or not anything consumes it.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Review the CloudWatch metric stream. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- CloudWatch Metric Streams on AWS
- The fix, by hand
- CloudWatch → Metric streams → the resource → review included namespaces.
- Add Exclude filters for namespaces you don't actually need downstream (every AWS service emits to CloudWatch; you rarely need them all).
- Confirm the Kinesis Data Firehose destination is healthy (Firehose → DeliveryStream → Monitoring → IncomingBytes).
- If the downstream observability platform no longer ingests this stream: Actions → Delete metric stream.
- Metric streams charge per metric update. Namespace filtering is the dominant cost lever.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-177- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.