> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/cloud-onboarding/aws-cloud-onboarding/quickstart-aws/add-aws-as-a-new-flow-source-in-fusion.md).

# Add AWS as a new traffic source in Fusion

Add AWS as a traffic source in Vectra Fusion.

1. In Netography Fusion navigate to **Settings** -> **Traffic Sources** -> **Add Traffic Source**

![](https://1075194167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7upncbzIm3grJePXaOO9%2Fuploads%2Fgit-blob-0343a5400714c290236cd06d32c59c2b9ae5e41b%2F5dc7401fa2db9351ae7e4ff72999e5d505359ee9a42ffd005c78711d479b8ae1.png?alt=media)

2. Select **AWS S3 VPC**

![](https://1075194167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7upncbzIm3grJePXaOO9%2Fuploads%2Fgit-blob-d08c5447e41a28f077e18a533a810e4749b594da%2F9105b9cbdc2579fb17ad6f57379df196f284f94ddce40501b33d14189443f9c5.png?alt=media)

3. Fill out the AWS S3 VPC Traffic Source flow form:

**Name:** This will be the Name of your configuration in Netography Fusion. You can use anything you like here.

**Polling:** Leave set as default which is enabled.

**Down Sample:** Leave as default unless you know how to use this feature.

**Account ID:** Your AWS Account ID

**Region:** Your AWS account **Region**

**Bucket Name:** S3 Bucket where you're sending your DNS query logs

**Bucket Region:** The **Region** of your S3 bucket

**Prefix:** S3 bucket storage location typically used if you're sharing a bucket with multiple applications or purposes

Copy your **Account ID** from the upper right dropdown in the AWS console

![](https://1075194167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7upncbzIm3grJePXaOO9%2Fuploads%2Fgit-blob-517e35115deae9d93e4696c48ec7c8d8135e9445%2F7177ec310ea3995ea713f0ca1c277273569c6ed3f4e5dd982c49529b06fb584c.png?alt=media)

Under **Authentication Type** leave the toggle set to the default of **ROLE**.\
Paste in the ARN you saved during the [Create custom role](/cloud-onboarding/aws-cloud-onboarding/quickstart-aws/create-custom-role.md) step

Click **SAVE**

![](https://1075194167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7upncbzIm3grJePXaOO9%2Fuploads%2Fgit-blob-26cb94dd3e6c8e490bb4ebadc1ecd6465e39bab9%2F12b679d2654df70fcddb22c9128c2e7ed4101a462463453b41e267af4f47c7bc.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fusion.vectra.ai/cloud-onboarding/aws-cloud-onboarding/quickstart-aws/add-aws-as-a-new-flow-source-in-fusion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.