# AWS ELB

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6d_d3kKn_olenSKMJD%2Fpp_img_3_col_ELB_7_378x171.6072b3759f48035df87f576f58fc26959b7138a5.png?alt=media\&token=2c2efe8e-67f8-481a-bb3b-f0f02d4c67f3)

[AWS](https://aws.amazon.com/) provides a powerful cloud load balancer service called [Elastic Load Balancer](https://aws.amazon.com/elasticloadbalancing/?nc1=h_ls). There are a few types of it but on this page, AWS [ALB](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html) (Application Load Balancer) is the target.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6df4Uygnrn3yiONtds%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%207.59.06.png?alt=media\&token=4e019be2-58e7-46cd-a335-d46f67aed99f)

Select the Application Load Balancer on the load balancer creation page.

![](/files/-MPcGqVc3BpAFHFWU-pF)

Set the load balancer's name and further details. Since we are going to use SSL with the load balancer, the lister for HTTPS should be also added in this section.

![](/files/-MPcGvgNly99gmqrAqj8)

Select the SSL certificate you already have on AWS [ACM](https://aws.amazon.com/certificate-manager/?nc1=h_ls) (Amazon Certificate Manager). You could always issue a new one on the fly by going to the ACM console without any charge.

![](/files/-MPcGxyZ-LboaKh2Jc0j)

Select (or create) the security group with the 80 / 443 ports opened.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6dhdxUFlqHg53lfm4z%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%207.59.45.png?alt=media\&token=c1223bda-c978-4dcd-a0d8-85bcdca64d9d)

Create a load balancer target group. This will be a pool of servers to which a load balancer can forward the traffic. Please make sure to set the health check path to `/v1/health`. This would make the load balancer call the HollaEx health page to check the target pool availability.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6diq66qob__lsdq3QM%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%207.59.51.png?alt=media\&token=f3d3f1ce-a81a-41aa-b14a-9804c886cf43)

Add your instance with HollaEx running at here. This would be added as a member of the target group pool.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6dk30GsikuxmOP0E50%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%208.26.58.png?alt=media\&token=bac783c4-01d4-484e-a0df-fd3e3210885f)

Once you have reviewed your configurations and created a load balancer, you would able to see a DNS name for it. This should be bound with your domain(s) for the domain access.

There are 2 domains required for the exchange operation. One for the API server, and the other for the exchange website. If your domain is `example.com`, we recommend you to use `api.example.com` as the API domain, and `example.com` as the website domain. These domains should be bound with the load balancer DNS name with CNAME.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6dljccX1uEDKFi0yXK%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%208.35.22.png?alt=media\&token=cc1fed40-6ede-415d-8917-fdfd62321dda)

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6dlmiesCVFzfeo9v3K%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%208.35.25.png?alt=media\&token=7069a9a4-7f9d-4598-8067-dc95c8ad3c0a)

Once it's all set, there's a command needed to be run using the HollaEx CLI. The [`hollaex prod`](https://docs.bitholla.com/v/master/hollaex-kit/commands#hollaex-prod) command will help you to apply domains for production on the exchange.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6dnEDHive8_U3wAQ5N%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%206.00.10.png?alt=media\&token=b2a2aaa7-8c8a-4750-a12e-2f0f1e3ed9d5)

Apply the domains you've just configured on your DNS. Since we've already bound an SSL on the load balancer level, you should not issue an SSL through the HollaEx CLI.

![](https://gblobscdn.gitbook.com/assets%2F-LhnROlk-mZfTYA5IOjC%2F-M6d_Fhwq-ZRZX2hY56g%2F-M6dnoCn-gBDoVmmCW_Y%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202020-05-06%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%206.43.28.png?alt=media\&token=0d6e6848-b9b1-4adb-92bc-7fe360742db8)

Once everything is done, try to reach the exchange health page through your domain. If it's all accessible, you are done. You can now proudly introduce your exchange to the world. Have fun :)


---

# Agent Instructions: 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:

```
GET https://docs.hollaex.com/advanced/load-balancer/aws-elb.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.