> 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-xpanse/integrations/ingest-cloud-resources-from-prisma-cloud/prisma-cloud-resource-types.md).

# Prisma Cloud resource types

This lists below include the types of cloud resources that may be ingested into Cortex Xpanse from Prisma Cloud CSPM via the cloud integration. Cloud resources are ingested four times per day. Learn more about this integration [here](/cortex-xpanse/integrations/ingest-cloud-resources-from-prisma-cloud.md).

{% hint style="info" %}

### Note

Cortex Xpanse pulls in Compute Instances from AWS, GCP, and Azure via the direct integration. More resource types are pulled in via the Prisma Cloud integration.
{% endhint %}

**Alibaba resource types**

* ECS

**AWS resource types**

* Amazon Elasticsearch Service
* Amazon MQ
* Amazon Sagemaker
* API Gateway
* CloudFront
* EC2
* EKS
* Elastic Beanstock
* ELB
* ELBv2
* EMR
* NAT Gateway
* RDS
* RedShift
* Route 53
* S3
* Workspaces

**Azure resource types**

* AKS
* API Management Service
* App Service
* Application Gateway
* Blob Storage
* CDN
* Cosmos DB
* Data Analytics
* Data Lake Store
* Databricks Workspace
* Event Hub Namespace
* Firewall
* Key Vault
* Load Balancer
* Logic App Workflow
* MySQL
* PostgresSQL
* Public IPs
* SQL DB
* VM

**Google resource types**

* App engine
* Cloud DNS
* Cloud NAT
* Cloud Run
* Cloud SQL
* Cloud Storage
* GCE
* Kubernetes Engine
* Load Balancer

**Oracle resource types**

* Public IPs


---

# 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/cortex-xpanse/integrations/ingest-cloud-resources-from-prisma-cloud/prisma-cloud-resource-types.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.