Let's Encrypt (Rails/Puma/NginX/AWS)

I have set up Let's Encrypt on a Rails site hosted on a stand alone AWS server. This took me about two and half days to configure in part, due to issues I experienced with AWS but mostly due to the conflicting information I found online. I think that it may be worth adding specific instructions for AWS/Rails users or perhaps making changes to the Virtual Environment that can accommodate said users in future.

1) Deploy the most recent version of the site to AWS Elastic Beanstalk. The Gemfile had to contain puma and rbenv.
2) sudo yum install git
3) sudo yum install libffi-devel
4) sudo yum install puppet
5) cd /var/app/current
6) git clone https://github.com/letsencrypt/letsencrypt

7) ./letsencrypt-auto --server \
    https://acme-v01.api.letsencrypt.org/directory --help

8) ./bootstrap/venv.sh

9) ./letsencrypt-auto certonly \
      -a standalone \
     -d kohrvid.com \
     -d www.kohrvid.com \
     --server https://acme-v01.api.letsencrypt.org/directory \
     --agree-dev-preview --debug

Please note, my Let'sEncrypt installation required me to add the "--debug" flag because it believed I had python2.6 installed. The version of python on my ec2 server is 2.7.10.

10) Two puma files were set up in /etc/init
       puma.conf can be found here --> http://pastebin.com/x2DwqgWM
       puma-manager.conf --> http://pastebin.com/4G84xY8j

11) Delete /etc/nginx/
12) sudo yum remove nginx
13) sudo yum install nginx
14) In /etc/nginx/conf.d create a new file named “default.conf” which can be seen here --> http://pastebin.com/gCCUAYUd
15) Replace contents of /etc/nginx/nginx.conf with the following --> http://pastebin.com/iuWEHEnj
16) Replace contents of /etc/nginx/nginx.conf.default with the following --> http://pastebin.com/Z4z1c8nD
17) sudo start puma
18) sudo service nginx restart

At this point, it should be possible to load the site in a browser with an SSL certificate.