- Newest
- Most votes
- Most comments
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:
Relevant content
- asked 5 months ago
- asked 6 months ago
- asked 10 months ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Do you have the same problem when you use the Amazon Linux 2 AMI?