- 최신
- 최다 투표
- 가장 많은 댓글
This sounds like it could be a cipher mis-match, how old is the key that you're using to connect, and/or how old is the SSH client that you're using (e.g. PuTTY)?
Simplifying things a lot, some encryption algorithms that used to be considered to be secure, are now no longer thought of in that way, and are deprecated in the newest releases of the various flavours of Linux.
Are you able to update the SSH client and/or generate a new key that uses a more secure cipher, and see if that works, though I appreciate this means having to spin up a fresh Alma Linux 9 EC2? (actually, you can update the SSH key in-place using User Data but as a solution to your problem it's probably more trouble than it's worth https://repost.aws/knowledge-center/user-data-replace-key-pair-ec2 )
Embarrassingly enough, it was the ssh client that I was using. I used a newer client and I was able to connect. What really threw me off was when I tried to connect in the AWS UI on the instance page via the "connect" button, and it also failed. Maybe that UI was just not supported with that OS. Thanks.
This is likely because EC2 Instance Connect isn't supported on Alma Linux https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-prerequisites.html#eic-prereqs-amis
(although maybe the RHEL or CentOS package might work)