> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/saral-easy-installer/saral-production-user-installation-guide/automating-the-infra-provisioning-and-install-of-the-saral-application/what-automation-does.md).

# What automation does

You should have the entire Saral Infra setup on you AWS account Infra structure Which Includes the following components

<table data-full-width="true"><thead><tr><th width="64">Sr No</th><th>Name of Resource  Provisioned</th></tr></thead><tbody><tr><td>1</td><td><p> EKS cluster with fargate Nodes</p><p></p></td></tr><tr><td>2</td><td> VPC</td></tr><tr><td>3</td><td>Subnets (2-Private and 2-Public subnet for EKS cluster 2-Private subnets for Document DB)</td></tr><tr><td>4</td><td>Application load balancer controller</td></tr><tr><td>5</td><td>NAT gateway</td></tr><tr><td>6</td><td>Elastic IP</td></tr><tr><td>7</td><td>AWS document DB</td></tr></tbody></table>

The following is the reference architecture of the Infra provisioned by the installer

<figure><img src="/files/FDqv3bFMSSW5FWLjEbrs" alt=""><figcaption><p>Saral AWS reference Architecture</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://saral.sunbird.org/saral-easy-installer/saral-production-user-installation-guide/automating-the-infra-provisioning-and-install-of-the-saral-application/what-automation-does.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.