AdobeStock_425671164-2

The Pleasure of Finding Things Out: Federated Search Across All Major Cloud Providers and Native Support for Amazon Security Lake

Last edited: July 17, 2026

Your telemetry is distributed across multiple clouds: flow logs in Amazon S3, Azure Blob Storage, and Google Cloud Storage. Searching each one separately requires switching between consoles, wastes hours, and can miss correlations. Cribl Search 4.2 addresses this with federated search across the major cloud providers and native support for Amazon Security Lake. One query language and one interface cover the supported clouds.

This post shows how the new dataset providers expand what Cribl Search delivers out of the box, then walks through building and running federated queries step by step.

What new dataset providers can you search?

Cribl Search 4.2 adds Amazon S3, Azure Blob Storage, and Google Cloud Storage as dataset providers, so your cloud flow logs are one query away. Cloud storage is widely used and distributed across providers, which is why your search tool needs to access all of it. With Cribl Search 4.2, navigating flow logs across platforms works with commands like:

Code example
dataset="aws_s3_flowlogs" earliest=-1h | limit 1000

This query selects from the AWS S3 flow logs dataset, restricts the search to the most recent hour, and returns up to 1,000 records.

To query Azure or Google Cloud, swap the dataset name. Replace

Code example
dataset="azure_blob_flowlogs" earliest=-1h | limit 1000
word-image-48630-2

Or:

Code example
dataset="google_gcs_flowlogs" earliest=-1h | limit 1000
word-image-48630-3

Same syntax, different cloud. You do not need new tools or to move data.

How does federated search work across all three clouds?

Federated search in Cribl Search means one query can target multiple datasets at once, regardless of which cloud holds the data. By appending _flowlogs to each dataset name, you can use a wildcard to search across them simultaneously:

Code example
dataset="*_flowlogs" earliest=-1h | limit 1000
word-image-48630-4

For example, to identify traffic patterns across ports and datasets within the last hour, use:

Code example
dataset="*_flowlogs" | limit 1000 | summarize flowcount=count() by dstport, dataset | extend port_and_source=dstport + ":" + dataset | project port_and_source, flowcount
word-image-48630-5

What each step does:

  • dataset="*_flowlogs" selects every dataset ending in _flowlogs, letting an administrator analyze traffic across all relevant clouds at once.

  • | limit 1000 restricts the pull to the most recent 1,000 records to keep the query responsive.

  • | summarize flowcount=count() by dstport, dataset counts traffic by destination port and dataset, showing volume per port per cloud.

  • | extend port_and_source=dstport + ":" + dataset creates a column that combines port and dataset into a single string.

  • | project port_and_source, flowcount displays those two columns for a concise view of traffic patterns.

This produces cross-cloud traffic analysis in a single query. You do not need to export data or use spreadsheets. This example shows one way federated search simplifies analysis.

What does native support for Amazon Security Lake mean?

Cribl Search 4.2 queries Amazon Security Lake directly, without ingestion. This integration uses the Open Cybersecurity Schema Framework (OCSF) and the Parquet format, so security data remains standardized and searchable at the source.

For example, to access the Amazon Security Lake stage and return the 100 most recent records:

Code example
dataset="amazon_security_lake_stage" | limit 100
word-image-48630-6

 

To categorize and summarize data by disposition using projection and predicate pushdown:

Code example
dataset="amazon_security_lake_stage" category_name="Network Activity" | summarize count() by disposition
word-image-48630-7

Only the data required for the query is processed, which reduces latency and cost. This is search-in-place.

How Cribl can help with federated search across cloud providers

Cribl is a platform for telemetry built on the idea that data should serve teams. When telemetry is scattered across clouds, formats, and tools, IT and security teams lose time and miss signals. Cribl Search removes those barriers by bringing federated, search-in-place queries to data where it lives, whether in Amazon S3, Azure Blob Storage, Google Cloud Storage, or Amazon Security Lake.

Because Cribl's platform is vendor agnostic, you are not locked into a single cloud, storage format, or analytics tool. Search data at the source, forward only the critical results to your analysis systems, and avoid the ingestion and egress costs of moving everything first. Combined with Cribl Stream for routing and transformation and Cribl's other products, you get control and flexibility over telemetry.

Extracting actionable insights from data lakes is possible regardless of cloud platform or security solution.

Sign up for a free Cribl.Cloud account to process up to 1 TB per day at no cost, or try a Cribl Sandbox.

Federated search across all major cloud providers FAQ

Cribl, the AI Platform for Telemetry, empowers enterprises to manage and analyze telemetry for both humans and agents with no lock-in, no data loss, no compromises. Trusted by organizations worldwide, including half of the Fortune 100, Cribl gives customers the choice, control, and flexibility to build what’s next.

We offer free training, certifications, and a free tier across our products. Our community Slack features Cribl engineers, partners, and customers who can answer your questions as you get started and continue to build and evolve. We also offer a variety of hands-on Sandboxes for those interested in how companies globally leverage our products for their data challenges.

More from the blog

get started

Choose how to get started

See

Cribl

See demos by use case, by yourself or with one of our team.

Try

Cribl

Get hands-on with a Sandbox or guided Cloud Trial.

Free

Cribl

Process up to 1TB/day, no license required.