Which CloudFront log format is supported?

CloudFront standard access logs in the W3C format. Legacy standard logs work as-is. For standard logging v2, use an Amazon S3 destination, W3C output, and a tab delimiter.

Do I need to unzip the files first?

No. Gzip-compressed log files are supported directly, so LLM Pulse can read them exactly as CloudFront writes them to S3.

Can I automate this instead of uploading manually?

Yes. Connect the Amazon S3 bucket where CloudFront writes its logs. LLM Pulse pulls new files once a day, and you can use Sync now whenever you need the latest files. Manual upload remains available.

Which plans include the CloudFront integration?

Agent Analytics is included on Scale and Enterprise plans. CloudFront imports populate the overview dashboard. The Enterprise per-URL drilldown currently requires a connected Cloudflare source.

Agent Analytics Integration

Turn CloudFront access logs into agent analytics

Connect the Amazon S3 bucket behind your AWS CloudFront logs and see which AI agents request your content. New W3C log files sync automatically each day.

Start Free Trial

14-day free trial

Cancel anytime

Features

Your CloudFront logs already hold the answer

Every AI agent request to your distribution is sitting in your access logs. LLM Pulse reads them and shows you who is crawling what.

Connect once, sync daily

Connect the S3 bucket where CloudFront writes its standard access logs. We pull new W3C log files automatically, including gzip-compressed files.

AI bots extracted automatically

User agents are matched against our catalog of AI bots, covering GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended, Bytespider, Amazonbot and more.

Backfill up to 90 days

We import CloudFront log files dated up to 90 days back, then keep the dashboard current with daily syncs.

No tags, no JavaScript, no gaps

Access logs record every request at the edge, including all the bots that client-side analytics never see.

From S3 bucket to AI bot dashboard

Connect the S3 bucket once, then let daily syncs keep the dashboard current.

1

Send standard logs to S3

Enable CloudFront standard logging with an Amazon S3 destination. For logging v2, choose W3C output and a tab delimiter.
2

Connect the bucket

In Agent Analytics, open AWS CloudFront and connect the S3 bucket with read-only credentials scoped to its log prefix.
3

Explore your AI bot traffic

The first sync starts after connection. New log files are pulled once a day, and Sync now is available on demand.

"After noticing rising visits from various LLMs in GA4, we needed visibility into those black boxes: which models were mentioning us, in which answers, and how that was changing over time. LLM Pulse gave us the clarity to understand our brand's evolution across AI models and to shape new strategies to boost our exposure."

Victor Hernández

Casa Batlló

Frequently Asked Questions

Common questions about the AWS CloudFront integration for Agent Analytics.

: CloudFront standard access logs in the W3C format. Legacy standard logs work as-is. For standard logging v2, use an Amazon S3 destination, W3C output, and a tab delimiter.
: No. Gzip-compressed log files are supported directly, so LLM Pulse can read them exactly as CloudFront writes them to S3.
: Yes. Connect the Amazon S3 bucket where CloudFront writes its logs. LLM Pulse pulls new files once a day, and you can use Sync now whenever you need the latest files. Manual upload remains available.
: Agent Analytics is included on Scale and Enterprise plans. CloudFront imports populate the overview dashboard. The Enterprise per-URL drilldown currently requires a connected Cloudflare source.

Decode your CloudFront logs today

Connect your CloudFront log bucket and see every AI agent on your distribution. Live on Scale and Enterprise plans.