---
title: "AWS VPC"
slug: "aws-vpc-doc-standard"
updated: 2025-10-30T18:41:11Z
published: 2025-10-30T18:41:11Z
canonical: "docs.databee.buzz/aws-vpc-doc-standard"
---

> ## 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 VPC

Amazon Virtual Private Cloud (VPC) lets you create a secure, isolated network within AWS. For detailed information refer to the [AWS VPC’s official documentation](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html).

**Integration** **Method**: S3

**Tables**: Network Activity (4001)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Network Events | Get the list of AWS Network Events |

> [!NOTE]
> **Note:**
> 
> AWS VPC doesn’t follow a traditional versioning system. Instead, it is a continuously updated cloud service.

## Prerequisites

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

## Configuration overview

1. [Create S3 Bucket](/user-manual/docs/aws-vpc-doc-standard#create-s3-bucket) for AWS VPC flow logs.
2. [Create an AWS VPC flow log](/user-manual/docs/aws-vpc-doc-standard#create-vpc-flow-logs).
3. Add the [AWS VPC data feed](/user-manual/docs/aws-vpc-doc-standard#databee-configuration) in the DataBee console with the below parameters.

| **DataBee Parameter** | **AWS VPC Parameter** |
| --- | --- |
| S3 Bucket Name | [Bucket Name](/docs/aws-vpc-doc-standard#bucket_name) |
| AWS Region | Bucket Region |

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

## AWS VPC 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.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-4qmso074.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
3. Create Bucket

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-1qid37nz.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%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-vpc-doc-standard-image-bxwyhqr3.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  1. 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).
  2. It is between 3 and 63 characters long.
  3. 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.
  4. Begin and end with a letter or number.
  5. 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-vpc-doc-standard-image-e1vdfisw.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
7. Click **Create bucket**.
8. Navigate to **Properties** of the bucket. Copy the **ARN value** of bucket for future use.

![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-5og9qxb1.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%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-vpc-doc-standard-image-6xvyv0j1.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
10. Add policy for the VPC Flow logs

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-0pfi7t4c.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-aluhp34z.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  1. Navigate to [bucket permissions for VPC flow logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-s3-permissions.html). Copy the permissions and paste in the Bucket policy.
  2. Here replace the following values.
    - my-s3-arn – replace with the bucket arn value.
    - account_id – replace with the account_id. Click on the top-right profile menu to get the account id.
  - arn:aws:logs:region:account_id – replace with the aws region and account_id.
  - bucket_name – replace with the [bucket name](/docs/aws-vpc-doc-standard#bucket_name).
11. Click on **Save changes**.

### Create VPC Flow Logs

1. Sign in to the AWS Management Console and open the Amazon VPC console.
2. Navigate to the **Your VPCs** tab.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-kavmw5ei.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
3. Select the existing VPC or [create VPC](https://docs.aws.amazon.com/vpc/latest/userguide/create-vpc.html).
4. Create VPC flow logs.
5. Navigate to the **Flow logs** tab.
6. Click on **Create flow log**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-r9c2bbda.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
7. Enter the flow log settings details

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-qbtbluur.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  1. Enter the **Name**.
  2. Select **All** for Filter.
  3. Select **Maximum aggregation interval** as per your preference.
8. Select the Destination as S3 bucket to publish the flow log data.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-nbx10qq6.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  1. Paste the bucket ARN value.
9. Select the log record format

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-j2pdjnw7.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  1. Select the **Custom format**.
  2. Click on the **Select All** button.
10. Select Log file format and partition logs by time

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-f5kmise6.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  1. Select **Text (default)** as Log file format.
  2. Select **Partition logs by time** as per your preference.
11. Click **Create flow log** button.

## 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.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-86ehu9tm.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
2. Search for **AWS VPC** and click on it as shown below.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-8kivn5bx.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
3. Click on the **AWS S3** collection method.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-3ahizzag.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
4. In configuration, enter feed contact information, confirm the following and click Next.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-c2fyeoxj.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
  - **S3 Bucket Name:** Paste the [bucket name](/docs/aws-vpc-doc-standard#bucket_name)
  - **AWS Region:** Select the AWS Region in which bucket is created
  - **Compression**: Select gzip
  - **Content Type**: Select SSV
  - **KMS Encryption Key (optional)**: Paste the [KMS Key](/docs/aws-vpc-doc-standard#aws_kms_key) if setup the KMS key for bucket
  - **SNS Topic ARN (optional)**: Enter the SNS Topic ARN
5. Copy the IAM policy and KMS policy to apply to your AWS S3 bucket.
6. Copy the policy statement to clipboard.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-5pcv0462.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
7. Go to the **Permissions** tab in the bucket. Navigate to Bucket policy and click the **Edit** button.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-pn11sp9z.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
8. Add the bucket policy statement copied from DataBee.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-naar27x9.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
9. Save the bucket policy.
10. Click **Next**.
11. Setup AWS S3 bucket notification.
12. Copy the **SQS ARN** to clipboard.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-d2omohr7.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
13. Go to the **Properties** tab of the bucket.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-5o9vwvxe.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
14. Navigate to **Event notifications** and click **Create event notification**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-5o9vwvxe.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
15. Enter the **General configuration** details.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-ynk0fd5g.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
16. Select the **Event types** for **Object creation**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-vv9ebx21.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
17. Set the **Destination**
  1. Select **SQS queue** as Destination.
  2. Select option to **Enter SQS queue ARN**.
  3. Paste the SQS queue ARN.
18. Click **Save Changes**.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-6iucxojr.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
19. Click on **Test Connection** button to check the connection between AWS VPC and DataBee.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/aws-vpc-doc-standard-image-ky8wvh1v.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A52Z&se=2026-11-15T01%3A04%3A52Z&sr=c&sp=r&sig=A6S%2FnLk0OZ3r5Ze%2BPOdXrSdy61gL7KUdH0o3eaHrAIU%3D)
20. 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](/docs/aws-vpc-doc-standard#notification_configuration).

#