> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/setup/installation.md).

# Installation

Installation steps for DIGIT HCM

### DIGIT HCM Installation:

The DIGIT HCM installation comprises five steps to create a new production-ready server that can be scaled on demand. The installation process is currently supported only for AWS. However, support for other cloud platforms such as Azure and GCP will be available in the future.

**Step 1:** [**Execute GitHub Action for installation**](/health/v1.5/setup/installation/install-using-github-actions-in-aws.md): Execute a GitHub action for the installation process.&#x20;

**Step 2**: [**Execute the System Data Setup**](/health/v1.5/setup/installation/system-data-setup.md): Execute this setup to load system-required data.

**Step 3:** [**Execute the Project Data Setup**](/health/v1.5/setup/installation/project-data-setup.md): Execute the minimum setup data required to run a campaign.

**Step 4:** [**Generating the APK for the Server**](/health/v1.5/setup/installation/setup-mobile-app.md): Generate the APK pointing to the server as mentioned above.

**Step 5:** [**Kibana Dashboard Setup**](/health/v1.5/setup/installation/setup-kibana-dashboard.md)**:** To create and configure health campaign dashboards in a different space within Kibana.

### **DIGIT HCM Cleanup:**&#x20;

After completing the HCM Installation, if you want to uninstall/destroy the server, follow the steps mentioned in [**Server Cleanup**](/health/v1.5/setup/installation/server-cleanup.md).


---

# 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.digit.org/health/v1.5/setup/installation.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.
