> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/operations/deployment/deployment-guide/aws.md).

# AWS

Additional guides related to deployment on AWS

{% hint style="info" %}
**For a standard production deployment on AWS, start with** [**Stage 2 — Provisioning**](/operations/deployment/infrastructure-setup/provisioning.md)**.** The bundled `openg2p-aws-provision.sh` creates the production VMs (Reverse Proxy, Compute, Storage, and — with `backup_node.enabled: true` — the Backup node), networking, and the stable Elastic IP for the Reverse-Proxy node. The pages in this section are **manual / reference material** for the older AWS-LB exposure pattern and individual AWS tasks (ACM certificates, security groups, Route 53 mappings); they are not part of the supported automated flow.
{% endhint %}

These guides cover individual AWS console tasks that some deployments still perform by hand:

* [Create ACM Certificate on AWS](/operations/deployment/deployment-guide/aws/create-acm-certificate-on-aws.md)
* [Create Security Group on AWS](/operations/deployment/deployment-guide/aws/create-security-group-on-aws.md)
* [Domain mapping on AWS Route53](/operations/deployment/deployment-guide/aws/domain-mapping-on-aws-route53.md)
* [Make Environment Publicly Accessible using AWS LB Configuration](/operations/deployment/deployment-guide/aws/make-environment-publicly-accessible-using-aws-lb-configuration.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.openg2p.org/operations/deployment/deployment-guide/aws.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.