Why EC2 Termination Doesn't Have Double Confirmation that to with Default 'Delete on Termination' Flag setted true?

Have you ever wondered why terminating an EC2 instance doesn't require double confirmation through email, unlike other critical actions such as enabling services for payments? And why is the default setting for the "Delete on Termination" flag set to true, risking accidental and irreversible data loss?

While options like auto backups and snapshots exist to safeguard data, not everyone may be aware of or have access to them. Even with these options, there's still a risk of permanently losing important data if termination is accidental or unintended.

Imagine this: you're about to terminate an instance without realizing that you haven't taken any snapshots or backups. A double confirmation email could alert you to this fact, giving you a chance to reconsider and take necessary precautions to avoid data loss.

In simple terms, shouldn't there be extra steps to prevent unintended terminations and ensure data safety? Yes, there are auto-backup and snapshot options available, but not everyone may know how to use them or have them set up.

Therefore, just think how a double confirmation email like "Hey, just a heads up, you haven't backed up your data and Delete on Termination is enabled, so if you go ahead, you might lose all data associated with this instance" could serve as a vital safety net, reminding users to protect their data before proceeding with termination.

Moreover, once an instance is terminated, there's often no immediate way to regain lost data, at least for a certain period. This underscores the importance of implementing effective safeguards to prevent accidental data loss.