letsencrypt/hashicorp-lessons

Certbot is part of EFF’s effort to encrypt the entire Internet. Secure communication over the Web relies on HTTPS, which requires the use of a digital certificate that lets browsers verify the identity of web servers (e.g., is that really google.com?). Web servers obtain their certificates from trusted third parties called certificate authorities (CAs). Certbot is an easy-to-use client that fetches a certificate from Let’s Encrypt—an open certificate authority launched by the EFF, Mozilla, and others—and deploys it to a web server.

Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate is. Certbot and Let’s Encrypt can automate away the pain and let you turn on and manage HTTPS with simple commands. Using Certbot and Let's Encrypt is free.

Getting Started

The best way to get started is to use our interactive guide. It generates instructions based on your configuration settings. In most cases, you’ll need root or administrator access to your web server to run Certbot.

Certbot is meant to be run directly on your web server on the command line, not on your personal computer. If you’re using a hosted service and don’t have direct access to your web server, you might not be able to use Certbot. Check with your hosting provider for documentation about uploading certificates or using certificates issued by Let’s Encrypt.

Contributing

If you'd like to contribute to this project please read Developer Guide.

This project is governed by EFF's Public Projects Code of Conduct.

Links

Documentation: https://certbot.eff.org/docs

Software project: https://github.com/certbot/certbot

Changelog: https://github.com/certbot/certbot/blob/master/certbot/CHANGELOG.md

For Contributors: https://certbot.eff.org/docs/contributing.html

For Users: https://certbot.eff.org/docs/using.html

Main Website: https://certbot.eff.org

Let's Encrypt Website: https://letsencrypt.org

Community: https://community.letsencrypt.org

ACME spec: RFC 8555

ACME working area in github (archived): https://github.com/ietf-wg-acme/acme

Current Features

• Supports multiple web servers:
  • Apache 2.4+
  • nginx/0.8.48+
  • webroot (adds files to webroot directories in order to prove control of domains and obtain certificates)
  • standalone (runs its own simple webserver to prove you control a domain)
  • other server software via third party plugins
• The private key is generated locally on your system.
• Can talk to the Let's Encrypt CA or optionally to other ACME compliant services.
• Can get domain-validated (DV) certificates.
• Can revoke certificates.
• Supports ECDSA (default) and RSA certificate private keys.
• Can optionally install a http -> https redirect, so your site effectively runs https only.
• Fully automated.
• Configuration changes are logged and can be reverted.

hashicorp-lessons's Issues

Commands issued during lesson 2/2.5

Storing these here until we figure out where they should really go (if anywhere)

$ ../nomad job status
ID           Type     Priority  Status   Submit Date
hello-world  service  50        running  2021-12-14T17:24:08-05:00

$ ../nomad job allocs hello-world
ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
bc001e20  1bd5b87c  web         3        run      running   6m54s ago   6m43s ago
2fa30681  1bd5b87c  web         2        run      failed    7m30s ago   6m54s ago
bee8a517  1bd5b87c  web         2        stop     failed    9m5s ago    7m30s ago
e456f68a  1bd5b87c  web         2        stop     failed    10m8s ago   9m5s ago
56c06768  1bd5b87c  web         0        stop     complete  41m21s ago  34m13s ago

$ ../nomad alloc logs -stderr -tail -f bc001e20
< 2021/12/14 17:31:21.749149  length=59 from=0 to=58
HTTP/1.0 200\r
Content-Type: text/plain\r
\r
Hello, samantha\r

$ curl localhost:23232
Hello, samantha

$ ../consul kv export
[]

$ ../consul kv put hello-world/config to:'PHIL!!!'
Success! Data written to: hello-world/config

# This is invalid YAML and will cause a failed deployment. I had to stop the deployment and revert to a previously successful deployment to get it functional again.
$ ../consul kv get hello-world/config
to:PHIL!!!

# I needed to update my value to make it valid yaml because computers
$ ../consul kv put hello-world/config 'to: PHIL!!!'
Success! Data written to: hello-world/config

$ ../nomad job allocs hello-world
ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
ec776540  1bd5b87c  web         9        run      running   2m56s ago   2m38s ago
92f4f5ef  1bd5b87c  web         8        stop     complete  3m5s ago    2m51s ago
3ab71232  1bd5b87c  web         5        stop     failed    8m5s ago    3m5s ago

# This is getting a service in kubernetes
$ ../nomad alloc status ec776540 | grep web-listen
*web-listen  yes      127.0.0.1:21381

$ curl localhost:21381
Hello, PHIL!!!