It appears there must be a scheduled job on servers to remove the frappe user authorized_keys in favour of using the root user for all management via ssh and ansible.
This is not a great security policy in general and is dangerous if people are unaware and install their keys under the frappe user for emergency purposes.
You could install your own user on each server, but in a large deployment this is not feasible.
I also suggest you deploy UFW on every server to match the AWS security group, with a ufw limit ... rule for rate limiting ssh and for defence in depth.
ufw limit OpenSSH
ufw allow “Nginx Full”
ufw allow from 10.1.0.0/16 comment "internal vpc"
ufw allow from 172.17.0.0/16 comment "internal docker"
It appears there must be a scheduled job on servers to remove the frappe user
authorized_keysin favour of using the root user for all management via ssh and ansible.This is not a great security policy in general and is dangerous if people are unaware and install their keys under the frappe user for emergency purposes.
You could install your own user on each server, but in a large deployment this is not feasible.
I also suggest you deploy UFW on every server to match the AWS security group, with a
ufw limit ...rule for rate limiting ssh and for defence in depth.