No delete credentials present a cost issue when moving from a provider... I've accidentally left data behind after I thought I'd deleted it. Worth the risk, and learned my lesson.

You can set a lifecycle rule. You don't need credentials to delete.

Only if you allow permissions to set a lifecycle rule...

You don't set the lifecycle rule at runtime. You set it at environment setup time. The credentials that put your object don't have to have the power to set lifecycle permissions.

You obviously don't put your environment setup user in your app. That would be utterly retarded.

Not useful for me at environment setup time because I never want any of my data deleted. The only time is if I decide to abandon that cloud provider.

And when you're moving providers you use your application credentials to do that? That makes no sense. This is nonsensical engineering. You'd use your environment credentials to alter the environment.

I'm not "engineering" anything - I'm just stopping a service. I close the account, or disable billing, or whatever that step requires. I don't even read the data back out or anything - just cancel. Doesn't really require "engineering".