# Quick Start

- [Welcome to Vectra Fusion](https://docs.fusion.vectra.ai/quick-start/readme.md): 🏁 Quick Start Guides The quick start guides walk you through setting up and starting to use Fusion. The first step is to integrate with a cloud provider. Getting started with AWS Getting started with
- [Home](https://docs.fusion.vectra.ai/quick-start/home.md): Before you have added a traffic source to Fusion, the home page will display a screen with instructions on how to add your first traffic source. Once you have added a traffic source, it will change to
- [Fusion Portal Layout](https://docs.fusion.vectra.ai/quick-start/layout.md): ID Area Description 1 Top Dynamic Page Title, Page Tabs, Stationary Elements, Settings Icon 2 Left User ID and Menu and Main Navigation 3 Center-Top Controller (Global Filter) 4 Center Page Content 5
- [Need More Help?](https://docs.fusion.vectra.ai/quick-start/support.md): We are happy to help you configure or troubleshoot any issues you run into using Fusion or integrating it with other systems. If you have additional questions or need assistance, you can reach us at:
- [Quickstart: AWS](https://docs.fusion.vectra.ai/quick-start/quickstart-aws.md): Getting started with Amazon AWS
- [Video Guides](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/video-guides-1.md): Below is a video series based on the steps in the Quickstart: AWS guide for Flow Log Ingestion , Context Enrichment , and DNS Ingestion . These videos augment the written guides but can't replace them
- [Create S3 bucket](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/create-s3-bucket.md): Navigate to S3 in the AWS console Create a bucket. Note: You'll want to create the S3 bucket in same region as your VPC. Give your bucket a name. Leave all settings as default, or follow the policies
- [Create the SNS topic](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/create-the-sns-topic.md): Navigate to SNS in the AWS console Create a topic Leave all settings as default and click Create Topic Save the SNS topic ARN in a text file. This will come in handy later.
- [Create the SQS queue](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/create-the-sqs-queue.md): Navigate to SQS in the AWS console Create a queue Give the queue a name Under Configuration , Set Message retention to 1 day Under Access policy , click Advanced . Delete the default JSON in the Advan
- [Subscribe to Amazon SNS topic](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/subscribe-to-amazon-sns-topic.md): After you've completed the previous step of creating the SQS queue, you'll find the Subscribe to Amazon SNS topic button on the lower half of the Amazon SQS page. Click Subscribe to Amazon SNS topic S
- [Create IAM policy](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/create-iam-policy.md): Navigate to IAM in the AWS console Under Access management in the sidebar menu click Policies Click Create policy Select the JSON tab and delete the default text. Copy and paste in the JSON below. Rep
- [Create custom role](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/create-custom-role.md): On the IAM page under Access management in the sidebar menu click Roles Click Create role Select AWS account You're going to need Netography's Account ID and the custom External ID created in your Fus
- [Create an event notification](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/create-an-event-notification.md): Navigate to S3 in the AWS console Click on your S3 bucket created in a previous step Click the Properties tab Scroll down to event notifications and click Create event notification Give this event a n
- [Enable VPC flow logs](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/enable-vpc-flow-logs-1.md): Navigate to VPC in the AWS console Under Resources by Region Select VPCs The next step will use the CloudShell, where you'll copy and paste a CLI command to more efficiently and accurately enable work
- [Add AWS as a new traffic source in Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/add-aws-as-a-new-flow-source-in-fusion.md): In Netography Fusion navigate to Settings -\&gt; Traffic Sources -\&gt; Add Traffic Source Select AWS S3 VPC Fill out the AWS S3 VPC Traffic Source flow form: Name: This will be the Name of your configu
- [Add context integration to Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/add-context-integration-to-fusion.md): Context permissions were already granted via the Custom role created in a previous step. This document is all that is needed to enable context enrichment for AWS in Netography Fusion. Navigate to Sett
- [Enable DNS query logging in AWS](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/enable-dns-query-logging-in-aws.md): 📘 It is recommended to create a new S3 bucket to be used only for DNS query log storage See our Create S3 bucket steps. Navigate to Route53 in the AWS console Under Resolver in the sidebar, click Que
- [Add DNS as a traffic source in Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-aws/add-dns-as-a-traffic-source-in-fusion.md): Navigate to Settings -\&gt; Traffic Sources -\&gt; Add Traffic Source Under DNS select AWS S3 VPC Fill out the AWS S3 VPC Traffic Source form: VPC ID: The VPC ID you enabled query logs for Account ID: Y
- [Quickstart: GCP](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp.md): Getting started with GCP
- [Diagram: GCP Integration to Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/diagram-gcp.md)
- [Video Guides](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/video-guides.md): Below is a video series based on steps in the Quickstart: GCP for Flow Log Ingestion , Context Enrichment , and DNS Ingestion . These videos are meant to augment the written guides but can't replace t
- [Enable VPC Flow Logs (Network Management API)](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/enable-network-management-api-flow-logs.md): The Network Management API lets you configure VPC Flow Logs for organizations, Virtual Private Cloud (VPC) networks, subnets, VLAN attachments for Cloud Interconnect, and Cloud VPN tunnels. 📘 Before
- [Create a Pub/Sub topic](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/create-a-pubsub-topic.md): Create a Cloud Pub/Sub topic 📘 Onboarding multiple projects at an organization or folder level: You can create a single topic in a designated project that you will use for centralized logging resourc
- [Logging sink design patterns](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/logging-sink-design-patterns.md): 📘 Choosing the right design pattern for GCP logging sinks: There is no single design for GCP logging sinks that is right for all organizations. Reach out to Netography Support if you would like furth
- [Create a Logging Sink Pub/Sub for the topic](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/create-a-logging-sink-pubsub-for-the-topic.md): Create a Cloud Logging Sink Pub/Sub Go to the Log Router page in the Google Cloud console. Select the project to create the sink in. If you are using an aggregated sink, you will want to select a fold
- [Create a Pub/Sub pull subscription](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/create-a-pubsub-pull-subscription.md): Create a Pub/Sub Pull Subscription to a topic Go to the Topics page in the Google Cloud console. Click ⋮ next to the topic you created in a previous step and select Create Subscription . Fill out the
- [GCP service account permissions](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/gcp-service-account-permissions.md): Give Netography's GCP service account permission to be added as a principal to the Pub/Sub subscription 📘 The following steps are a prerequisite for adding Netography as a principal to the Pub/Sub su
- [Add Netography as a principal](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/add-netography-as-a-principal.md): Add Netography's GCP service account as a principal to the Pub/Sub subscription Go to the Subscriptions page in the Google Cloud console. Select the subscription you created in the previous step to br
- [Add GCP as a new flow source in Netography Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/add-gcp-as-a-new-flow-source-in-netography-fusion.md): Add a new GCP flow source to Fusion In the Fusion portal, click the ⚙️ -\&gt; Settings -\&gt; Traffic Sources -\&gt; Add Traffic Source -\&gt; Flow GCP Add the GCP Project ID containing the Pub/Sub subscr
- [Add context integration to Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/context-integration.md): 📘 You need a GCP service account to setup a context integration.: Follow the initial steps below to create one. 1. Create a GCP service account Go to the Service Accounts page Click Create Service Ac
- [Adding DNS as a Traffic Source](https://docs.fusion.vectra.ai/quick-start/quickstart-gcp/adding-dns-as-a-traffic-source.md): Enable DNS logging Before you can start, you need to use DNS policies to enable logging for your networks. When you enable query logging, every DNS query to a Cloud DNS private managed zone is logged,
- [Quickstart: Azure](https://docs.fusion.vectra.ai/quick-start/quickstart-azure.md): Getting started with Microsoft Azure
- [Set working subscription](https://docs.fusion.vectra.ai/quick-start/quickstart-azure/set-working-subscription.md): Access Azure Cloud Shell to run CLI commands from your web browser using az. List our Subscription IDs. az account list --output table Name CloudName SubscriptionId TenantId State IsDefault ----------
- [Register Microsoft Insights Provider](https://docs.fusion.vectra.ai/quick-start/quickstart-azure/register-microsoft-insights-provider.md): Access Azure Cloud Shell to run CLI commands from your web browser using az. Check if Microsoft.Insights is not yet registered. az provider show --namespace Microsoft.Insights --query "registrationSta
- [Create a storage account](https://docs.fusion.vectra.ai/quick-start/quickstart-azure/create-a-storage-account.md): Access Azure Cloud Shell to run CLI commands from your web browser using az. Create a Storage account in the same region as your Virtual Network . List your Virtual Networks , their Resource groups ,
- [Create a flow log](https://docs.fusion.vectra.ai/quick-start/quickstart-azure/create-a-flow-log.md): Access Azure Cloud Shell to run CLI commands from your web browser using az. Create a Flow Log to be read by Netography Fusion. az network watcher flow-log create \\\ --location \\$REGION\&gt; \\\ --name
- [Add Azure VNet as a new flow source in Netography Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-azure/add-azure-vnet-as-a-new-flow-source-in-netography-fusion.md): In Netography Fusion navigate to Settings -\&gt; Traffic Sources -\&gt; Add Traffic Source Select Azure VNet Fill out the Azure traffic source flow form: Name: This will be the Name of your configuratio
- [Add Context Integration to Fusion](https://docs.fusion.vectra.ai/quick-start/quickstart-azure/add-context-integration.md): Access Azure Cloud Shell to run CLI commands from your web browser using az. Create a new App Registration with 'accounts in this organizational directory only' preselected. You can use any Display Na
- [Quickstart: Events](https://docs.fusion.vectra.ai/quick-start/introduction-to-events.md): Getting started with events
- [Quickstart: Dashboards](https://docs.fusion.vectra.ai/quick-start/introduction-to-dashboards.md): Getting Started with Dashboards


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fusion.vectra.ai/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
