certbot-certbot

mirror of https://github.com/certbot/certbot.git synced 2026-07-27 08:09:10 +02:00

T

Jacob Hoffman-Andrews d67de61ad8 Move sleep(TTL) into perform.

This means we only do it once, even when there are many hostnames.

2017-03-15 11:38:26 -07:00

certbot_route53

Move sleep(TTL) into perform.

2017-03-15 11:38:26 -07:00

.gitignore

Initial commit

2016-01-31 18:35:35 -08:00

LICENSE

Initial commit

2016-01-31 18:35:35 -08:00

LICENSE.txt

Initial commit, not safe to use

2016-01-31 22:33:17 -08:00

MANIFEST.in

Make it work as certbot-route53

2016-10-04 14:24:09 +01:00

README.md

Make it work as certbot-route53

2016-10-04 14:24:09 +01:00

sample-aws-policy.json

Make it work as certbot-route53

2016-10-04 14:24:09 +01:00

setup.cfg

Initial commit, not safe to use

2016-01-31 22:33:17 -08:00

setup.py

add support for root domain

2016-11-04 20:26:34 -05:00

README.md

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

Create a virtual environment
Make sure you have libssl-dev (or your regional equivalent) installed. pycparser suffers from https://github.com/eliben/pycparser/issues/148, which is why we need to recompile it, which depends on libssl-dev.
Install by adding these to your requirements.txt file:

--no-binary pycparser
-e git+https://github.com/certbot/certbot.git#egg=certbot
-e git+https://github.com/certbot/certbot.git#egg=acme&subdirectory=acme
certbot-route53

We need DNS01 support in certbot, which is only available in master for now.

How to use it

Make sure you have access to AWS's Route53 service, either through IAM roles or via .aws/credentials.

To generate a certificate:

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