> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloudflare

> Deliver Cloudflare HTTP request logs to Profound through Amazon S3.

## Overview

Send Cloudflare Logpush logs to your assigned Profound S3 destination to see agent traffic in Agent Analytics. This guide covers Cloudflare HTTP request logs and uses SSE-S3 encryption.

<Info>
  Contact [Profound support](mailto:support@tryprofound.com) to receive your S3 bucket name and destination prefix. The destination region is `us-west-2` (US West, Oregon). When Cloudflare asks you to verify ownership, contact support for your ownership token.
</Info>

For delivery over HTTP, use the [Cloudflare Logpush streaming integration](/agent-analytics/cloudflare_logpush).

## Prerequisites

* Access to Cloudflare HTTP request Logpush.
* Permission to create and manage Logpush jobs for your domain.

## Encryption

Use **SSE-S3 (AES256)** for this Cloudflare integration. Amazon S3 encrypts your stored logs. You do not need to configure a KMS key.

## Configuration

<Steps>
  <Step title="Get your destination settings">
    Contact [Profound support](mailto:support@tryprofound.com) with your domain and Cloudflare zone details to receive your S3 bucket name and destination prefix. The destination region is `us-west-2` (US West, Oregon). Use these values exactly as supplied.

    Profound configures the source, destination bucket, and write permissions for your organization.

    | Setting    | Value                         |
    | ---------- | ----------------------------- |
    | Bucket     | Your assigned Profound bucket |
    | Path       | Your complete assigned prefix |
    | Region     | `us-west-2` (US West, Oregon) |
    | Encryption | SSE-S3 (AES256)               |

    Your S3 destination uses this format:

    ```text theme={null}
    s3://<assigned-bucket>/<assigned-prefix>/
    ```

    Use the prefix exactly as provided by Profound.
  </Step>

  <Step title="Open Cloudflare Logpush">
    Sign in to the Cloudflare dashboard, select your domain, and open **Investigate → Logpush**. Select **Create a Logpush job**.

    <Frame>
      <img src="https://mintcdn.com/profound-37face47/0hJzfTbdqU5C4M5V/images/agent-analytics/cloudflare_s3/logpush-navigation.png?fit=max&auto=format&n=0hJzfTbdqU5C4M5V&q=85&s=172f44804eab0eaab7d87cc225c8d2f6" alt="Cloudflare Investigate menu with Logpush selected and the Create a Logpush job button" width="3630" height="1734" data-path="images/agent-analytics/cloudflare_s3/logpush-navigation.png" />
    </Frame>
  </Step>

  <Step title="Select Amazon S3">
    Choose **Amazon S3** as the destination.

    <Frame>
      <img src="https://mintcdn.com/profound-37face47/0hJzfTbdqU5C4M5V/images/agent-analytics/cloudflare_s3/select-destination.png?fit=max&auto=format&n=0hJzfTbdqU5C4M5V&q=85&s=537076e0406c3ed0f6a74e220ea34f54" alt="Cloudflare destination selection with the Amazon S3 option" width="2192" height="1872" data-path="images/agent-analytics/cloudflare_s3/select-destination.png" />
    </Frame>
  </Step>

  <Step title="Enter your destination details">
    1. Enter the bucket name and destination path supplied by Profound.
    2. Set **Bucket region** to **US West (Oregon) — `us-west-2`**.
    3. Select **My policy requires AWS SSE-S3 AES256 Server Side Encryption**.
    4. Select **Continue** to start ownership verification.

    <Frame>
      <img src="https://mintcdn.com/profound-37face47/0hJzfTbdqU5C4M5V/images/agent-analytics/cloudflare_s3/destination-details.png?fit=max&auto=format&n=0hJzfTbdqU5C4M5V&q=85&s=8e3bea5c0f18e1dd096f679fcf1504ff" alt="Cloudflare S3 destination form showing bucket, path, region, and the SSE-S3 encryption checkbox" width="3534" height="1750" data-path="images/agent-analytics/cloudflare_s3/destination-details.png" />
    </Frame>

    The screenshot uses placeholder bucket and path values. Replace them with the values supplied by Profound.

    Profound handles the bucket policy. If Cloudflare reports an access error, contact support with the source details.
  </Step>

  <Step title="Complete ownership verification">
    Cloudflare writes a challenge file to the destination. Ask Profound support for the token associated with your source, then enter it in Cloudflare to verify the destination.

    <Frame>
      <img src="https://mintcdn.com/profound-37face47/0hJzfTbdqU5C4M5V/images/agent-analytics/cloudflare_s3/prove-ownership.png?fit=max&auto=format&n=0hJzfTbdqU5C4M5V&q=85&s=b034854b36798a9ae46abd9e5310ff2e" alt="Cloudflare ownership verification with the token and challenge-file path blurred" width="1738" height="905" data-path="images/agent-analytics/cloudflare_s3/prove-ownership.png" />
    </Frame>

    If verification fails, confirm that the token and destination belong to the same setup attempt. Ask support for help if you need to repeat verification.
  </Step>

  <Step title="Configure HTTP request logs">
    Select the **HTTP requests** dataset. Include the fields below, filter the hostname to your configured domain, and use RFC3339 timestamps. Keep the standard JSON output, with one record per line.

    <Frame>
      <img src="https://mintcdn.com/profound-37face47/0hJzfTbdqU5C4M5V/images/agent-analytics/cloudflare_s3/select-dataset.png?fit=max&auto=format&n=0hJzfTbdqU5C4M5V&q=85&s=4bbac60cd1b29d8c6c0c98aac5973120" alt="Cloudflare dataset selection with the HTTP requests option" width="3426" height="1794" data-path="images/agent-analytics/cloudflare_s3/select-dataset.png" />
    </Frame>

    | Fields                                           | Used for                    |
    | ------------------------------------------------ | --------------------------- |
    | `ClientIP`                                       | Client address              |
    | `ClientRequestHost`                              | Requested domain            |
    | `ClientRequestMethod`, `ClientRequestURI`        | Requested resource          |
    | `ClientRequestReferer`, `ClientRequestUserAgent` | Referral and agent analysis |
    | `EdgeStartTimestamp`, `EdgeEndTimestamp`         | Request timing              |
    | `EdgeResponseStatus`, `EdgeResponseBytes`        | Response details            |

    These are the same record fields used by Profound's Cloudflare streaming integration. To capture all traffic, turn off sampling.
  </Step>

  <Step title="Enable delivery">
    Once ownership verification is complete and Profound confirms the source is ready, save and enable your job. Generate traffic to your configured domain and check Cloudflare for delivery errors.
  </Step>
</Steps>

## Verify ingestion

Open Agent Analytics for your domain and select a date range covering the delivered records. Confirm that expected agent traffic appears. Upload success alone does not confirm successful processing.

Logs appear after Cloudflare delivers a batch and Profound processes it. If data is missing, provide support with your domain, Logpush job ID, delivery time, and the S3 file path or error shown by Cloudflare. Do not include credentials.

## Troubleshooting

| Problem                               | What to check                                                                                                      |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Destination access denied             | Confirm the supplied bucket, region, prefix, and SSE-S3 setting. Ask Profound to verify destination permissions.   |
| Ownership challenge fails             | Confirm the token matches the exact destination and current setup attempt. Request help retrieving or renewing it. |
| Delivery succeeds but data is missing | Check source readiness, `ClientRequestHost`, the field selection, and the selected date range.                     |
| Traffic counts are incomplete         | Review hostname filters and sampling, and allow time for delivery and processing.                                  |

## Additional Resources

* [Cloudflare: Configure Logpush to Amazon S3](https://developers.cloudflare.com/logs/logpush/logpush-job/enable-destinations/aws-s3/)
* [Cloudflare streaming integration](/agent-analytics/cloudflare_logpush)
* [Contact Profound support](mailto:support@tryprofound.com)