Overview
Send Fastly access logs to your assigned Profound S3 destination to see agent traffic in Agent Analytics. This guide covers Fastly CDN services using VCL and SSE-S3 encryption.Contact Profound support to receive your bucket name, destination prefix, region, and IAM role ARN before enabling delivery.
Prerequisites
- Access to the Fastly service that handles your website’s traffic.
- Permission to edit logging endpoints and activate a service version.
- Your Fastly account ID, which Profound needs to configure delivery permissions.
Encryption
This guide uses SSE-S3 (AES256) to encrypt your logs at rest with keys managed by Amazon S3.Configuration
1
Get your destination settings
Contact Profound support with your domain and Fastly account ID. Profound configures the source and a role that allows Fastly to write to your assigned destination.You will receive a bucket name, destination prefix, region, and role ARN. Use the prefix exactly as provided, including the trailing slash. The prefix identifies your source.The role ARN is the authorization value for this setup. You do not need AWS access keys or a Profound HTTP ingestion token.
2
Create an S3 logging endpoint
Open your Fastly service and edit a service version. In its logging settings, create an Amazon S3 endpoint.
Keep the default logging placement. Follow Fastly’s S3 endpoint guide for the current control-panel layout.
3
Set the log format
Paste this template into Log format as a single line. It emits the fields expected by Profound’s Fastly processor.
Use Blank for the log line format (
message_type=blank) so no syslog prefix is added. Each line must contain one JSON object. Profound does not accept the default space-separated log format or a JSON array for this S3 integration.Use uncompressed output or gzip. Gzip filenames must end in .gz so Profound can decompress them. Do not enable PGP encryption, Snappy, or Zstandard for this setup.4
Filter to your domain
Attach a logging condition that matches the hostname you want to monitor. For example:Replace
example.com with your hostname. Include any additional hostnames you intend to monitor in your condition.5
Enable delivery
Once Profound confirms your source is ready, save the endpoint and activate the service version. Generate traffic to the configured domain and allow time for Fastly to deliver a log file.The endpoint’s Period setting controls how frequently files are finalized. Check that setting when estimating when your test traffic will arrive.