Why was the entire data deleted from the server?

Hello,

Data loss likely due to accidental termination (meant to stop, but terminated). Here's how to prevent it:

1. Back up regularly to S3 or another server.

2. Enable confirmation prompts before terminating instances.

3. Understand stopping vs. terminating: Stopping keeps data, terminating deletes it.

4. Monitor server health to prevent overload.

Here's a comprehensive link that covers all the points to prevent data loss:

AWS Well-Architected Framework - Fault Tolerance and Recovery: https://docs.aws.amazon.com/awssupport/latest/user/fault-tolerance-checks.html

Hello.

From what I see in the image, it looks like there is a problem with the network you are using.
Please try connecting from a different network, PC, or browser.
Also, please try to see if you can access it from the URL below.
https://console.aws.amazon.com/console/home?nc2=h_ct&src=header-signin

We had the Terminate instance option disabled when stopped, but I don’t know why, after some time, the instance got Terminated instead stopping.

By the way, if you stop and start, EC2 will not be automatically terminated.
I suspect that you may have pressed the Terminate button by mistake.

I’m very curious how we can prevent such data losses, since we lost a lot of time on project recovery.

I recommend backing up your EC2 to prepare for such unexpected situations.
You can easily set up backups using AWS Backup.
https://docs.aws.amazon.com/aws-backup/latest/devguide/whatisbackup.html

Hi Possible Causes of Data Loss: =>Instance Termination vs. Stop: If an instance is terminated instead of stopped, all data on the instance store volumes (not EBS volumes) is lost. Even if EBS volumes are attached, they can be deleted if not configured to persist after termination.

=>Instance Overload and Restart Issues: Server overload can cause instances to become unresponsive. Restarting or stopping and starting instances is a common troubleshooting step, but it must be handled carefully to avoid data loss.

=>Misconfiguration: There might have been a configuration issue that led to the termination of the instance instead of stopping it.

Review Logs: Check CloudTrail logs to understand what actions were taken before the instance was terminated.