I am following this guide on how to Configure SSL/TLS on Amazon Linux 2023. It recommends to obtain a CA-signed certificate using Certbot. And to get Certbot, it's recommended to install Snap.

I have tried several things, not able to install any of prerequisites:

sudo yum install snapd
    Error: Unable to find a match: snapd

sudo amazon-linux-extras install epel
    sudo: amazon-linux-extras: command not found

sudo yum install -y amazon-linux-extras
    Error: Unable to find a match: amazon-linux-extras
  • 1
    Guides that recommend yum are inherently a bit dated: yum is the predecessor of dnf, and Amazon Linux 2023 uses dnf, and only has a yum compatibility layer. The guides that you've been reading might have been bad, or outdated. (Many many bad guides on the internet, sorry.) May 1, 2023 at 16:18

1 Answer 1


There's honestly no good reason to run certbot, which is really just enough code to interact with letsencrpyt and modify a few configuration files, in a snap. Especially if you want it to actually do its job of modifying the system, snap's isolation capabilities aren't useful.

Amazon doesn't recommend using snap to install certbot; that's just this site https://eff-certbot.readthedocs.io/en/stable/install.html#installation which lists it as one of many ways.

You'll be fine just installing the most recent certbot using the pip-method described on the same page. It's a lot less overhead than using snap (really not happy about them recommending that; also, I think their pip-based description has minor bugs). For a quick overview of how that'd work:


# create an isolated python environment for certbot purposes alone
python3 -m venv /opt/certbot

# Modify environment for the current shell only to make python modify
# the virtual environment and not your system libraries
source /opt/certbot/bin/activate

# Install certbot
pip install certbot

That's it. If you later want to run certbot as standalone program,

/bin/bash -c "source /opt/cerbot/bin/activate; certbot" 

does that.

You can of course also put that into a shell script, e.g.


source /opt/certbot/bin/activate
/opt/certbot/bin/certbot "$@"

make that executable (chmod 755 /usr/bin/certbot) and henceforth simply use certbot as command.

You might also want to set up a systemd timer to automatically renew your certificates regularly.

That's pretty easy:

  1. Make a file /lib/systemd/system/certbot.service with this content

ExecStart=/bin/bash -c "source /opt/cerbot/bin/activate; certbot -q renew" 

and one file /lib/systemd/system/certbot.timer with this:

Description=Run certbot twice daily

OnCalendar=*-*-* 00,12:00:00


Source code of this timer straight from the Fedora packaging

To activate that timer, systemctl enable --now certbot.timer. From there on, your certificates get renewed if necessary automatically.

You might also want to drop an email to AWS support and ask them why they recommend to use some software named "certbot" that every other larger Linux distro just includes (so that you could install via yum install certbot and get all the above done for you), but decide not to include certbot in Amazon Linux 2023 themselves. That seems like a pretty stupid oversight.

  • 1
    bit of a typo. "opt/cerbot" should be "opt/certbot" in ExecStart=/bin/bash -c "source /opt/cerbot/bin/activate; certbot -q renew" Jul 26, 2023 at 22:35
  • 1
    @VictorPowell sorry, it's a bit late around these parts of the planet, I'm kinda blind and don't see it! Could you simply go ahead and edit my answer, so I can just accept the edit in the morning? Jul 26, 2023 at 23:10
  • 1
    I tried but got an error about too many edits in the edit queue the first time and the second time I got an error that my edit was not long enough :/ Jul 27, 2023 at 3:07

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .