2

I have an EC2 instance that I can't ssh into – the process takes extremely long, and if succeeded, I can't type any command in there. 3-4 hours ago this process was taking milliseconds.

What can I do in this scenario? I was trying to stop the instance manually, yet AWS tells me I can't do it as it is connected with Spot Request (and it's true).

It would be great if there is something that can be done that does not delete what's on the disk.

Improve this question
1
  • 2
    Create an AMI of the instance, terminate the spot instance, restart as on-demand for diagnosis. Or take a snapshot of the disk and mount it to an EC2 instance. Commented Nov 3, 2021 at 17:57

1 Answer 1

Reset to default
0

Looks to me like an out-of-memory problem. Use an instance with more RAM.

To preserve the disk content: As @Tim already said: create a snapshot of the old instance. Either attach it as an additional disk to the new instance or create an AMI from the snapshot and launch the new instance with that AMI.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.