Google Compute Engine also offers a load balancer. ELB works with AWS’s auto-scaling and supports IPv4 and IPv6 addresses, HTTP and TCP load balancing, and logging. Apart from load balancing incoming traffic, ELB also offers session stickiness, cross-zone load balancing, and SSL termination. This traffic distribution to backend instances happens using a weighted round robin algorithm. EC2 vs Google Compute Engine: Load BalancingĮlastic Load Balancer (ELB) allows you load balance incoming traffic among your backend instances in multiple availability zones (within a single region). Google’s Firewall is also a whitelist service. Similarly, Google Compute Engine firewalls regulate outgoing traffic from instances using iptables. Network ACLs, on the other hand, work at subnet level, and allow or deny specific IP addresses or networks. With Security Groups – working as whitelists – you control incoming and outgoing traffic at the instance level. EC2 vs Google Compute Engine: Security Groups, Network ACLs, and FirewallsĪs AWS instances are now provisioned within VPCs, Amazon provides the benefit of both Security Groups and Network ACLs. To maximize savings, GCE also offers inferred instances, i.e., it combines multiple, non-overlapping instances of the same instance type in the same zone into a single instance for billing. The sustained usage pricing model provides discounts if your instance is used for more than 25% of a month. GCE offers both on-demand and sustained usage pricing models. After 10 minutes, instances are charged in 1-minute increments, rounded up to the nearest minute. Google Compute Engine machine types are charged for a minimum of 10 minutes’ use. Spot instances – bid for instances using a supply and demand model.Reserved instance prices are determined by 4 factors : term (1 or 3 year), operating system, region, and payment options (no upfront, partial upfront, all upfront). Reserved instances – maximize savings by purchasing reserved instances that meet your long term business needs.On-demand – pay for compute capacity by the hour with no long term commitments.EC2 vs Google Compute Engine: PricingĪmazon EC2 offers three types of pricing models: Note: This is a high-level comparison table. Memory Optimized/ High Memory Instance Type

Just like AWS, Google Compute Engine also offers instances based on workload type.Ĭurrently, GCE instances are divided into 4 types:Ĭompute Optimized / High CPU Instance Type The use of previous generation instances is not recommended due to performance limitations.

In its current form, there is a total of 28 instances types. Instance types are divided into different “families” like m3 (balanced), c4 (compute optimized), and t2 (baseline level). EC2 vs Google Compute Engine: Compute CapacityĪWS Instance types are optimized for different types of workloads, like Compute, Storage, Memory, and GPU. However, according to this post from Gigaom, us-central1 translates to Oklahoma, and Europe-west1 is in Ireland. Google does not officially reveal the exact locations of these zones. Google Compute Engine is spread across 3 different regions: us-central1, Europe-west1, and asia-east1. EC2 vs Google Compute Engine: RegionsĪmazon EC2 is spread across 11 different regions: Northern Virginia, Oregon, Northern California, Ireland, Germany, Singapore, Tokyo, China, Sau Paulo, Sydney, and US GovCloud. In this post, we’ll discuss the main differences between Amazon’s EC2 and Google Compute Engine (GCE). Within that, in terms of services and features, AWS enjoys the top position, while Google Cloud Platform is slowly catching up. Arguably, Infrastructure as a Service (IaaS) is the most important cloud computing vertical.

Google cloud compute engine ftp server