Integration · Clouds
AWS
EC2 / ECS / EKS / Lambda via CloudWatch plus native agents.
What gets collected
A CloudWatch metrics importer for the baseline, native agents on EC2/ECS/EKS for high cardinality, and a Lambda extension for function-level metrics.
Requirements
- ✓IAM: cloudwatch:GetMetricData
- ✓IAM: cloudwatch:ListMetrics
- ✓native agent on EC2/EKS (optional)
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
ec2.cpuec2.statusecs.task.countlambda.durationlambda.errorscloudwatch.*Setup steps
- 1IAM role with cloudwatch:GetMetricData
- 2AWS_REGION + AWS_PROFILE in the agent env
- 3Lambda extension layer for functions
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
AWS
Frequently asked questions
- What does Unimoni collect from AWS?
- EC2 / ECS / EKS / Lambda via CloudWatch plus native agents. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across AWS and everything else in one place.
- How long does it take to connect AWS?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the AWS integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is AWS monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.