- Newest
- Most votes
- Most comments
This is what I get :
$ aws ec2 start-instances --instance-ids i-0b0da3b7135256146
{ "StartingInstances": [ { "InstanceId": "i-0b0da3b7135256146", "CurrentState": { "Code": 16, "Name": "running" }, "PreviousState": { "Code": 16, "Name": "running" } } ] }
Instance state is till "Stopped" and I still cannot access.
You should just be able to start the instance via the AWS Console or CLI, at which point, it should start again. If it fails to start via the Console, you may be able to see more useful diagnostic information by running the following command at the CLI:
aws ec2 start-instances --instance-ids <instance-id>
The cli return is telling the truth, the console - not so much. I had to get out and back into the console to see it running.
a related question : I see where people stop and start their ec2 somewhat regularly. Does this practice somehow help with "underlying" problems?
What about taking a snapshot from the EBS and start a new instance with this snapshot?
Relevant content
- asked 3 years ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago