> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/installation-setup/installation/amazon-web-services/lightsail.md).
# LightSail
To deploy ngSurvey on an Amazon LightSail instance you may select Ubuntu as your OS and add following startup script to your image. As soon as the LightSail instance will be ready ngSurvey will start installing itself and be ready to use on your LightSail public within a couple of minutes. \
\ **To get your access token contact ngSurvey's sales team.**
{% hint style="warning" %}
An instance with minimum 4gb of ram is required.
{% endhint %}
```
curl -o ngs-ubuntu-docker.auth.sh https://ngsurvey.s3.eu-central-1.amazonaws.com/ngs-ubuntu-docker.auth.sh
chmod +x ./ngs-ubuntu-docker.auth.sh
./ngs-ubuntu-docker.auth.sh ngsurvey YOUR_ACCESSTOKEN
```
If you prefer to use CentOS as your host you may use following script as launch script
```
curl -o ngs-centos-docker.sh https://ngsurvey.s3.eu-central-1.amazonaws.com/ngs-centos-docker.auth.sh
chmod +x ./ngs-centos-docker.auth.sh
sed -i 's/\r$//' ngs-centos-docker.auth.sh
./ngs-centos-docker.auth.sh ngsurvey YOUR_ACCESSTOKEN
```
---
# 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.ngsurvey.com/installation-setup/installation/amazon-web-services/lightsail.md?ask=&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.