markuman123

on 3.21 with the previous version ...

1. ufw limit ssh.

2. Ansible devsec.hardening.ssh_hardening

3. fail2ban

      totp() {
        TOKEN=$(keyring get totp $1)
        oathtool -b --totp $TOKEN | xclip
      }

    - name: set TOTP in keyring
      with_items: "{{ TOTP }}"
      community.general.keyring:
        service: totp
        username: "{{ item }}"
        password: "{{ TOTP[item] }}"
        keyring_password: "{{ keyring_password }}"

To be clear, I'm no aws advocate.

14kb in your bucket and you pay for outgoing traffic. means, while you're sleeping, I can ruin your aws bill.

In any case, committing credentials is always wrong and you cannot justify it.

Depending on your ci tool (e.g. gitlab-runner, drone-ci ... ) there are other and better ways to provide credentials for a git project in CI/CD pipeline.

Postgres and MySQL (MariaDB/Percona) are both big players with a huge community.

Maybe consider to use Mariadb or Percona instead of MySQL to avoid oracle vendor lock in.