5 reasons VPNs suck in the cloud
March 9, 2013
Grazed from CloudTech. Author: Dome9.
If you’ve been around the block a few times, you’re probably wondering why the title of this post isn’t, 50 Reasons VPNs Suck in the Cloud. VPNs have long been the bane of both administrators and users (and lets not forget, support). They’re clunky, complex, and costly, and the same is true when they’re deployed to secure cloud access. Today, VPNs are increasingly used to connect to cloud computing resources.
Either by routing traffic back through the corporate network or direct to the cloud provider, VPNs offer authentication and transport-layer encryption to keep the bad guys out and sensitive information secure. But at what cost? Both VPN configurations (corporate and provider) are complex to set up, require client agents with loads of support, and can be expensive to maintain. Arguably, there’s room for – and exists – a better approach to securing access to cloud servers. We’ll get to what that is in a coming post, but for now we thought we’d share a few reasons why VPNs suck in the cloud, in reverse order (for effect)…
5 Reasons why VPNs suck in the cloud
#5: Cloud VPNs don’t scale
Is your cloud spread across multiple regions? Get ready to spin up multiple VPN servers (for HA) in each. The larger, more distributed your cloud is, the more backend infrastructure, complexity, and cost you’ll have just to support VPN…
Read more from the source @ http://www.cloudcomputing-news.net/blog-hub/2013/feb/15/5-reasons-vpns-suck-in-the-cloud/