> 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/data-security-documentation/onboard-and-configure/csp-onboarding/outpost-onboarding/outpost-creation-workflow.md).

# Outpost creation workflow

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-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/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-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/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 Cloud to create an outpost authentication Terraform template. This template establishes trust with the CSP and grant the necessary permissions to Cortex Cloud.

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-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/amazon-web-services-cloud-onboarding/onboard-amazon-web-services.md)
* [Onboard Microsoft Azure](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/microsoft-azure-cloud-onboarding/onboard-microsoft-azure.md)
* [Onboard Google Cloud Platform (GCP)](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/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 dynamically by asking a question.

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

```
GET https://cortex-docs.paloaltonetworks.com/data-security-documentation/onboard-and-configure/csp-onboarding/outpost-onboarding/outpost-creation-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.