upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-04-09 19:18:08 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
Certificats Let's Encrypt
12 commits 858 branches 155 tags 126 MiB
Python 94.5%
Shell 3.7%
Batchfile 0.8%
Makefile 0.7%
Augeas 0.2%
Find a file
Chow Loong Jin e9531dc80b Replace xrange with range
2017-03-01 01:43:11 +08:00
certbot_route53 Replace xrange with range 2017-03-01 01:43:11 +08: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 Make it work as certbot-route53 2016-10-04 14:24:09 +01: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

  1. Create a virtual environment

  2. 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.

  3. 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