> 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-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-creation-workflow.md).

# Outpost creation workflow

Learn about the creation process for an outposts, which facilitate security scanning performed on infrastructure in a cloud account owned by you.

{% hint style="info" %}
**License type:** This feature is included with a Cortex XDR license that has the Cloud Posture Security or Cloud Runtime Security add-on.
{% endhint %}

This page describes the overall flow for creating outposts for different CSPs.

{% hint style="info" %}
**Important**: While outposts provide maximum control over the scanning environment, cloud scan mode is the recommended default for most organizations. For details, see [When to choose outpost scan](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-fundamentals-and-planning.md#when-to-choose-outpost-scan).
{% endhint %}

Creating an outpost comprises the following phases:

{% stepper %}
{% step %}

### Phase 1: Planning

Determine if an outpost infrastructure meets your security needs.

Review [Outpost fundamentals and planning](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-fundamentals-and-planning.md) to determine your outpost configuration.
{% endstep %}

{% step %}

### Phase 2: Creating the outpost

Create your outpost running the outpost creation wizard in Cortex XDR to create an outpost authentication Terraform template. This template establishes trust with the CSP and grant the necessary permissions to Cortex XDR.

At this stage, the outpost is in **Pending** status.
{% endstep %}

{% step %}

### Phase 3: Deploying the outpost

Deploy your outpost by executing a Terraform template in the CSP.

At this stage, the outpost is still in **Pending** status.
{% endstep %}

{% step %}

### Phase 4: Onboarding the CSP

Run (or resume) the CSP onboarding wizard in Cortex to generate an authentication template for the relevant CSP.

* [Onboard Amazon Web Services (AWS)](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/amazon-web-services-cloud-onboarding/onboard-amazon-web-services.md)
* [Onboard Microsoft Azure](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/microsoft-azure-cloud-onboarding/onboard-microsoft-azure.md)
* [Onboard Google Cloud Platform (GCP)](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/google-cloud-platform-cloud-onboarding/onboard-google-cloud-platform.md)

Execute the authentication template in the CSP to onboard and ingest its data sources, using the outpost you created.

At this stage, the outpost is in **Connected** status.
{% endstep %}
{% endstepper %}


---

# 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-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-creation-workflow.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.