> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/getting-started/deploy-enforcement-point/docker/single-docker.md).
# Single Docker
CloudGuard WAF can be deployed as a single docker containing a managed reverse proxy server and the CloudGuard Security agent.
## Configuration
When creating either Web application or Web API assets:
* Define the URLs that Users/Clients will access (1)
* Define the Application/API URL that will be accessed by the Reverse Proxy (2)
{% hint style="info" %}
If you plan to deploy in Azure App Services the URLs should be http and not https, because Azure is handling the SSL encryption opening by itself. Certificate configuration will be done in Azure (explained later)
{% endhint %}
* Make sure to select a Docker based profile if creating a new profile to protect the asset (keep the default settings for **Single docker container** and without selecting to manage NGINX yourself):
{% hint style="info" %}
For deployment in Azure App Services, you can skip the Certificates page in the Wizard above.
{% endhint %}
## Deployment options
Select the deployment option that best fits your environment and requirements:
Manually deploying using the docker command:
{% content-ref url="/pages/z2qByl0nUxvworJXQas5" %}
[Deployment using 'docker' command](/getting-started/deploy-enforcement-point/docker/single-docker/deployment-using-docker-command.md)
{% endcontent-ref %}
Deployment using Azure App Services:
{% content-ref url="/pages/bBIhxegGtaeCggh40dQK" %}
[Deployment in Azure App Services](/getting-started/deploy-enforcement-point/docker/single-docker/deployment-in-azure-app-services.md)
{% endcontent-ref %}
---
# 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://waf-doc.inext.checkpoint.com/getting-started/deploy-enforcement-point/docker/single-docker.md?ask=&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.
