Monitor Amazon S3 with SigNoz

S3 Sync (One-Click)

S3 Sync uses EventBridge and Lambda to forward log files to SigNoz whenever new objects are created in your S3 buckets.

Use Cases

• Ingest ELB access logs stored in S3
• Ingest VPC Flow Logs stored in S3
• Ingest CloudTrail logs stored in S3
• Ingest any custom log files stored in S3

Setup

See the detailed guide: Sync Logs from S3 Buckets

This covers:

1. Installing the AWS Integration Agent
2. Enabling S3 Sync in the SigNoz UI
3. Configuring bucket and prefix filters

Manual Setup

S3 Storage Metrics

To collect S3 storage metrics, you can use the Prometheus CloudWatch Exporter. This tool scrapes metrics from AWS CloudWatch and exposes them in Prometheus format, which the OpenTelemetry Collector can then scrape and forward to SigNoz.

Prerequisites

Before proceeding, ensure you have:

• OpenTelemetry Collector installed and configured. See Get Started with OTel Collector.
• Java 11 or higher installed on the host machine (for JAR-based setup), or Docker (for container-based setup).
• AWS credentials configured via environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY), IAM role, or ~/.aws/credentials.
• IAM permissions for the credentials:
  • cloudwatch:ListMetrics
  • cloudwatch:GetMetricStatistics

Step 1: Create Configuration File

Create a file named s3-metrics.yaml with the following configuration:

region: <aws-region>
metrics:
  - aws_namespace: AWS/S3
    aws_metric_name: BucketSizeBytes
    aws_dimensions: [BucketName, StorageType]
    aws_statistics: [Average]

  - aws_namespace: AWS/S3
    aws_metric_name: NumberOfObjects
    aws_dimensions: [BucketName, StorageType]
    aws_statistics: [Average]

Replace the following:

• <aws-region>: Your AWS region where S3 buckets are located (e.g., us-east-1, eu-west-1, ap-south-1).

See example configurations for more service templates.

Step 2: Download and Run the Exporter

curl -LO https://repo1.maven.org/maven2/io/prometheus/cloudwatch/cloudwatch_exporter/0.16.0/cloudwatch_exporter-0.16.0-jar-with-dependencies.jar

java -jar cloudwatch_exporter-0.16.0-jar-with-dependencies.jar 9106 s3-metrics.yaml

docker run -d \
  --name cloudwatch-exporter \
  -p 9106:9106 \
  -v $(pwd)/s3-metrics.yaml:/config/config.yml \
  -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \
  prom/cloudwatch-exporter

Verify the exporter is running by checking the metrics endpoint:

curl http://localhost:9106/metrics | grep aws_s3

You should see metrics like aws_s3_bucket_size_bytes_average, aws_s3_number_of_objects_average, etc.

Step 3: Configure OpenTelemetry Collector

Add the following prometheus receiver to your existing otel-collector-config.yaml to scrape the CloudWatch Exporter:

receivers:
  prometheus:
    config:
      scrape_configs:
        - job_name: 's3-cloudwatch'
          scrape_interval: 60s
          static_configs:
            - targets: ['<exporter-host>:9106']

Replace the following:

• <exporter-host>: The hostname or IP where the CloudWatch Exporter is running. Use localhost if running on the same machine.

Enable the prometheus receiver in your metrics pipeline by updating the service section:

service:
  pipelines:
    metrics:
      receivers: [otlp, prometheus]
      processors: [batch]
      exporters: [otlp]

Restart your OpenTelemetry Collector to apply the changes.

Validate

To confirm that S3 metrics are flowing to SigNoz:

1. Navigate to Dashboards → New Dashboard → New Panel in SigNoz.
2. In the query builder, search for metrics starting with aws_s3_ (e.g., aws_s3_bucket_size_bytes_average).
3. Verify that metrics appear with bucket_name labels matching your S3 buckets.

If you see metrics with labels like bucket_name, your setup is working correctly.

Log File Ingestion

For ingesting log files from S3, use the S3 Lambda Forwarder pattern described in:

• RDS Logs
• VPC Flow Logs
• ELB Logs