# Obtaining and Installing a proper SSL certificate for the AWS Standard Hosted Solution **URL:** \ **Category:** Support\ **Tags:** aws\ **Created:** [June 4, 2018, 2:42am UTC](https://community.open-emr.org/t/obtaining-and-installing-a-proper-ssl-certificate-for-the-aws-standard-hosted-solution/10258 "2018-06-04T02:42:56Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Ralf\_Lukner](https://community.open-emr.org/user_avatar/community.open-emr.org/ralf_lukner/32/11962_2.png) [@Ralf\_Lukner](https://community.open-emr.org/u/Ralf_Lukner)\ **Post date:** [July 5, 2019, 8:03am UTC](https://community.open-emr.org/t/obtaining-and-installing-a-proper-ssl-certificate-for-the-aws-standard-hosted-solution/10258/8 "2019-07-05T08:03:33Z")
I figured out one very convoluted but effective way on how to get HTTPS working on Amazon AWS. - Use Amazon Route 53 to host a domain. Then use GoDaddy as the certificate authority to generate the certificates. Why Amazon cannot do this all, I have no clue. There might be a way to get GoDaddy hosted domain certificates to work as well. - copy the certificates both to the instance /etc/ssl/certs and to the respective docker (so it doesn’t matter where apache gets them … they are there and they are identical). - modify the ssl.conf and openemr.conf file to point at the SSL certificates … who knows which one is really used … - I also used an .htaccess file to make sure that http is forced to https. - Configure all the SSL stuff in OpenEMR Administration (look for relevant fields in security etc.) Feel free to ask me more details. I’m sure a much cleaner way to do this will evolve now that I have been able to get this to work at all … whew … I’m sure the above is not yet easy to reproduce, but I’m willing to help others out in this. –Ralf --- _[View the full topic](https://community.open-emr.org/t/obtaining-and-installing-a-proper-ssl-certificate-for-the-aws-standard-hosted-solution/10258)._