certbot/certbot-route53
Zach Shepherd c9ff9e3c7a route53: add unit tests (#4725)
This change introduces unit tests to cover all lines of the route53
plugin except for the timeout in `_wait_for_change`.
2017-05-31 15:25:24 -07:00
..
certbot_route53 route53: add unit tests (#4725) 2017-05-31 15:25:24 -07:00
examples route53: tweak source organization to match other packages (#4729) 2017-05-26 11:28:55 -07:00
tools route53: tweak source organization to match other packages (#4729) 2017-05-26 11:28:55 -07:00
.gitignore Moved files to 'certbot-route53' 2017-05-18 16:44:05 -07:00
LICENSE Moved files to 'certbot-route53' 2017-05-18 16:44:05 -07:00
MANIFEST.in Moved files to 'certbot-route53' 2017-05-18 16:44:05 -07:00
README.md route53: tweak source organization to match other packages (#4729) 2017-05-26 11:28:55 -07:00
setup.cfg Moved files to 'certbot-route53' 2017-05-18 16:44:05 -07:00
setup.py route53: update setup.py to follow repo conventions (#4731) 2017-05-26 14:44:05 -07:00

Route53 plugin for Let's Encrypt client

Before you start

It's expected that the root hosted zone for the domain in question already exists in your account.

Setup

  1. Create a virtual environment

  2. Update its pip and setuptools (VENV/bin/pip install -U setuptools pip) to avoid problems with cryptography's dependency on setuptools>=11.3.

  3. Make sure you have libssl-dev and libffi (or your regional equivalents) installed. You might have to set compiler flags to pick things up (I have to use CPPFLAGS=-I/usr/local/opt/openssl/include LDFLAGS=-L/usr/local/opt/openssl/lib on my macOS to pick up brew's openssl, for example).

  4. Install this package.

How to use it

Make sure you have access to AWS's Route53 service, either through IAM roles or via .aws/credentials. Check out sample-aws-policy.json for the necessary permissions.

To generate a certificate:

certbot certonly \
  -n --agree-tos --email DEVOPS@COMPANY.COM \
  -a certbot-route53:auth \
  -d MY.DOMAIN.NAME