Explore documentation
  1. Welcome to Telemetry 👋
  2. Quick start guide
  3. Wide events vs. time series
  4. Ingesting data
    1. Better Stack collector
    2. Vector
    3. OpenTelemetry
    4. Ingesting via HTTP API
    5. Ingesting metrics
    6. Ingesting logs
      1. Docker & Kubernetes
      2. Operating systems
      3. Log forwarders
      4. Programming languages
      5. Cloud platforms
        1. AWS
          1. Amazon CloudWatch
          2. Amazon ECS
          3. Amazon EKS
          4. AWS Elastic Load Balancing
          5. AWS Fargate
          6. AWS Lambda
          7. AWS Direct Connect
        2. Azure
        3. Cloudflare
        4. Google
        5. Digital Ocean
        6. Heroku
        7. Vercel
        8. Render
        9. Fly.io
      6. Web servers & Load balancers
      7. Databases & queues
      8. Storage
    7. Migrating to Better Stack
  5. Using the product
    1. Transforming ingested data
    2. Querying data
    3. Tracing
    4. Alerts
  6. Telemetry API
    1. Getting an API token
    2. Sources
    3. Metrics API
    4. Query API ↗
  7. Alternative to
    1. Lightstep

AWS Direct Connect

When sending logs or metrics from AWS to Better Stack, you typically incur AWS egress charges.

AWS charges up to $0.09/GB for data egress, which can significantly increase your expenses for high-volume telemetry.

To help you reduce these costs, Better Stack offers dedicated ingestion endpoints that leverage AWS Direct Connect. By routing your data through these endpoints, you can reduce your egress expenses.

We bill for Direct Connect ingestion at $0.04/GB, offering substantial savings compared to standard AWS egress rates.

How to use AWS Direct Connect

To utilize Direct Connect, you need to change your ingestion endpoint from the default ingesting host to the AWS proxy address for your chosen region.

Format for the Direct Connect ingesting host
<cluster>-aws-<aws-region>.betterstackdata.com

For example, if your logs currently ingest through a host in the eu-nbg-2 cluster and you want to use AWS Direct Connect in the eu-central-1 region, it would look like this:

Default ingesting host s123456.eu-nbg-2.betterstackdata.com
Cluster eu-nbg-2
Chosen AWS region eu-central-1
New ingesting host eu-nbg-2-aws-eu-central-1.betterstackdata.com

Configuration Steps

  1. Identify your cluster
    Find the cluster you're using in Telemetry -> Sources -> Your source, e.g. eu-nbg-2 or us-east-9.

  2. Choose an AWS region
    Select one of our available AWS regions that offers Direct Connect.

  3. Construct the new ingesting host
    Combine your cluster and the chosen AWS region into <cluster>-aws-<aws-region>.betterstackdata.com. For instance, eu-nbg-2-aws-eu-central-1.betterstackdata.com. This will be your new ingesting host.

  4. Update your source configuration
    Modify your log forwarder, application, or collector configuration to use this new endpoint. This usually involves updating the ingesting_host or endpoint parameter.

Using syslog to send your logs?

If you're using *-vec.betterstackdata.com ingesting host, as suggested for connecting Heroku, Digital Ocean and Render apps, or connecting via RSyslog or Syslog-ng, the AWS Direct Connect cannot be used directly.

Please let us know if you have specific request at hello@betterstack.com.

Available AWS regions

We currently have Direct Connect forwarders in the following AWS region:

  • eu-central-1

Cross-Region Data Transfer

If your AWS services are not running in eu-central-1, you can still use our Direct Connect endpoint in that region to reduce costs. You will incur an AWS cross-region data transfer charge, but the total cost to you will still be less than the standard AWS egress costs.

Looking for a different AWS region?

We are actively working on expanding our Direct Connect presence. Please let us know if you have specific region requests at hello@betterstack.com.

Need help?

Please let us know at hello@betterstack.com. We're happy to help! 🙏

Previous article

Better Stack AWS Lambda logging

Next article

Better Stack Azure Event Hub logging