It's only been a few years since you had to pay in order to get a trusted SSL Certificate. Then just about 2 years ago, the EFF together with the Mozilla Foundation and several others have decided join forces and launched Let's Encrypt with the goal of having 100% of the web traffic run over HTTPS by issuing domain validated certificates - free of charge! You can also make this a bit shorter by just passing the entire Lexicon command line as the --manual-auth-hook flag to Certbot and avoid creating a separate hook file, however that is avoided here to try draw a clear (newbie-friendly) delination between components here. If you need help, please ask on the Let's Encrypt Community forums:) ! ????ssl?????,???http??????????,?????????????https??ssl??,????,??????ssl????????????web?????????ss Installation and Usage of Certbot on CentOS to Obtain a Let's Encrypt Wildcard TLS/SSL Certificate. - centos-wildcard-certbot.md I'm using a wildcard cert from letsencrypt. Currently there is only one way how to verify that you hold the domain you are requesting cert for: creating TXT record in that domain. As others have mentioned, the problem with this approach is the lack of automation. The TXT record that is provided changes every renewal, meaning that you'd have to update DNS records for your domain manually every 90 days. I use Cloudflare for my DNS, and they have an API that allows updating of DNS records. ?????????????????????????????? ??? ???????????https????????? ?webroot??????(??????????????????????) ????????? How can I run and automated scalable version of Let's encrypt Certbot on Elastic beanstalk ? Haven't found an answer on the web so I put together this .ebextension. I hope you find it useful. Clone via HTTPS Clone with Git or checkout with SVN using the repository's web address. 2017-10-11 ??: renew ?? 2017-10-12 ??: ?? -webroot ???? 2018-03-23 ??: ????? ??????????? HTTPS ????(?) ,?????? Let's Encrypt ??? HTTPS ?????????? ??????????????????????? H