Amazon ELB Classic

Ensure your logs are being sent to an S3 bucket. The following guide from Amazon will help you achieve this if you are not doing this already:

ELB classic to s3

The following permissions applied to the AWS IAM Policy being used:

• s3:ListBucket to check if the S3 bucket exists and list objects in it.
• s3:GetObject to check object metadata and download objects from S3 buckets.

Below is how your permissions should appear:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "SidID",
            "Effect": "Allow",
            "Action": [
                "s3:GetObject",
                "s3:ListBucket"
             ],
            "Resource": [
                "arn:aws:s3:::your-bucket/*"
            ]
        }
    ]
 }

To start sending logs and metrics from AWS to your Stack you need to configure an AWS Input on your Logit.io Stack.

Go to Dashboard

Logit.io will verify your input before it is applied, we will contact you to confirm when this has been completed.

Data should now have been sent to your Stack.

View my data

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

Sending data to Logit.io from Amazon Elastic Load Balancer (ELB) Classic is a streamlined process that empowers businesses to centralize their log and metrics data for enhanced monitoring and analysis. To further enhance the capabilities of your AWS environment, consider integrating Amazon RDS into your Logit.io account. Amazon Relational Database Service (RDS) simplifies database management, offering high availability, security, and scalability. In addition, by integrating Amazon ELB Classic logs and metrics with CloudWatch, you can set up automated responses to events and proactively address any issues that may arise. Efficient integration is a hallmark of Logit.io's AWS logging, which includes these integrations and more.