AWS Infrastructure Monitoring

Complete visibility into your AWS infrastructure. Monitor EC2 instances, RDS databases, Lambda functions, containers, and all AWS services from a single unified platform.

Monitor All AWS Services

EC2 Instances

Monitor CPU, memory, disk, and network metrics. Auto-discover instances with tags.

  • CPU and memory utilization
  • Disk I/O and space
  • Network traffic
  • System and application logs

RDS Databases

Deep database monitoring for MySQL, PostgreSQL, Aurora, and more.

  • Query performance
  • Connection counts
  • Replication lag
  • Storage utilization

Lambda Functions

Track serverless function invocations, duration, and errors.

  • Invocation counts
  • Execution duration
  • Error rates
  • Cold start tracking

ECS & EKS

Container and Kubernetes monitoring with pod-level visibility.

  • Container metrics
  • Pod health status
  • Service discovery
  • Resource allocation

Load Balancers

Monitor ALB, NLB, and Classic load balancer performance.

  • Request rates
  • Response times
  • Healthy target counts
  • Error rates

CloudWatch Integration

Seamless integration with AWS CloudWatch metrics and logs.

  • Native CloudWatch metrics
  • Custom metrics
  • Log aggregation
  • Cost optimization insights

AWS Monitoring Features

๐Ÿš€ Auto-Discovery

Automatically discover and monitor EC2 instances, RDS databases, and containers based on tags and filters.

๐Ÿ“Š Unified Dashboards

View your entire AWS infrastructure on customizable dashboards with real-time updates.

๐Ÿ”” Smart Alerts

Get intelligent alerts when AWS resources exceed thresholds or behave abnormally.

๐Ÿ’ฐ Cost Tracking

Track AWS spending and correlate costs with resource utilization for optimization.

๐Ÿ”’ Multi-Account Support

Monitor multiple AWS accounts from a single pane of glass with role-based access.

๐Ÿ“ˆ Trend Analysis

Identify usage patterns and capacity planning opportunities with historical data.

โ˜๏ธ CloudWatch Integration

Native integration with AWS CloudWatch for comprehensive metrics collection without additional configuration.

๐Ÿณ Container Monitoring

Monitor ECS and EKS containers alongside EC2 instances for complete visibility into your containerized workloads.

Easy Setup

1

Install Bleemeo Agent

Deploy our lightweight agent on EC2 instances via user data or configuration management tools.

wget -qO- 'https://get.bleemeo.com?accountId=<your_account_id>&registrationKey=<your_registration_key>' | sh
2

Configure CloudWatch

Connect your AWS account for CloudWatch metrics integration (optional but recommended).

3

Start Monitoring

Instances are auto-discovered and monitoring begins immediately. Customize dashboards and alerts.

Why Choose Bleemeo for AWS?

Better Than CloudWatch Alone

Combine CloudWatch metrics with agent-based monitoring for complete visibility into OS and application metrics.

Multi-Cloud Ready

Monitor AWS alongside Azure, GCP, and on-premise infrastructure in one platform.

No Vendor Lock-In

Own your monitoring data. Export metrics anytime. Switch providers without losing history.

Faster Troubleshooting

Correlate infrastructure metrics with application logs for rapid root cause analysis.

Want to go further?

Read the Documentation

Frequently Asked Questions

Everything you need to know about Bleemeo's AWS monitoring

What AWS services can Bleemeo monitor?

Bleemeo can monitor a wide range of AWS services through CloudWatch integration. This includes: EC2 instances (CPU, memory, disk I/O, network), RDS databases (MySQL, PostgreSQL, Aurora), DynamoDB tables, S3 buckets (object count, storage size), ELB/ALB/NLB load balancers, ECS and EKS containers. You also get cost metrics from AWS Cost Explorer.

How does Bleemeo integrate with AWS?

Bleemeo integrates with AWS in two complementary ways: CloudWatch integration pulls metrics directly from AWS APIs using IAM credentials you provide, and the Glouton agent can be installed on EC2 instances for deeper OS and application-level metrics. The CloudWatch integration requires read-only IAM permissions (like cloudwatch:GetMetricStatistics, ec2:DescribeInstances). We recommend using both for complete visibility.

Do I need to install an agent on EC2 instances?

It depends on your needs. CloudWatch integration alone provides basic metrics (CPU, network, disk I/O) without installing anything. However, installing the Glouton agent on EC2 instances gives you more detailed metrics including memory usage (not available in CloudWatch), per-process metrics, application-specific metrics, and log collection. The agent deployment can be automated via user data scripts.

Does Bleemeo AWS monitoring add to my AWS costs?

Yes, there are minimal AWS API costs for CloudWatch metric retrieval. Estimated costs: EC2 ~$0.70/month per instance, RDS ~$2.64/month per database, DynamoDB ~$1.76/month per table, ELB ~$1.76/month per load balancer, S3 less than $0.01/month per bucket. AWS provides a $10/month CloudWatch free tier that covers many use cases. Cost Explorer metrics add ~$1.24/month per account.

What IAM permissions does Bleemeo need?

Bleemeo requires read-only permissions to access AWS resources and metrics. The core permissions include cloudwatch:GetMetricStatistics for metrics and ec2:DescribeRegions for region discovery. Each service adds specific describe permissions (e.g., ec2:DescribeInstances, rds:DescribeDBInstances). For cost metrics, you need Cost Explorer permissions. We provide detailed IAM policies in our documentation for each service.

Can I monitor multiple AWS accounts?

Yes, Bleemeo supports multi-account monitoring. You can configure multiple AWS integrations with different IAM credentials, one for each AWS account. All resources from all accounts appear in your Bleemeo dashboard, allowing you to monitor your entire AWS organization from a single pane of glass. You can also use role-based access control in Bleemeo to manage who sees which accounts.

How does Bleemeo compare to CloudWatch alone?

Bleemeo enhances CloudWatch in several ways: Longer retention (13 months vs CloudWatch's standard 15 days for detailed metrics), unified dashboards combining AWS metrics with on-premise resources, deeper OS metrics (memory, processes) via the agent, simpler alerting without complex CloudWatch alarm configuration, and the ability to correlate metrics with logs in one platform.

Can I monitor ECS and EKS containers?

Yes, Bleemeo provides container-level monitoring for both ECS and EKS. For ECS, you can monitor task and container metrics through CloudWatch integration. For EKS, deploying Glouton via Helm provides comprehensive Kubernetes monitoring including pod, container, and cluster-level metrics. You get automatic service discovery, pod health tracking, and resource allocation visibility.

Does Bleemeo track AWS costs?

Yes, through the AWS Cost Explorer integration, Bleemeo can track: daily costs, current monthly costs, cost forecasts for end of month, and Savings Plans utilization and coverage. These metrics appear in your dashboards alongside resource metrics, helping you correlate spending with utilization and identify optimization opportunities.

Can I monitor hybrid AWS and on-premise infrastructure?

Yes, this is one of Bleemeo's key strengths. You can monitor AWS resources via CloudWatch, EC2 instances with Glouton agent, and on-premise servers all in the same platform. Dashboards can combine metrics from all sources, allowing you to see your entire infrastructure - cloud and on-premise - in unified views. This is ideal for hybrid deployments and migration projects.

Start Monitoring Your AWS Infrastructure

Get complete visibility into your AWS environment in minutes.