> 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/reference-documents/saral-infra-requirements-and-associated-cost.md).

# SARAL Infra Requirements & Associated Cost

**Dev Infrastructure:**

<table><thead><tr><th width="73">No</th><th width="510">Resource Name</th><th width="284">What it hosts</th><th width="119">Environment</th><th>Resource Type</th><th width="301">Configuration</th><th width="191">Monthly Cost in USD</th><th>Usage Scenario</th></tr></thead><tbody><tr><td>1</td><td>Saral-Sandbox-Instance</td><td>Backend (Saral Node application)</td><td>Sandbox</td><td>EC2 Instance</td><td>Instance Type<br>t3a.medium | Family: t3a |<br>2 vCPU | 2 GiB Memory<br>Storage GP3: 30GB"</td><td>$20.70</td><td></td></tr><tr><td>2</td><td>Saral-Sandbox-DB-Instance</td><td>Mongo DB</td><td>Sandbox</td><td>EC2 Instance</td><td>Instance Type<br>t3a.medium | Family: t3a |<br>2 vCPU | 2 GiB Memory<br>Storage GP3: 30GB"</td><td>$20.70</td><td></td></tr><tr><td>3</td><td>Saral-Sandbox-Elastic IP for DB-Instance and Sandbox-Instance</td><td>Elastic IP</td><td>Sandbox</td><td>Public static IP</td><td></td><td>$7.20</td><td></td></tr></tbody></table>

**Production Infrastructure:**

<table><thead><tr><th width="68">No</th><th width="171">Resource Name</th><th width="140">What it hosts</th><th width="135">Environment</th><th width="120">Resource</th><th width="147">Configuration</th><th width="182">Monthly Cost in USD</th><th width="382">Usage Scenario</th><th data-hidden></th></tr></thead><tbody><tr><td>1</td><td>Amazon EKS</td><td>EKS Controle Plane</td><td>Production</td><td>EKS Cluster</td><td>NA</td><td>$73.00</td><td></td><td></td></tr><tr><td>2</td><td>AWS Fargate Nodes</td><td>Backend (Saral Node application)</td><td>Production</td><td>Fargate nodes</td><td>6</td><td>$56.79</td><td>3,000 Users (with peak concurrency of 500-1000 users) can Successfully Login and Submit the Marksheet for 4,50,000 Students at a 1500 students save per second. Test Duration 5 Minutes with average response time of 10-20 Seconds with 100% Success rate</td><td></td></tr><tr><td>3</td><td>Network Address Translation (NAT) Gateway</td><td>Elastic IP</td><td>Production</td><td>NAT gateway</td><td>1</td><td>$41.72</td><td></td><td></td></tr><tr><td>4</td><td>Application Load Balancer</td><td>Load balancer</td><td>Production</td><td>Load balancer</td><td>1</td><td>$29.13</td><td></td><td></td></tr><tr><td>5</td><td>Amazon DocumentDB (with MongoDB compatibility)</td><td>Mongo DB</td><td>Production</td><td>Database</td><td>1</td><td>$235.45</td><td></td><td></td></tr></tbody></table>


---

# 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://saral.sunbird.org/saral-easy-installer/reference-documents/saral-infra-requirements-and-associated-cost.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.