Sign inSign up

wildscamp/certbot-route53

By wildscamp

•Updated about 6 years ago

A container to simplify generation of LetsEncrypt certificates against Amazon Route53 DNS.

Image
0

1.6K

wildscamp/certbot-route53 repository overview

⁠Let's Encrypt Amazon Route53 Certbot

Docker Logo The Wilds Logo

This container is designed to be used for local development. As such, it has not been hardened as required for a production environment.

The purpose of this container is to manage local development certificate creation and renewal for Let's Encrypt certificates against Amazon Route53.

⁠Environment variables

This image uses environment variables to for providing the necessary values to the container.

⁠AWS_ACCESS_KEY_ID

⁠AWS_SECRET_ACCESS_KEY

⁠SELF_SIGNED_SUBJECT
  • Description: If no AWS_ACCESS_KEY_ID is provided, certbot will be unable to authenticate to Amazon Route53. In that case a self-signed certificates will be created instead under /etc/pki/tls. This is the subject of the self-signed certificate.
  • Example: /C=US/ST=NY/L=New York/O=Example Company/CN=localdev.example.com

⁠BASE_DOMAIN
  • Description: This is the main domain part of the certificate that certbot will generate. It will request a cert for BASE_DOMAIN as well as a wildcard for the base domain.
  • Example: localdev.example.com. This generates certificates for localdev.example.com and *.localdev.example.com.

⁠ADDL_DOMAIN_PREFIX
  • Description: If provided, this would request an additional wildcard certificate with this prefixed to the BASE_DOMAIN.
  • Example: jdoe. If BASE_DOMAIN was localdev.example.com, then an additional certificate for *.jdoe.localdev.example.com would be requested.

⁠Volumes

The following volumes are used by certbot:

  • /etc/letsencrypt - The certbot data folder. Certbot will automatically generate new certificates if this folder is empty.
  • /etc/pki/tls - Let's Encrypt certificates are linked here.
    • /etc/pki/tls/cert/cert.pem - Corresponds to Let's Encrypt's fullchain.pem file.
    • /etc/pki/tls/private/privkey.pem - Corresponds to Let's Encrypt's privkey.pem file.

⁠Examples

⁠Docker Run
docker run -it --rm -e AWS_ACCESS_KEY_ID=AAAAAAAAAAAAAAAA \
    -e AWS_SECRET_ACCESS_KEY=BBBBBBBBBBBBBBBB \
    -e BASE_DOMAIN=localdev.example.com -e ADDL_DOMAIN_PREFIX=jdoe \
    -v $HOME/Dev/.letsencrypt-data:/etc/letsencrypt \
    -v $HOME/Dev/project/certificates:/etc/pki/tls \
    wildscamp/certbot-route53
⁠Docker Compose
letsencrypt:
  image: wildscamp/certbot-route53
  environment:
    - AWS_ACCESS_KEY_ID=AAAAAAAAAAAAAAAA
    - AWS_SECRET_ACCESS_KEY=BBBBBBBBBBBBBBBB
    - BASE_DOMAIN=localdev.example.com
    - ADDL_DOMAIN_PREFIX=jdoe
  volumes:
    - ../.letsencrypt-data:/etc/letsencrypt
    - ./certificates:/etc/pki/tls

Tag summary

Content type

Image

Digest

Size

53.2 MB

Last updated

about 6 years ago

docker pull wildscamp/certbot-route53