> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security.md).

# Cloud Deployment

OX cloud security integrations link your cloud and Kubernetes environments directly to OX so you can see what is running, where it is deployed, and how security findings relate to real workloads.

By connecting [GCP](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security/gcp-and-gke-1.md), [GKE](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security/gcp-and-gke-1/gcp-and-gke.md), [AWS](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security/aws-1.md), [Azure Cloud](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security/azure-new.md), and [Amazon EKS](https://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security/eks.md), OX pulls cloud and runtime context into the platform. This context lets you:

* Map applications, repositories, and images to the cloud resources and clusters where they run.
* Enrich issues with deployment and runtime metadata to support prioritization.
* Filter and act on findings based on whether code, images, or workloads are actively running in your environment.

These connectors work alongside your source control and pipeline integrations. Together, they give you a full view from code and build, through deployment, to runtime in the cloud.

When you connect GKE or Amazon EKS, OX also adds Kubernetes reachability context. This shows whether a vulnerable workload or service is exposed to cluster or external traffic, helping you prioritize findings based on real access paths rather than configuration alone.


---

# 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://docs.ox.security/ox-integrations/3rd-party-integrations/cloud-security.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.
