> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/17.latest/run-in-production/infrastructure-and-ops.md).

# Infrastructure & Ops

Set up servers, run health checks, and manage database availability and distributed locks for Umbraco in production.

This section covers the operational aspects of running Umbraco in production. Topics include server setup, health monitoring, database availability, and distributed locking.

* [Server Setup](/umbraco-cms/17.latest/run-in-production/infrastructure-and-ops/server-setup.md) - configure servers for use with Umbraco, including load balancing and environment-specific setup.
* [Health Checks](/umbraco-cms/17.latest/run-in-production/infrastructure-and-ops/health-check.md) - monitor the state of your Umbraco project using built-in and custom health checks.
* [Database Availability](/umbraco-cms/17.latest/run-in-production/infrastructure-and-ops/database-availability.md) - understand how Umbraco checks database availability on startup and how to customize that behavior.
* [Distributed Locks](/umbraco-cms/17.latest/run-in-production/infrastructure-and-ops/distributed-locks.md) - learn how Umbraco uses database locks during save operations to prevent concurrency issues.


---

# 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.umbraco.com/umbraco-cms/17.latest/run-in-production/infrastructure-and-ops.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.