> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/32/cloud-service-providers/cloud-accounts-discovery-pcce.md).

# Cloud Discovery

It’s difficult to ensure that all your apps running on all the different types of cloud services are being properly secured. If you’re using multiple cloud platforms, you might have many separate accounts per platform. You could easily have hundreds of combinations of providers, accounts, and regions where cloud native services are being deployed.

Cloud discovery helps you find all cloud-native services being used on AWS, Azure, and Google Cloud, across all regions, and across all accounts. It enables you to continuously monitor these accounts, detect when new services are added, and report on the services that are unprotected, so that you can mitigate your exposure to rogue deployments, abandoned environments, and sprawl.

Cloud discovery offers coverage for the following services.

**Registries:**

* AWS
* Azure
* Google Artifact Registry
* Google Container Registry<sup>1,2</sup>

**Serverless functions:**

* AWS
* Azure
* Google Cloud

<sup>3</sup> **Managed platforms:**

* AWS ECS
* AWS EKS
* Azure Kubernetes Service (AKS)
* Azure Container Instances (ACI)
* Google Kubernetes Engine (GKE)

**Virtual machines:**

* AWS EC2 instances
* Azure VMs<sup>3</sup>
* Google Cloud Platform (GCP) Compute Engine VM instances<sup>3</sup>

<sup>1</sup>Although Artifact Registry supports a number of content types (for example, Java, Node.js, and Python language packs), Prisma Cloud only supports discovering and scanning Docker images.

<sup>2</sup>Prisma Cloud doesn’t support scanning Helm charts saved as OCI images and stored in Artifact Registry. The OCI image that represents a Helm chart has a single layer that contains the Helm package. It is only a way to store a Helm chart, but it has no meaning in terms of a container. Prisma Cloud has no way to run the image to scan it. Note that Helm charts stored as OCI images will be shown in the list of resources discovered in the registry because we can’t indicate their type until we actually pull and scan them.

<sup>3</sup>Auto-defend is currently not yet available for these services. Auto-defend utilizes rule-based policies to automatically deploy Prisma Cloud to protect resources in your environment.

## Troubleshooting

Ensure you have the right [permissions](/admin-guide/32/configure/permissions.md) for the account before you start with cloud discovery.

### Empty results from Cloud Discovery

Cloud discovery results are visible per account. If you have multiple credentials associated with the same account, the results are only displayed for one credential to avoid duplication. The other credentials for the same account will show empty results. To view comprehensive results for all credentials, navigate to Cloud Radar **Radars > Cloud**.


---

# 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://docs.prismacloud.io/admin-guide/32/cloud-service-providers/cloud-accounts-discovery-pcce.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.