Stream Heroku Logs Directly to Your AWS
S3 & CloudWatch

Gain complete control over your Heroku log data. Securely archive logs to your own AWS S3 buckets and CloudWatch Log Groups for compliance, cost savings, and powerful analysis. No vendor lock-in, total data ownership.

Get Started Learn more

New: We're adding Vercel, Fly.io, and Render.com support soon!

Pricing starts at $9/month per GB of daily log volume. Start with a free month.

/aws/lambda/production-app-logs

Timestamp

Message

Showing latest events... Connected

Full Data Control

Unlock the Value of Your Heroku Logs

LogBox securely streams your Heroku logs directly to your AWS S3 and CloudWatch, giving you unparalleled control, cost savings, and powerful log analysis capabilities.

Complete Data Ownership & Compliance: Maintain complete ownership over your data. No vendor lock-in, no external retention policies — you decide log retention and access, to help meet compliance, audit, and security requirements.
Scalable & Cost-Effective Log Archival: Leverage AWS S3 & Glacier for virtually unlimited, low-cost log storage. Archive terabytes affordably, stop paying high log retention fees, and easily retrieve historical data for analysis or investigations.
Real-time Monitoring & Powerful Insights: Utilize AWS CloudWatch Logs for real-time log streaming, analysis with Logs Insights, custom dashboards, and automated alerting. Proactively detect errors, monitor performance, and ensure application health.

How it works?

Simple setup

LogBox.io acts as a secure Heroku log drain, reliably forwarding your application and system logs for long-term archival and analysis in AWS S3 and CloudWatch. Get set up in minutes:

Setup AWS Resources: Create an S3 bucket (and optionally, a CloudWatch Log Group) and an IAM user with the necessary permissions. We provide an example IAM policy for easy setup.
Configure LogBox.io: Sign up and connect your LogBox.io account. Provide the AWS IAM credentials, S3 bucket name, and optional CloudWatch Log Group details.
Attach Heroku Log Drain: Add the secure LogBox.io drain URL to your Heroku app(s). Logs will immediately start streaming to your configured AWS destinations.; heroku drains:add https://[YOUR-SECURE-TOKEN]@drains.logbox.io --app YOUR-APP-NAME

Simple Usage-Based Pricing

Pay only for what you use, based on daily log volume. Transparent pricing starts at just $9.00/month per GB/day.

Connect unlimited Heroku apps per account.

Start with a free first month. Afterwards, select a plan based on your actual usage.

1 GB of logs per day

$9 /month

Total charge per month (excl. AWS charges)

Get started

Do you require a custom plan? Get in touch

Expanding Support

Connect More of Your Favorite Platforms

We're working hard to bring LogBox.io to more platforms. Soon, you'll be able to stream logs from Vercel, Fly.io, and Render.com directly to your AWS S3 and CloudWatch. This will allow for seamless Vercel logs to CloudWatch, robust Fly.io log management, and efficient Render log streaming to S3.

Be the First to Know!

We respect your privacy. No spam, unsubscribe anytime.

Frequently Asked Questions

Have a different question about LogBox.io, Heroku log drains, or AWS integration? Reach out to our support team by sending us an email and we'll get back to you promptly.

: LogBox.io buffers application logs for about two minutes. When they are successfully uploaded to S3 the service no longer has access to any messages.
: LogBox.io stores AWS credentials encrypted in database and never share them with anyone. But you do not have to trust us, we strongly encourage users to give us minimal set of permissions (write-only access to a single bucket).
: You can use AWS calculator to get best estimates: (https://calculator.s3.amazonaws.com/index.html). LogBox.io makes a single PUT request every minute (30 days * 24 hours * 60 minutes = 43 200 requests, AWS will charge $0.20 for it).
: Yes, we offer 30 days free trial.
: We will still process application logs but you will be kindly asked to upgrade your plan.

This policy grants the minimum required permissions for LogBox.io to securely send logs to your AWS S3 bucket and CloudWatch Logs group. Ensure the IAM user has programmatic access enabled.

Replace BUCKETNAME, REGION, ACCOUNT_ID, and LOGGROUPNAME with your specific AWS resource names and details.

{
"Version": "2012-10-17",
"Statement": [
    {
        "Sid": "LogBoxS3",
        "Effect": "Allow",
        "Action": [
            "s3:PutObject",
            "s3:GetBucketLocation"
        ],
        "Resource": [
            "arn:aws:s3:::BUCKETNAME/*",
            "arn:aws:s3:::BUCKETNAME"
        ]
    },
    {
        "Sid": "LogBoxCloudWatch",
        "Effect": "Allow",
        "Action": [
            "logs:DescribeLogStreams",
            "logs:CreateLogStream",
            "logs:PutLogEvents"
        ],
        "Resource": [
            "arn:aws:logs:REGION:ACCOUNT_ID:log-group:LOGGROUPNAME:*"
        ]
    }
]
}

Note: You only need the LogBoxCloudWatch statement if you plan to forward logs to CloudWatch Logs in addition to S3.