- Newest
- Most votes
- Most comments
Note: Answering this question assuming your security group has port 22 inbound traffic allowed from your source IP.
Do you have SSM agent installed/enabled on your instance? If yes try connecting using it. Below is the guide if you need help connecting via SSM. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/session-manager.html
Also if you think you lost the key you can try couple of methods to get into system. I found a nice re:Post article explaining the same which should be able to get you in to your system via SSH. Try this: https://repost.aws/knowledge-center/user-data-replace-key-pair-ec2
Thanks for the reply. SSM isn't installed. Port 22 is open to my IP and as I mentioned before I can't ping the IP so it's probably disconnected from any network. I've been logging in with my key pretty frequently so I know where that is and what it is.
My main problem is that I set this up so long ago with the absolute minimum knowledge of how it works and I think I've just been lucky.
Like do I just make another instance and point it to the filestore and point the elastic ip to the instance?
I mean not everything looks normal, something went screwy with my CPU today when this all went sideways
https://kunamakst.s3.us-west-2.amazonaws.com/wp-content/uploads/ScreenRegion_230407_185623.png
Could it be that the boot volume has run out of space? That can cause all kinds of havoc. If so, you could detach the root volume and attach to a working instance and expand the volume and file system. Then reattach the expanded volume to the broken instance.
Also, if you are over your head on this you may want to consider using AWS IQ to get some help.
Also, take a snapshot of the instance's volume(s) so you can go back to a known state.
Open up an Account and billing case with AWS support and make sure your account was not isolated in some way.
Unlikely to be full, I expanded it to many GB beyond what I was using. I created another instance that I cannot access either so expanding anything still won’t work if I can’t connect to anything
Relevant content
- asked 3 years ago
- asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
Created a new instance and still no connectivity, is it something with my account/billing? I've been down for many hours now, this is the first time I've had any sort of outage in 7 years other than reboot time.