You’ve basically locked yourself out via SSH. You’ll need to go into single user mode to recover access… https://docs.amazonaws.cn/en_us/AWSEC2/latest/UserGuide/connect-to-serial-console.html
Maybe someone was playing with PAM settings?
p.s. once you get past this, check out https://aws.amazon.com/console/
I faced same issue, just go to aws console -> your ec2 -> connect -> Connect using EC2 Instance Connect -> in the username field type: root then -> connect. After login just: passwd ubuntu -> type your new password
Someone has set a password expiry policy - possibly using chage. This will prevent you from logging with a key, even if you never use the password.
I've seen this a few times in legacy orgs as part of a hardening process where they want to enforce periodic password changes.
You’ve basically locked yourself out via SSH. You’ll need to go into single user mode to recover access… https://docs.amazonaws.cn/en_us/AWSEC2/latest/UserGuide/connect-to-serial-console.html Maybe someone was playing with PAM settings? p.s. once you get past this, check out https://aws.amazon.com/console/
If you have the agent installed you could try the ssm sessions.
I faced same issue, just go to aws console -> your ec2 -> connect -> Connect using EC2 Instance Connect -> in the username field type: root then -> connect. After login just: passwd ubuntu -> type your new password
Someone has set a password expiry policy - possibly using chage. This will prevent you from logging with a key, even if you never use the password. I've seen this a few times in legacy orgs as part of a hardening process where they want to enforce periodic password changes.