Amazon VPC vs OVH: What are the differences?
Amazon VPC: Provision a logically isolated section of the AWS Cloud and launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can easily customize the network configuration for your Amazon VPC; OVH: Dedicated infrastructure for your business. Hundreds of new servers are installed in our 12 datacenters everyday. For our clients, this guarantees bare-metal resources accessible in less than an hour, and the liberty to use it to rollout the software of their choice. The many functions available on our dedicated servers allow our clients to manage their infrastructure autonomously.
Amazon VPC belongs to "Virtual Private Cloud" category of the tech stack, while OVH can be primarily classified under "Dedicated Cloud Hosting".
Some of the features offered by Amazon VPC are:
- Create an Amazon Virtual Private Cloud on AWS's scalable infrastructure, and specify its private IP address range from any range you choose.
- Divide your VPC’s private IP address range into one or more public or private subnets to facilitate running applications and services in your VPC.
- Control inbound and outbound access to and from individual subnets using network access control lists.
On the other hand, OVH provides the following key features:
- Delivery of servers in less than an hour 24/7/365
- Full user control
- Guaranteed bandwidth
"Secure" is the top reason why over 39 developers like Amazon VPC, while over 51 developers mention "Cost effective" as the leading cause for choosing OVH.
Coursera, Intuit, and Expedia.com are some of the popular companies that use Amazon VPC, whereas OVH is used by Webedia, Welovebuzz, and Critizr. Amazon VPC has a broader approval, being mentioned in 298 company stacks & 76 developers stacks; compared to OVH, which is listed in 66 company stacks and 24 developer stacks.
What is Amazon VPC?
What is OVH?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon VPC?
What are the cons of using OVH?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use Hetzner Online AG since the inception of our business, because of the great prices, marvelous support and great interface (especially the new cloud interface). Other options that we tested are DigitalOcean (was more expensive than the new hetzner cloud and didn't offer "huge" dedicated servers), @Vultr (about the same issue as with DigitalOcean , although the prices were better), OVH (Prices, old interface, no "tiny" packages and [at least back at the day] only monthly payment) and Living Bots (Only dedicated servers, too expensive for our needs).
Hetzner offered the best spectrum of servers and has great prices and REALLY great prices in the server auctions.
VPC launched in mid 2009 as a companion product to the existing EC2 offering, though it quickly became considered to be EC2 2.0, as it remedied many of the commonly accepted EC2 downfalls. At face value, the migration didn’t seem conceptually difficult, as VPC was just another software abstraction on top of the same hardware, yet it was much more complex, with a few main issues:
- You cannot migrate a running instance.
- AWS offers no migration plan.
- EC2 and VPC do not share security groups.
This last point lingered in our heads as we tried to come up with a solution. What would it take to make EC2 and VPC talk to each other as if the security groups could negotiate? It seemed insurmountable: we had thousands of running instances in EC2 and we could not take any downtime. We were looking for a solution that would allow us to migrate at our own pace, moving partial and full tiers as needed, with secure communication between both sides.
So, we created Neti, a dynamic iptables-based firewall manipulation daemon, written in Python, and backed by Zookeeper.
We use OVH to host the majority of our servers spread across the globe. This allows us to have a single point of contact for our main hosting when issues arise as well as giving us the ability to quickly failover servers when needed. OVH also helps us by keeping the price we pay for servers down therefore keeping the fees on our products themselves down.
Our architecture is running in Amazon VPC. That's actually what we started with and we're still very happy with. We’re pretty much tied into the entire platform.
The majority of our dedicated servers are hosted with OVH, due to their competitive pricing, easy to use control panels and quick on-site support options.
The DB and some servers on a separate sub-net in the VPC. This ensures access to these servers are denied from any other machine than the VPC.
With VCP, you can secure and segment your nodes.
It is easy to manage, flexible, and gives great control over your virtual infrastructure.
Build & Deployment tools; Development, Sandbox and Business Continuity environments; ad hoc processing workers