> 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-cloud-outposts/appendix-b-managed-resources.md).

# Appendix B:   Managed resources

This reference lists the resources that are installed and managed for working with outposts.

## Resource properties

Each resource has, but is not limited to, the following properties:

* Scope (global, regional, or zonal)
* Provisioning method (static or dynamic, created by Terraform or by Cortex Cloud)
* Resource name
* Resource type
* Output name (specific instance of resource of specific type)
* Cortex Cloud modules that require the resource
* Purpose or use case

## Resource reference table

This table lists the resources deployed on customer-managed outposts by CSP.

This document lists static resources only. Dynamic resources might also be deployed depending on the scan processes.

{% hint style="info" %}
**Note:** \
The resource tables are subject to change. The tables are up-to-date as of August 27, 2026.
{% endhint %}


---

# 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-cloud-outposts/appendix-b-managed-resources.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.