amazon linux 2 ec2 -use unable to connect highly urgently solution required
till about 4 hours ago i was able to connect properly to this instance then it just abrubtly stopped connecting. i have ssh port 22 opened in instance. time zone is same as that of server , sweden and no changes in key pair or ip adress . pls help urgently
- Newest
- Most votes
- Most comments
Have you tried connecting using AWS Systems Manager Session Manager? https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-prerequisites.html
In the EC2 section of AWS Console is the instance state Running, and its status is 2/2 checks passed ? https://eu-north-1.console.aws.amazon.com/ec2/home?region=eu-north-1#Instances:
If you select the instance and go to the Monitoring tab is there anything of concern in the metrics shown for resource consumption?
What's the instance type and what workload is running on it?
It may be necessary to restart the instance, and if it comes back okay after that then it would be helpful to setup CloudWatch agent to collect more detailed system logs https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html If the incident recurs then this will give you more information to find the root cause.
Relevant content
- asked 7 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 months ago
ANSWER 2 ) YES Instance is running and 2/2 checks passed answer 3)no all metrics appear to be low and fine . i am unable to provide a scrrenshot as comments dont support images answer 4) t3. micro free instance and i was trying to runa hadoop map reduce job on 10,000 documents on it
I'm wondering if a t3.micro has got enough resources to run this? 2 cores and 1GB of memory isn't a lot. It would definitely be worthwhile installing CloudWatch Agent on the instance so you can get a much better view of resource usage.
An instance type with more resources might give you a better outcome, but if you want to stay within Free Tier on a t3.micro then consider adding some additional swap space https://repost.aws/knowledge-center/ec2-memory-swap-file