PrivateLink Support and Custom Parser Upgrades

By: Jade Lassery Henn Idan

Logz.io Adds PrivateLink Support, Introduces the Parsing Rules Hub, and Significantly Enhances DIY Parsing Capabilities

Today, we’re excited to announce support for AWS PrivateLink, allowing Logz.io customers to securely send logs and metrics through private VPC connectivity, without any data ever hitting the public internet. If you’re running workloads inside a VPC on AWS, this upgrade drastically improves your security posture, simplifies your networking architecture, and – most notably – reduces your data transfer costs (a lot).

In addition, we’re introducing the Parsing Rules Hub — a centralized interface that lets you create and manage custom parsing rules to structure your logs as they arrive, giving you full visibility and control over all rules configured in your account.

Last but not least, we’ve revamped the DIY parsing experience, streamlining the rule creation process. Most processor types are now applied in near real time, making it faster and easier to parse your data.

AWS PrivateLink

Why This Matters

Most teams running on AWS send observability data over the public internet, it’s standard practice. But as data volumes grow, this can lead to higher transfer costs, limited control over routing, and in some cases, compliance considerations.

Private Link offers an alternative: a dedicated, private path from your VPC to Logz.io that can reduce costs and simplify networking – without exposing traffic to the public internet.

AWS PrivateLink Integration

AWS PrivateLink support is now available for all Logz.io consumption-based customers. Your data flows directly from your AWS VPC to Logz.io using AWS Interface Endpoints and our internal NLB, no public internet, no proxies, no compromises.

Organizations sending large volumes of observability data to Logz.io are seeing significant reductions in data transfer costs after enabling Private Link, which could be up to *88.9% cost reduction even factoring in static VPC endpoint charges.

*Actual savings may vary based on each customer’s AWS setup, AWS pricing structure and usage patterns.

Implementation: ~20 Minutes

Request approval from Logz.io (contact us)
Deploy VPC endpoints in your target regions (2 recommended for redundancy)
Optional cross-region routing (adds $0.02/GB)
Validate and enable the PrivateLink
Confirm PrivateLink is working, ensuring logs and metrics are being sent to Logz.io properly

Requirements & Availability

To use Private Link with Logz.io, you’ll need:

An AWS VPC
A consumption-based Logz.io plan
A one-time endpoint setup (we recommend 2 endpoints per region for HA)

Don’t have consumption-based pricing yet? This is a strong reason to switch, it unlocks flexibility and cost savings.

Private Link Cost Advantage

For a customer sending 50TB monthly, here’s a rough cost estimate:

Current cost: $4,500/month ($0.090/GB)
With Private Link: $515/month ($0.010/GB + $14.60 2xVPC endpoints)
Monthly savings: $3,985
Annual savings: $47,820
ROI: 775%

Getting Started

With Private Link, you’re not just making your data pipeline more secure, you’re optimizing your TCO and eliminating unnecessary egress spend.

Contact our team to calculate your specific savings and get started with implementation.

View technical documentation for detailed setup instructions.

FAQ

How to start using it?

To get started, contact Logz.io Support, or your CSE/Account Manager. We’ll pre-approve your AWS account and region, and provide the correct endpoint service name for your setup. Once approved, you can create your VPC interface endpoints and connect directly to Logz.io. Setup typically takes less than 20 minutes, and we’ll guide you through the process if needed. Here you can find the official documentation.

Do we support other cloud providers besides AWS?

Private Link is AWS-specific and only works for workloads running in AWS VPCs.

Can customers use Private Link with subscription-based pricing?

No, Private Link requires consumption-based pricing.

What if the customer has multi-region deployments?

Cross-region Private Link is supported but costs more ($0.020/GB vs $0.010/GB).

How long does implementation take?

Typical setup is ~20 minutes. We provide technical support to simplify the process.

What about reliability and redundancy?

We recommend 2 VPC endpoints per region for redundancy.

Does this affect data compression or ingestion performance?

No impact on compression ratios.

Can customers test Private Link before committing?

Yes, customers can set up endpoints and test data flow. VPC endpoint costs are minimal during the testing phase.

What happens if Private Link goes down?

If the Private Link connection becomes unavailable, data shipping to Logz.io will fail, just like it would with any unavailable endpoint. That’s why we strongly recommend a high-availability (HA) setup using two VPC endpoints per region across multiple Availability Zones. This ensures redundancy and minimizes the risk of disruption.

Do you charge extra for Private Link on top of consumption pricing?

No, Private Link is currently offered at no additional cost to Logz.io customers on consumption-based plans. Contact us today to schedule a demo.

Parsing Rules Hub & DIY Parsing

Why This Matters

Parsing is foundational to unlocking the value of your logs. Without proper structure, troubleshooting becomes more difficult, and critical insights remain buried in noisy, unstructured data — making search, analysis, and alerting harder, and limiting the effectiveness of your AI agents.

The new Parsing Rules Hub gives you a powerful, intuitive way to manage parsing rules across your entire environment — reducing reliance on engineering, eliminating guesswork, and ensuring your data is AI-ready.

With our revamped DIY parsing experience and near real-time rule application, you can parse more data, faster. The result: smoother onboarding, faster troubleshooting, and more efficient operations — all with greater control in your hands.

And we’re just getting started: we’re doubling down on enhancing the parsing experience and will soon roll out AI-powered capabilities on our journey to fully automatic parsing — a key milestone on our path to autonomous observability.