Why is there no standards for deleting

You raise a valid point about the inconsistency in deletion confirmation processes across AWS services. While AWS does strive for standardization in many areas, the deletion confirmation methods can indeed vary between different services and resources.

The reason for these variations is often related to the criticality and potential impact of the deletion action. For some resources, like EC2 instances, the deletion (termination) process is designed to be quick and straightforward, with options like termination protection available for added safety. In contrast, other resources might require more stringent confirmation steps due to the potential for data loss or service disruption.

AWS does offer some standardized safety measures, such as enabling termination protection for EC2 instances or using deletion protection for certain database services. However, the specific implementation of deletion confirmations can differ based on the service team's assessment of risk and user needs.

That being said, your frustration with the inconsistent user experience is understandable. A more standardized approach to deletion confirmations could indeed improve user experience and efficiency. While AWS does continually work on improving and standardizing their interfaces, this particular area seems to have room for improvement.

If you have strong feelings about this, you can provide feedback to AWS through the feedback button in the AWS Management Console. AWS takes user feedback seriously and uses it to inform future improvements to their services and interfaces.

In the meantime, for services you frequently use, familiarizing yourself with their specific deletion processes and utilizing available protection features can help streamline your workflow while maintaining necessary safeguards against accidental deletions.
Sources
Why EC2 Termination Doesn't Have Double Confirmation that to with Default 'Delete on Termination' Flag setted true? | AWS re:Post
shared responsibility model understanding confirmation | AWS re:Post