From the AWS EC2 Dashboard, choose the elastic load balancer created for Yarkon. Add an HTTPS listener, allowing traffic from the internet through port 443 to port 80 on the EC2 instance (assuming that you have Yarkon Server listening on port 80), and set the certificate for this route to be the aforementioned.
If you had port 80 opened on the load balancer while you were setting up the cert (as can be seen in the image above), once you confirm that port 443 works, you can safely remove the route for port 80.
If you have Yarkon Server running on a non EC2 server, you can secure it the same way you handle your other servers.
The process might be slightly different depending on the registrar you use for your domain names; in case you use AWS Route53 to manage your domains, as most AWS clients do, you will have to assign an A record for the server IP or the reverse proxy you use in front of it, for instance:
Next you’d need to ensure only secure HTTP (HTTPS) traffic can access the Yarkon Application. For that you’d need an SSL certificate that matches the DNS name you created before, or a star (*) certificate that matches the domain.
If you are using a reverse proxy in front of the server (very common), you should install the SSL cert on it as you do for any other server.
Yarkon Server itself does not support SSL termination at this time.
Next Step – Customize the look and feel
Go back to Getting Started