> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/use/getting-started/install.md).

# Install

To commence your journey with SunbirdEd, follow these guidelines: 

* **Choose Cloud Platform:** Your first step is to create an account on a cloud platform that best fits your needs. Whether you opt for Azure, AWS, GCP, or OCI, your choice should be guided by considerations like your budget, available technical resources, and the degree of control you wish to have over your deployment. You can also leverage an existing account if it aligns with your requirements.
* **Provision Cloud Infrastructure**: In order to provision the infra please refer to the [Pre-requisites](/use/getting-started/pre-requisites.md) and ensure the requirements are met.

## Prepare the Environment

1. Copy the template directory

```
bash cd terraform/<cloud-provider> # Replace <cloud-provider> with your cloud provider 
cp -r template <env> # for reference
```

2. Ensure the required values in `<env>/global-values.yaml` are populated properly by following the prerequisites.

## Provision Infra and Install Services

In order to provision infra and install all services, run the following command

1. Ensure you are in the respective environment related folder<br>

   ```
   cd terraform/<cloud-provider>/<env>
   ```
2. Run the `install.sh` script that provisions the infra and installs the services<br>

   ```
   time ./install.sh
   ```

> NOTE: Currently there is only support for Azure. To add support for a new cloud provider, follow this [document](/use/source-code/easy-installer/adding-support-for-a-new-cloud-provider.md). We welcome contributions!


---

# 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://ed.sunbird.org/use/getting-started/install.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.