- 최신
- 최다 투표
- 가장 많은 댓글
Also, I'm thinking that the issue should be addressed to AMI developers. I'm using AMI with CentOS 8.4 for aarch64, so devs should preconfigure swap for such cases.
In addition: https://www.mail-archive.com/centos-virt@centos.org/msg05892.html
So, if use Amazon Linux 2 it works as expected. I had the issue with CentOS 8, but according to Minimum RAM requirements 768 MiB is a minimum value, so, it looks like expected. Meanwhile, I have no issues with CentOS 8 on t4g.nano in Hong Kong region, but it takes a bit of time.
Have you considered starting a session via SSM instead. Requires the EC2 instance is running the SSM agent and relevant policy attached to the EC2 instance role. SSM essentially provides one-click access to ec2 instances without the need to open inbound ports or manage SSH keys.
Refer to
SSM is great but it's just a workaround because base functionality doesn't work.
To add to RoB's answer, you can also use Use EC2Rescue for Linux. refer to link {1}
With the help of SSM, The AWSSupport-TroubleshootSSH runbook installs EC2Rescue for Linux and then uses the tool to check or attempt to fix common issues that prevent a remote connection to a Linux machine via SSH. For more information, refer to link {2}
Please refer to the below link to know more:
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 2년 전
Do you have the same problem when you use the Amazon Linux 2 AMI?