> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/create-a-custom-outpost.md).

# Create a custom outpost

Create a custom outpost with the Create Outpost wizard. Choose how the outpost reaches the internet, bring your own network (BYON) or app registration (BYOA) if you need to, and deploy the template in

Create a custom outpost when you need to control parts of the outpost infrastructure yourself. You define the outpost in the Create Outpost wizard, and then you deploy the template that the wizard generates in your CSP. Cortex XSIAM creates every resource that you do not supply yourself.

The Create Outpost wizard has the following pages:

* **Global Settings:** The outpost account, the outpost name, cloud tags, how the outpost reaches the internet, and, for Azure, whether you bring your own app registration.
* **Regional Settings:** The regions the outpost operates in, and, if you bring your own network, the network in each region.
* **Summary:** A review of your settings, and the options for deploying the template.

## Step 1. Plan and prepare

Before you start the wizard, decide how the outpost reaches the internet, whether you bring your own network or app registration, and which deployment tool you use.

1. Review [Plan your custom outpost](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/plan-your-custom-outpost.md), and decide on the **Outpost networking** option.
2. If you plan to set **Outpost networking** to **Custom**, complete the [custom networking prerequisites](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/custom-networking-prerequisites.md). Have the IDs of your network resources ready for each region.
3. (Azure) If you plan to bring your own app registration, complete the [prerequisites](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/bring-your-own-azure-app-registration-byoa/prerequisites-for-bringing-your-own-app-registration.md), and then [create the Azure app registration](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/bring-your-own-azure-app-registration-byoa/create-the-azure-app-registration.md). Have the IDs that you recorded ready.

{% hint style="info" %}
**Notes:**

* Before you create your outpost, verify that your internet connection is active. An active internet connection is necessary for the notification to be sent to Cortex XSIAM to create the new outpost.
* (Azure) Due to limitations in Terraform, the Azure subscription name cannot contain blanks.
  {% endhint %}

## Step 2. Configure global settings

On the Global Settings page, you enter the outpost account and name, add cloud tags, choose how the outpost reaches the internet, and, for Azure, choose whether to bring your own app registration.

1. In Cortex XSIAM, navigate to **Settings > Data Sources and Integrations > Outposts**.
2. Click **New Outpost**, and then choose your CSP.
3. Select **Custom Outpost**, and then click **Next**. The **Custom Outpost** wizard opens on the Global Settings page.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> To see the resources that Cortex XSIAM creates for you in this outpost, click the information icon next to the wizard title. For the full lists, see <a href="https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-outpost-concepts/what-cortex-creates-in-a-custom-outpost.md">What Cortex creates in a custom outpost</a>.</p></div>
4. Enter the account details according to your CSP.

<details>

<summary>AWS</summary>

* **Account ID:** The ID of the AWS account where Cortex XSIAM deploys the outpost.
* **Instance Name:** A name for the outpost. The instance name can be up to 255 characters.

</details>

<details>

<summary>Azure</summary>

1. (Optional) To use your own pre-created Entra ID app registration instead of having Cortex XSIAM create one automatically, toggle **Bring Your Own App Registration** on, and enter the following IDs. You recorded these IDs when you [created the Azure app registration](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/bring-your-own-azure-app-registration-byoa/create-the-azure-app-registration.md).
   * **Application (Client) ID:** The Application (Client) ID of your Azure app registration. This is the `customer_app_client_id` value that the helper shell script returns, or the value on the app registration's **Overview** page in the Azure portal.
   * **Service Principal Object ID:** The Object ID of the service principal associated with your Azure app registration. This is the `customer_sp_object_id` value that the helper shell script returns, or the **Object ID** on the enterprise application's **Properties** page. Do not confuse it with the Application (Client) ID. Both are UUIDs, and they are not interchangeable.
2. (Optional) If you turned on **Bring Your Own App Registration**, you can also supply your own pre-created managed identities instead of having Cortex XSIAM create them automatically. Toggle **Bring Your Own Scanner Managed Identities** on, and enter the Azure Resource Manager (ARM) resource ID of each of the following user-assigned managed identities (UAMIs). Enter all the identities. You need **Egress Proxy Resource ID** even if you set **Outpost networking** to **Egress routing off**. Each identity must be distinct and must be in the same subscription and tenant as the outpost. Keep the identities in a resource group that you own, outside the outpost resource group, so that they are not deleted if the outpost is removed.
   * **Agentless Disk Scanner Resource ID:** The identity that the agentless disk scanning (ADS) workload uses to snapshot and scan VM disks for vulnerabilities and malware. This is the `customer_uami_agentless_id` value that the helper shell script returns.
   * **DSPM Scanner Resource ID:** The identity that the DSPM scanner VM uses to scan data stores, such as Storage, SQL, and Cosmos DB, for sensitive data exposure. This is the `customer_uami_dspm_id` value.
   * **Registry Scanner Resource ID:** The identity that the registry scanner VM uses to pull and scan container images stored in Azure Container Registry. This is the `customer_uami_registry_id` value.
   * **Serverless Scanner Resource ID:** The identity that the serverless scanner VM uses to scan Azure Function Apps and other serverless code for vulnerabilities. This is the `customer_uami_serverless_id` value.
   * **Egress Proxy Resource ID:** The identity attached to the egress proxy VM. Scanner VMs route their outbound traffic, to Cortex XSIAM and to external services, through this proxy. This is the `customer_uami_proxy_id` value.
3. Enter the following details:
   * **Tenant ID:** The ID of the Microsoft Entra ID tenant in which you want to establish the outpost.
   * **Instance Name:** A name for the outpost. The instance name can be up to 255 characters.

</details>

<details>

<summary>GCP</summary>

* **Project ID:** The ID of the GCP project where Cortex XSIAM deploys the outpost.
* **Instance Name:** A name for the outpost. The instance name can be up to 255 characters.
* **Compute VPC ID:** This field appears only after you set **Outpost networking** to **Custom** in a later step. Enter the self-link of your VPC, for example `projects/my-project/global/networks/my-vpc`.

</details>

5. (Optional) Under **Cloud Tags**, click **Add Tag**, and enter a **Tag Key** and **Tag Value** for each tag to add to every new resource that Cortex XSIAM creates in the cloud environment. The `managed_by: paloaltonetworks` tag is defined by default and cannot be edited or removed. (GCP) GCP labels must use lowercase letters, numbers, or hyphens.
6. Under **Outpost networking**, choose how the outpost's scanner VMs reach the internet. For details about each option, see [Outpost networking options](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-outpost-concepts/outpost-networking-options.md).
   * **Default:** Scanner VMs reach the internet through an egress proxy that Cortex XSIAM manages. No networking setup is required.
   * **Custom:** You bring your own network (BYON). In the next step, you provide the network for each region. You can also route the outpost's outbound traffic through your own proxy.
   * **Egress routing off:** Scanner VMs have no outbound internet access. The wizard shows a warning that lists the Cortex XSIAM capabilities that do not work in this outpost.

     <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Important:</strong> With <strong>Egress routing off</strong>, vulnerability feeds, public registry scanning, SaaS DSPM sources, and threat intelligence do not work in this outpost.</p></div>
7. If you chose **Custom**, configure outbound access for the scanner VMs:
   * To use direct internet access through your own NAT gateway, leave **Outbound proxy** off. Ensure that your route tables and security groups allow outbound HTTPS (port 443) to `*.cortex.paloaltonetworks.com` and to cloud storage endpoints.
   * To route outbound traffic through your own forward proxy, toggle **Outbound proxy** on, and then configure the proxy.

<details>

<summary>Configure the outbound proxy</summary>

1. Enter the **Proxy address**, starting with `http://` or `https://`. You can use a hostname or an IP address. (AWS) You must use an IPv4 address. AWS does not support a hostname or an IPv6 address.
2. Enter the **Proxy port**, a number from 1 to 65535.
3. (Optional) If your proxy requires a username and password, toggle **Requires authentication** on.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> Cortex XSIAM does not store the proxy username and password. You provide them when you deploy the template. For Terraform, you pass them as the <code>proxy_username</code> and <code>proxy_password</code> variables. For CloudFormation, you enter them in the stack parameters.</p></div>
4. (Optional) If your proxy performs TLS inspection, toggle **SSL/TLS inspection** on, and provide the **CA Certificate (Server)** that the scanner VMs must trust, in PEM format. Do one of the following:
   * Click **Paste PEM**, and paste the certificate content.
   * Click **Upload file**, and then drag and drop or browse to the PEM file.

</details>

8. Click **Next**.

## Step 3. Configure regional settings

On the Regional Settings page, you choose the regions the outpost operates in. What you enter depends on the **Outpost networking** option that you chose on the Global Settings page.

<details>

<summary>Outpost networking: Default or Egress routing off</summary>

Cortex XSIAM manages the network resources in each region that you select.

1. Under **Regions**, select one or more regions from the **Select Regions** list.
2. Click **Next**.

</details>

<details>

<summary>Outpost networking: Custom</summary>

You provide your own network in each region. Only the regions you add here are enabled for the outpost. You cannot mix regions that use your network with regions that use a network that Cortex XSIAM creates in the same outpost.

1. Click **Add Region**.
2. From the **Region** list, select the region.
3. Enter the network details according to your CSP:

   * (AWS) **VPC ID**, and under **Subnets**, the **Zone Name** and **Subnet ID** of each subnet. To add a subnet in another Availability Zone, click **Add Subnet**. Each region must have at least one subnet.
   * (Azure) **Subnet Resource ID** and **Virtual Network ID**. The subnet must be in the virtual network that you enter.
   * (GCP) **Compute Subnetwork URI**, in the format `projects/<project>/regions/<region>/subnetworks/<subnetwork>`. The subnetwork must be in the VPC that you entered in **Compute VPC ID**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> To see the resources that Cortex XSIAM creates for you in this region, click the information icon on the region card.</p></div>
4. Click **Save Changes**. Cortex XSIAM validates the region settings and saves the region.
5. To add another region, repeat the previous steps. To change a saved region, click **Edit**. To remove it, click **Delete**.
6. Click **Next**.

</details>

## Step 4. Review the summary and get the template

On the **Summary** page, you review your settings and choose how to deploy the template. Cortex XSIAM generates the outpost template.

1. Review the **Account Details**, **Outpost networking**, **Outbound proxy**, and **Cloud Tags** sections. To change a setting, click **Back**.
2. Under **Outpost deployment**, choose how to deploy the template.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Important:</strong> (AWS) Choose your IaC tool carefully before you click an option. When you edit the outpost later, you can only download a template for the same IaC tool that you chose when you created it.</p></div>

   * **Automated:** (AWS, Recommended) Click **Execute in AWS** to open the AWS CloudFormation console with the pre-populated template. Before you click, verify that you are logged in to the AWS account where you deploy the outpost.
   * **Generate Template:** Click **CloudFormation** (AWS) to download the CloudFormation template file, or click **Terraform** to download the Terraform template archive.
3. Click **Done**.

{% hint style="info" %}
**Note:** If you leave the wizard before you deploy or download the template, the **Don't Forget** dialog appears. Click **Stay** to return to the wizard, or **Leave** to exit. The outpost does not appear on the **All Outposts** page until you deploy the template.
{% endhint %}

## Step 5. Execute the template in the CSP to deploy the outpost

In the previous step, you chose how to deploy the outpost template. Now, deploy the template in your CSP.

{% hint style="info" %}
**Note:** This step includes instructions for third-party CSP consoles and tools, which the CSP might change. For the most up-to-date and accurate instructions, see your CSP's documentation.
{% endhint %}

<details>

<summary>AWS: CloudFormation, automated (Execute in AWS)</summary>

1. **Check prerequisites:** Before you begin, ensure you have:
   * A browser session that is logged in to the AWS Management Console with the AWS account where you deploy the outpost.
   * Permission to create a CloudFormation stack, StackSets, and their resources in the outpost account. The template creates IAM roles, customer-managed IAM policies, policy attachments, and instance profiles, each of which requires IAM administration permission. Grant one of the following:
     * The AdministratorAccess managed policy, or
     * The IAMFullAccess managed policy (or a custom policy granting the `iam:Role`, `iam:Policy`, and `iam:InstanceProfile` actions) together with permission to create the other required resources (CloudFormation, EC2, VPC, S3, SQS, KMS, and SSM Parameter Store).
2. In the wizard, click **Execute in AWS**. The AWS CloudFormation console opens the **Quick create stack** page with the template and its parameters pre-populated.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Important:</strong> The link is valid for a limited time. Complete the following steps without delay.</p></div>
3. Under **Provide a stack name**, enter a **Stack name**. The stack name can include letters (A-Z and a-z), numbers (0-9), and hyphens.
4. Review the stack parameters. Cortex XSIAM pre-populates the parameter values from the wizard. Do not change them, with the following exceptions:
   * (Optional) You can change the **Resource name prefix**.
   * If you turned on **Requires authentication** for the outbound proxy, enter the **Proxy username** and **Proxy password**. Cortex XSIAM does not store them.
   * If the `AWSServiceRoleForEC2Spot` or `AWSServiceRoleForRedshift` service-linked role already exists in the account, set **Create service-linked roles (set to false if they already exist)** to `false`.
5. Under **Capabilities**, select **I acknowledge that AWS CloudFormation might create IAM resources with custom names**, and click **Create stack**.
6. Return to Cortex XSIAM. The dialog shows the status **Connecting**. Click **Close**.
7. To check the progress of the deployment, in the AWS CloudFormation console, open the **Stacks** list. Wait until the stack status is **CREATE\_COMPLETE**.

The template is deployed, and your outpost is created in **Connected** status. To view the outpost and its status, see [View and manage outposts](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/view-and-manage-outposts.md).

</details>

<details>

<summary>AWS: CloudFormation, manual (CloudFormation)</summary>

1. **Check prerequisites:** Before you begin, ensure you have:
   * Access to the AWS Management Console for the AWS account where you deploy the outpost.
   * The same permissions as for the automated CloudFormation deployment.
   * A CloudFormation template file that you downloaded within the last 7 days. The template contains a registration link that expires 7 days after download. If the link expires, the outpost cannot register with Cortex XSIAM, and you need to download a new template.
2. In the AWS Management Console, open **CloudFormation** and click **Create stack > With new resources (standard)**.
3. Select **Upload a template file**, choose the CloudFormation template file that you downloaded, and click **Next**.
4. Enter a stack name, and review the stack parameters. The downloaded template contains the parameter values from the wizard. Do not change them, with the following exceptions, and then click **Next**:
   * (Optional) You can change the **Resource name prefix**.
   * If you turned on **Requires authentication** for the outbound proxy, enter the **Proxy username** and **Proxy password**. Cortex XSIAM does not store them.
   * If the `AWSServiceRoleForEC2Spot` or `AWSServiceRoleForRedshift` service-linked role already exists in the account, set **Create service-linked roles (set to false if they already exist)** to `false`.
5. On the **Configure stack options** page, click **Next**.
6. Select **I acknowledge that AWS CloudFormation might create IAM resources with custom names**, and click **Submit**.
7. Wait until the stack status is **CREATE\_COMPLETE**.

The template is deployed, and your outpost is created in **Connected** status. To view the outpost and its status, see [View and manage outposts](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/view-and-manage-outposts.md).

</details>

<details>

<summary>AWS, Azure, and GCP: Terraform</summary>

1. **Check prerequisites:** Before you begin, ensure you have:
   * Installed Terraform on your local machine. You can download Terraform from the official [Terraform website](https://www.terraform.io/downloads.html) and follow the installation instructions for your operating system. (Azure) Use Terraform 1.9.4 or above.
   * Installed the CLI tool for your CSP: the AWS CLI (AWS), the Azure CLI (Azure), or the gcloud CLI (GCP).
   * A Terraform runner identity with the permissions to deploy the outpost. The permissions are the same as for a [standard outpost](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-standard-outposts/create-a-standard-outpost.md#step-3-execute-the-template-in-the-csp-to-deploy-the-outpost). If you set **Outpost networking** to **Custom**, the runner also needs the network permissions listed in the [custom networking prerequisites](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/custom-networking-prerequisites.md). If you bring your own app registration, the runner must be an owner of the app registration.
   * A Terraform template archive that you downloaded recently. The template contains a registration link that expires. If the link expires, download a new template from the wizard.
2. Open your local terminal (such as Command Prompt, PowerShell, or Terminal).
3. Log in to your CSP as the Terraform runner identity:
   * (AWS) Log in with the profile that you configured with the `aws configure sso` wizard, and confirm the identity:

     ```
     aws sso login --profile <my-profile>
     aws sts get-caller-identity
     ```
   * (Azure) Log in, select the outpost subscription, and confirm the identity. If the runner is a service principal, use `az login --service-principal`.

     ```
     az login
     az account set --subscription <subscription_id>
     az account show
     ```
   * (GCP) Log in, and confirm the identity. For a service account, use application default credentials with `gcloud auth application-default login`.

     ```
     gcloud auth login
     gcloud auth list
     ```
4. Create a directory on your local machine to store and run the Terraform code. If you are creating more than one outpost, you need a separate directory for each one:

   ```
   mkdir -p ~/terraform/custom-outpost-1
   ```
5. Navigate to the directory you created and extract the Terraform files.

   ```
   cd ~/terraform/custom-outpost-1
   tar -xzvf <your_template>.tar.gz
   ```
6. (Optional) If you set **Outpost networking** to **Custom**, [validate your network and proxy values](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/validate-your-network-and-proxy-values.md) in the `template_params.tfvars` file.
7. Initialize Terraform in your project directory:

   ```
   terraform init
   ```
8. Apply your Terraform configuration using the downloaded parameter file:

   ```
   terraform apply -var-file=template_params.tfvars
   ```

   If you turned on **Requires authentication** for the outbound proxy, pass the proxy credentials as variables:

   ```
   terraform apply -var-file=template_params.tfvars \
     -var="proxy_username=<user>" \
     -var="proxy_password=<password>"
   ```

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Important:</strong> Do not add <code>proxy_username</code> or <code>proxy_password</code> to the <code>template_params.tfvars</code> file. The file is intended to be checked into source control, so anyone who reads the repository can read credentials in it. Cortex XSIAM moves the credentials into your CSP's secret store during the first apply: AWS SSM Parameter Store (AWS), Azure Key Vault (Azure), or GCP Secret Manager (GCP).</p></div>
9. (Azure) When prompted for `var.input_ip_whitelist`, you can leave it empty to enable access from any public IP to the storage accounts. We recommend you to limit access to selected IPs. To limit access, enter a comma-separated list of public IP addresses, including your local machine's egress IP (to enable the completion of the Terraform run). For example: `8.8.8.8, 8.8.4.4`
10. Review the actions Terraform will perform and approve them by entering **yes**. If the plan fails, see the [Terraform validation reference](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/terraform-validation-reference.md) and [Custom outpost troubleshooting](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-outpost-troubleshooting.md).
11. Back up the Terraform state using one of the following methods, so that Terraform can upgrade or destroy the resources that it created for the outpost:
    * Create copies of the `terraform.tfstate` and `terraform.tfstate.backup` files. When you need to upgrade or destroy the outpost resources, move the copies to the working folder.
    * Use a backend block in your Terraform configuration to save the state. For more information, see [Backend block configuration overview](https://developer.hashicorp.com/terraform/language/backend).

The template is deployed, and your outpost is created in **Connected** status. To view the outpost and its status, see [View and manage outposts](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/view-and-manage-outposts.md).

</details>

## Step 6. Verify the outpost

After the template deployment completes, verify that the outpost is created and that it connects to Cortex XSIAM.

* **Check Cortex XSIAM:** The outpost appears on the **All Outposts** page at **Settings > Data Sources and Integrations > Outposts**. The outpost status is **Connected** after the outpost registers with Cortex XSIAM.
* **(Azure) Check federated credentials:** In the Azure portal, go to your **App Registration > Certificates & secrets > Federated credentials**. The list shows federated identity credentials that Cortex XSIAM created. If you brought your own app registration, the credentials are on your app registration.
* **Check scanning:** Cortex XSIAM begins discovery and scanning after you onboard the CSP. The first scan can take some time to start. If no scan starts after a reasonable interval, see [Custom outpost troubleshooting](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-outpost-troubleshooting.md).

## What's next?

Start (or continue) CSP onboarding. Run the onboarding wizard to generate an authentication template for [AWS](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/amazon-web-services-cloud-onboarding/onboard-amazon-web-services.md), [GCP](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/google-cloud-platform-cloud-onboarding/onboard-google-cloud-platform.md), or [Azure](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/microsoft-azure-cloud-onboarding/onboard-microsoft-azure.md).

If you set **Outpost networking** to **Custom**, review [Maintain your network after deployment](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/maintain-your-network-after-deployment.md).


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/create-a-custom-outpost.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.
