Back to Integrations
AWS CloudWatch

AWS CloudWatch

Integration Documentation

Documentation

AWS CloudWatch Integration

Overview

AWS CloudWatch provides monitoring and observability for your AWS resources and applications. This integration allows you to collect metrics, logs, and events from CloudWatch and correlate them with security events in Bloo.

Prerequisites

  • AWS account with CloudWatch enabled
  • IAM permissions to access CloudWatch metrics and logs
  • Bloo platform access credentials
  • Configuration Steps

    1. Enable CloudWatch Monitoring

  • Sign in to the AWS Management Console
  • 2. Navigate to CloudWatch service

    3. Ensure monitoring is enabled for your resources

    4. Set up log groups for your applications

    2. Create IAM Role

    Create an IAM role with the following permissions:

    {

    "Version": "2012-10-17",

    "Statement": [

    {

    "Effect": "Allow",

    "Action": [

    "cloudwatch:GetMetricData",

    "cloudwatch:ListMetrics",

    "logs:DescribeLogGroups",

    "logs:FilterLogEvents",

    "logs:GetLogEvents"

    ],

    "Resource": "*"

    }

    ]

    }

    3. Configure Bloo Integration

  • Log into your Bloo platform dashboard
  • 2. Navigate to Integrations > AWS CloudWatch

    3. Click "Configure Integration"

    4. Enter your AWS credentials and region

    5. Select the metrics and log groups to monitor

    6. Test the connection and save

    Supported Metrics

  • EC2 Metrics: CPU, memory, network, disk usage
  • RDS Metrics: Database performance and health
  • Lambda Metrics: Function execution and errors
  • Custom Metrics: Application-specific metrics
  • Log Monitoring

    Configure log monitoring for:

  • Application logs
  • System logs
  • Security logs
  • Access logs
  • Alerting Configuration

    Set up alerts for:

  • High resource utilization
  • Error rate thresholds
  • Performance degradation
  • Security events
  • Best Practices

  • Use detailed monitoring for critical resources
  • 2. Set up appropriate log retention policies

    3. Configure alarms for important metrics

    4. Regularly review and optimize monitoring costs