---
title: "AWS CloudFront"
slug: "aws-cloudfront"
updated: 2025-07-17T15:18:10Z
published: 2025-07-17T15:18:10Z
canonical: "docs.databee.buzz/aws-cloudfront"
---

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

# AWS CloudFront

CloudFront CDN speeds up distribution of static and dynamic web content through a worldwide network of data centers. For detailed information refer to the [AWS CloudFront's official documentation](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Introduction.html).

**Integration** **Method**: S3 **Tables**: HTTP Activity (4002)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Access logs | It contains detailed information about every user (viewer) request that CloudFront receives. |

> [!NOTE]
> **Note:**
> 
> AWS CloudFront doesn’t follow a traditional versioning system. Instead, it is a continuously updated cloud service. As of this document preparation, latest release was on **Apr 9, 2024**. For detailed information refer to the [AWS CloudFront’s update history documentation](https://aws.amazon.com/cloudfront/whats-new/).

## Prerequisites

- The user should have access to the AWS portal.
- The user should have access to the CloudFront dashboard and access to create an S3 bucket.
- The user should have access to the DataBee console.

## Configuration Overview

- [Create S3 Bucket](/user-manual/docs/aws-cloudfront#create-s3-bucket) for AWS access logs.
- [Configure standard logging](/user-manual/docs/aws-cloudfront#configure-standard-logging) by updating distributions in AWS CloudFront.
- Add [AWS CloudFront data feed](/user-manual/docs/aws-cloudfront#databee-configuration) in the DataBee console with the below parameters.

| **DataBee Parameter** | **AWS CloudFront Parameter** |
| --- | --- |
| S3 Bucket Name | Bucket Name |
| AWS Region | Bucket Region |

- Apply the generated Bucket policy from DataBee to S3 Bucket policy.
- Create an event notification for bucket with the AWS SQS ARN from DataBee.

## AWS CloudFront Configuration

### Create S3 Bucket

1. Sign in to the AWS Management Console and open the [Amazon S3 console](https://console.aws.amazon.com/console/home?nc2=h_ct&src=header-signin).
2. In the navigation bar on the top of the page, choose the name of the currently displayed AWS Region. Next, choose the Region in which you want to create a bucket.

![Picture](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-sgp2ocbh.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
3. Create Bucket

![Picture](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-ob58gwxv.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  1. In the left navigation pane, choose **General purpose buckets**.
  2. Choose **Create bucket**. The “Create bucket” page opens.
4. For **Bucket name**, enter a name for your bucket. The bucket name must:

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-xjlfzcd8.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  - Be unique within a partition. A partition is a grouping of regions. AWS currently has three partitions: aws (commercial Regions), aws-cn (China Regions), and aws-us-gov (AWS GovCloud (US) Regions).
  - Be between 3 and 63 characters long.
  - Consist only of lowercase letters, numbers, periods (.), and hyphens (-). For best compatibility, we recommend that you avoid using periods (.) in bucket names, except for buckets that are used only for static website hosting.
  - Begin and end with a letter or number.

For a complete list of bucket-naming rules, see [General purpose bucket naming rules](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html).
5. Configure the Object Ownership, Block Public Access settings, Bucket Versioning, and Tags according to your preferences.
6. Select the encryption type for **Default encryption** of object. If you want to encrypt the data with AWS KMS key, then follow [Create a KMS key](https://us-east-1.console.aws.amazon.com/kms/home?region=us-east-1#/kms/keys/create).

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-t59co2fh.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
7. Click **Create Bucket**.
8. Navigate to **Properties** of the bucket. Copy the **ARN** value of bucket for future use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-tt5oboc2.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
9. Navigate to **Permissions** > **Bucket policy** of the bucket. Click on the **Edit** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-fwj0ztgp.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
10. Add the policy below to the destination Amazon S3 bucket policy and replace the following values:

```json
{   
   "Version": "2012-10-17",
   "Statement": [
       {
           "Sid": "AWSLogDeliveryWrite",
           "Effect": "Allow",
           "Principal": {
               "Service": "delivery.logs.amazonaws.com"
           },
           "Action": "s3:PutObject",
           "Resource": "arn:aws:s3:::bucket_name/*",
           "Condition": {
               "StringEquals": {
                   "s3:x-amz-acl": "bucket-owner-full-control",
                   "aws:SourceAccount": "account-ID"
               },
               "ArnLike": {
                   "aws:SourceArn": "arn:aws:logs:region:account_ID:delivery-source:*"
               }
           }
       }
   ]
}
```

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-o9hjzovm.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  1. account_ID: replace with the account_id. Click on the top-right profile menu to get the account id.
  2. arn:aws:logs:region:account_ID: replace with the aws region and account_ID.
  3. bucket_name: replace with the bucket name.
11. Click on **Save changes**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-ay9j7hjl.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)

### Configure Standard logging

1. Login to your AWS account and search for CloudFront service as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-ieqz34tr.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
2. In “Distributions” page you will see the list of distributions. Click on the distribution to enable standard logging. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-ovi1z6oy.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
3. Click on **Logging** tab and click on **Add** button to add standard log destination. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-cdqcwv37.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
4. Select **Amazon S3** as log destination. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-8hfy27bp.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
5. Enter the following details to create standard log destination.
  - Destination S3 bucket: Select the S3 bucket which is created to forward log.
  - Field selection: We can select the fields which we want to be present in the access logs.
  - Partitioning (Optional): You can use partitioning to organize your access logs when CloudFront sends them to your S3 bucket. By default, CloudFront will send data to the AWSLogs/{account-id}/CloudFront path.
  - Output format: Select JSON.
6. Click on **Submit**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-falgzfmw.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![A screenshot of a computer AI-generated content may be incorrect., Picture](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-t7c4z423.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
2. Search for **AWS CloudFront** and click on it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-c3kjlshv.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
3. Click on the **AWS S3** collection method. ![Picture](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-p5lwn4w4.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
4. In the configuration page, enter feed contact information and confirm the following and click **Next**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-au2blukd.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  - S3 Bucket Name: Paste the bucket name.
  - AWS Region: Select the AWS Region in which bucket is created.
  - Compression: Select gzip.
  - Content Type: Select JSON Lines.
  - KMS Encryption Key (optional): Paste the KMS Key if setup the KMS key for bucket.
5. Copy the IAM policy and KMS policy to apply to your AWS S3 bucket
  1. Copy the policy statement to clipboard. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-tyxg9onb.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  2. Go to the **Permissions** tab in the bucket. Navigate to **Bucket policy** and click the **Edit** button and add the bucket policy statement copied from DataBee. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-vwwfblvh.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  3. Save the bucket policy.
6. Click **Next**.
7. Setup AWS S3 bucket notification.
  1. Copy the SQS ARN to clipboard. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-43wpas5v.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  2. Go to the **Properties** tab of the bucket. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-xskdq3xk.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  3. Navigate to **Event notifications** and click **Create event notification**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-jw3xyjne.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  4. Enter the **General configuration** details and select the **Event type** for object creation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-gullkv4l.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
  5. Set the **Destination**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-75np6v2m.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
    1. Select **SQS Queue** as Destination.
    2. Select option to **Enter SQS queue ARN**.
    3. Paste the SQS queue ARN.
    4. Click **Save changes**.
8. Click on **Test Connection**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-cloudfront-image-g0gt4ind.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A46%3A44Z&se=2026-10-30T13%3A46%3A44Z&sr=c&sp=r&sig=JC4UGx9Mm25Zy3zo%2FFDfa7DXmQDOP3%2BiEbFzXYvTDIA%3D)
9. Click **Submit**.

## Troubleshooting Tips

- If you are facing an error while testing the connection, then make sure the bucket policy is applied properly and check the SQS event notification configuration as described in the steps.

#