> 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/domain-mapping-on-aws-route53.md).

# Domain mapping on AWS Route53

Guide on mapping domain names on AWS Route53 (WORK IN PROGRESS)

AWS Route 53 is a highly scalable and reliable Domain Name System (DNS) web service designed to route end users to internet applications by translating human-readable domain names like [www.example.com](http://www.example.com) into IP addresses like 192.0.2.1. It integrates seamlessly with other AWS services, providing developers with a robust toolset for managing DNS records, domain registration, and health checking to ensure high availability and performance of web applications.

## Procedure

The steps to perform domain mapping on AWS Route53 are given below.

1. Login to AWS. Navigate to the Route53 console on AWS dashboard and select ***hostedzone***.

Notes:

If the ***hostedzone*** is not created, you have to create a new ***hostedzone***.

2. Click the ***Create Record*** button and do mapping according to your environment domain.


---

# 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/domain-mapping-on-aws-route53.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.