Amazon ELB Classic

Ship logs from ELB Classic to logstash

Step 1 - Confirm S3 Bucket

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

Step 2 - Ensure Adequate Bucket Permissions

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/*"
            ]
        }
    ]
 }

Step 3 - Start Sending Logs to a Stack

To start sending logs from ELB Classic to your stack you need to setup and apply an AWS input on an available stack.

Logit.io will verify your input before it is applied this should be actioned in less than 24 hours, we will contact you to verify.

Step 4 - Check Logit.io for your logs

Now you should view your logs:

Launch Dashboard

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

Step 5 - AWS ELB Classic Logging Overview

AWS Classic Load Balancer (CLB) is a service that routes incoming traffic to multiple targets, such as EC2 instances or containers, in a single Availability Zone or across multiple Availability Zones. CLB supports layer 4 (TCP) and layer 7 (HTTP/HTTPS) traffic routing

CLB provides access logs to help you monitor and troubleshoot your load balancer. Access logs contain detailed information about each request processed by the load balancer, including the source IP address, destination IP address, request time, response time, and HTTP status code.

You can use the CLB access logs to analyze the performance of your application, troubleshoot issues, and gain insights into your application traffic. Here are some use cases for CLB logs:

Traffic Analysis: You can use access logs to analyze the incoming traffic to your application, including the number of requests, response times, and HTTP status codes.

Troubleshooting: You can use flow logs to troubleshoot issues related to network connectivity, such as identifying dropped packets or network congestion.

Security Analysis: You can use access logs to monitor for suspicious activity, such as repeated failed login attempts or unexpected changes to your application traffic patterns.

CLB logs are stored in Amazon S3, and you can configure the load balancer to either send logs to an S3 bucket or stream them to Logit.io for real-time monitoring and analysis.

Logit.io makes performing troubleshooting and fault monitoring for applications running on AWS EC2 cloud infrastructure easier in comparison to dealing with the complexity associated with distributed cloud services & cloud monitoring topic environments.

Our platform as a service (PaaS) offering is able to fully support a whole host of AWS metrics including those from Kinesis, ELB Applications, VPC, Cloudwatch, CloudTrail, & Amazon RDS.

Expand View