Other CDNs and your own caches
Any CDN or cache that can export access logs can deliver to EINBLIQ.IO, including CDNs without a dedicated guide such as CDN77 and MainStreaming. These are the requirements checked during onboarding.
Updated
Log export
Your CDN or cache needs one of these export options:
| Option | Requirement |
|---|---|
| Export to S3 | Writes log files to an S3 bucket using an access key and secret, either on Amazon S3 or on S3-compatible storage. EINBLIQ.IO provides the endpoint, bucket and credentials. |
| HTTPS log streaming | Sends log lines by HTTP POST to an endpoint, with a custom Authorization header. EINBLIQ.IO provides <ENDPOINT_URL> and <BEARER_TOKEN>. |
| Your own pipeline | If logs already pass through Kafka or a similar system, forward them from there, as in the Kafka guide. |
Exports to other object storage, such as Azure Blob Storage or Google Cloud Storage, are possible on request.
Log format
- One record per request, as JSON or as CSV with a header row.
- All fields from Required log fields. Field names can follow your CDN; they are mapped during onboarding.
- Timestamps in UTC, ideally with milliseconds.
- The full query string. Some CDNs truncate or drop it unless configured.
CMCD
- Query parameter (recommended): works with any CDN that logs the full query string. Exclude the
CMCDparameter from the cache key, as described in Send CMCD as a query parameter. - Headers: your CDN needs to write the
CMCD-Request,CMCD-Object,CMCD-StatusandCMCD-Sessionheaders into the log, either as separate fields or combined in one field. Many CDNs require additional configuration for this.
Self-hosted caches
For your own caches, such as Varnish or NGINX-based delivery, the same requirements apply. Shipping the access logs to an S3 bucket provided by EINBLIQ.IO is usually the simplest route.
Next step
Contact EINBLIQ.IO with the name of your CDN or cache, its export options and an example log line with personal data removed. The fields and the delivery path are then agreed with you.