1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
It may be faster to create a new EC2 from a backup using an EC2 snapshot, etc., than to wait for it to stop.
If you wait, it will probably stop someday, but it may take some time, so you may want to consider restoring from a snapshot as a candidate.
https://docs.aws.amazon.com/prescriptive-guidance/latest/backup-recovery/restore.html#instance-from-snapshot
You may be able to forcefully stop it using the following command.
Try running the command from CloudShell.
https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html#how-to-get-started
aws ec2 stop-instances --instance-ids "instance-id" --force
Relevant content
- asked 3 years ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 15 days ago
- AWS OFFICIALUpdated 2 years ago
Yes, that is one option I am exploring. I think however, I will move to move the EBS data into EFS and setup a ASG. I don't think we can use the cloudshell command to force stop it, as it is in a shutting-down state. This is what is stated in the instance availability notice.