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

# Domain mapping on AWS Route53

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

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

```
GET https://docs.openg2p.org/1.3/deployment/deployment-guide/aws/domain-mapping-on-aws-route53.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.