Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
When destroy a droplet, system should ask to enter password to confirm before delete it for more safety. Since this is the most important decision.
huh, very slowly :D
It's a great idea, some weeks ago I destroyed a droplet accidetally, I was so stresed and confirm the destroy operation and I had a backup but I never could get the IP that the server has so I have to revalidate it on my client network.
This is a "must have"
This is really important I'm really confused as to why is it too easy to delete production droplets, it's crazy.
We can fix this by displaying the droplet name in the modal during confirmation.
It would also be good to require an additional step to delete a server though the API.
I would love a multi-step process or secondary password option for deleting a server. If someone gains access to your admin login it would be so simple for them to wipe out your active servers and backup images.
Agreed! I have never liked simple "are you sure you want to do this" questions. I have been conditioned over years to just automatically click that OK button. Asking for a password better communicates the seriousness of destroying a droplet along with all its data.
Would be a great option!
Please make it
I second this
Yes that would be a nice security feature...
Seems like a sensible thing to do, especially since (as I understand) backups will be deleted as well when deleting a droplet, so if you did *not* manually create a snapshot, there's no way to restore your server/droplet
I think it is an urgent feature !!!!
Another similar option that I like would be having something similar to EC2 "termination protection". Just a attribute you can enable so the interface just doesn't allow you to destroy the server unless you disable that option again.
I completely agree with Luis: we need a feature like EC2's "termination protection" that can be enabled per machine.
Or maybe approach this like Github does when deleting a repo: confirm deletion by typing the repo name (in this case it would be the Droplet name).
@Mathieu Martin: I agree! Something similar to GitHub would be nice, but now using the password. That might not be a good idea, especially for those having strong passwords.
We NEED this feature for security reasons.
Please. I just accidentally deleted a server on a business Digital Ocean account, and if Digital Ocean didn't keep backups on Droplet Destruction, I would've had to use a two week old backup.
This is a must to add extra step when someone is trying to destroy a droplet. Please consider to add 2FA verification (if enabled) beside password confirmation.
You won't be notified about changes to this idea.