If you leave password enabled you need to harden the env as you be getting git by every script kiddy the second your public IP is ready.
You shouldn't be logging into these systems manually either - you should be provisioning them with the OS's default config tools like Ubiquiti or Cloud-init, storing the configs and creds in encrypted formats and the feeding them to chef/puppet/Ansible or any other configuration management tool.
Humans shouldn't be fucking with production systems, they should be making commits to git that are applied by automated systems.
Perhaps rethink how you view and solve the problem?
Include /etc/ssh/sshd_config.d/.conf
UsePAM yes
PrintMotd no
AcceptEnv LANG LC_
PermitRootLogin prohibit-password
PasswordAuthentication no
PermitEmptyPasswords no
ChallengeResponseAuthentication no
KerberosAuthentication no
GSSAPIAuthentication no
X11Forwarding no
PermitUserEnvironment no
Content here is mainly supposed to fill intellectual curiosity. Support like questions do not align with that.
I used Stack Overflow for their family of sites, of course you need to select the right one (unfortunately, wish they had just one)
This most recent comment of yours is definitely not HN appropriate. We try to maintain a higher level of discourse and respect for others here.
My original comment is a parrot of the mods replies to these types of questions.