Select the Application Load Balancer at the load balancer creation page.
Set the load balancer 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.
Select the SSL certificate you've already got on AWS ACM (Amazon Certificate Manager). You could always issue a new one on the fly by going to the ACM console without any charge.
Select (or create) the security group with 80 / 443 port opened.
Create a load balancer target group. This would be a pool of servers 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 to call HollaEx health page to check the target pool availability.
Add your instance with HollaEx running at here. This would be added as a member of the target group pool.
Once you reviewed your configurations and create a load balancer, you would able to see a DNS name for it. This should be bind 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 bind with the load balancer DNS name with CNAME.
Once it's all set, there's a command needed to be run at the HollaEx CLI.
hollaex prod command would help you to apply domains for production on the exchange.
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.
Once everything is done, try to reach the exchange health page through your domain. If it's all accessible, you are done. You could proudly introduce your exchange to the world now. Have fun :)