They seem to be headed towards being an "AWS light". Would be nice to be have an alternative with reasonable egress costs. Still a long way to go though. At a minimum, they would need a more configurable load balancer and some S3 type function.
I've recently done a moderately complex hybrid setup that used DO in conjunction with S3 and Route53. My biggest takeaway from the experience was how much the simplicity and speed of DO's dashboard interface stood out - the AWS web interface just felt laggy by comparison. I know it sounds like a poor reason to favour a platform but DO was just a simple pleasure to navigate and use.
Cloud Firewalls
21–30 of 119 posts
Re: Cloud Firewalls
#22It's not clear what this offers over the usual iptables/firewalld + ansible solution. What am I missing?
The traffic is blocked/allowed at our network layer before being routed to the droplet. The rules are easily configurable through the control panel and API. You can also specify Droplets (individual or tagged) and our recently new Load Balancers as the targets.
You can also layer multiple firewalls on top of one another if you want to apply specific firewall rules to only a specific set of Droplets/LBs
The Intro tutorial we have is great for details: https://www.digitalocean.com/community/tutorials/an-introduc...
Feel free to reach out to us if you have any more specific questions. :)
Re: Cloud Firewalls
#23DigitalOcean is killing it against Linode - I just migrated my last services off Linode because you still cannot attach arbitrary sized disks to your instances, something they've been promising as arriving "soon" for months. Go DO!
Re: Cloud Firewalls
#24It's not clear what this offers over the usual iptables/firewalld + ansible solution. What am I missing?
Deny outbound access except through specific hosts (config management, internal package mirrors) so that even an attacker with root can't phone home.
The same reasons anyone uses firewall devices vs. host-based firewalls.
Re: Cloud Firewalls
#25It's not clear what this offers over the usual iptables/firewalld + ansible solution. What am I missing?
Re: Cloud Firewalls
#26Once they double the RAM on all plans like Linode and Vultr did, I will move all of my servers back to DigitalOcean. I love these features but double the RAM for the same price still outweighs them.
Do you consider this when you're talking about value? I know little about vultr.
5 vs 10 vs 20 vs 40 dollars doesn't mean much, and Linode pricing starts to converge on DO's after the $80 price point.
Re: Cloud Firewalls
#27Once they double the RAM on all plans like Linode and Vultr did, I will move all of my servers back to DigitalOcean. I love these features but double the RAM for the same price still outweighs them.
This is exactly why my next server will be on Vultr, too, although I still curse Linode for still not having block storage and forcing me to pay double price for a larger server even though I just need 20 more GB of disk space.
Re: Cloud Firewalls
#28They seem to be headed towards being an "AWS light". Would be nice to be have an alternative with reasonable egress costs. Still a long way to go though. At a minimum, they would need a more configurable load balancer and some S3 type function.
I would be extremely happy with DO if they put out an S3 competitor. Right now, most of my servers are on DO, the only things I need AWS for is a single windows server to run some windows only software, and S3 to store my database backups.
Re: Cloud Firewalls
#29DigitalOcean is killing it against Linode - I just migrated my last services off Linode because you still cannot attach arbitrary sized disks to your instances, something they've been promising as arriving "soon" for months. Go DO!