Amazon Web Services
Because most of Amazon's web services are deployed on Amazon Elastic Compute Cloud (EC2) instances, Amazon's networking services are heavily tied to Amazon EC2. Amazon Web Services (AWS) has two different networking stacks, both of which center on Amazon EC2:
Elastic Compute Cloud-Classic (EC2-Classic), their original offering.
Amazon Virtual Private Cloud (VPC), their current offering.
Amazon EC2-Classic launches all instance types into a public, shared network, where each instance has access to the Internet and is assigned a public IP address. This offering has been deprecated since late 2013, and can only be used by accounts created before that date.
Amazon VPC is a newer model, with support for a wider array of networking features. For example, Amazon VPC offers the following upgrades:
Support for creating private RFC 1918 address spaces and subnetting
Network access control lists (NACLs)
Inbound and outbound firewall rules
Routing
VPN
Google Cloud Platform
In contrast, Google Cloud Platform treats networking as a global feature that spans all services. Cloud Platform's networking is based on Google’s Andromeda architecture, which can create networking elements at any level with software. This software-defined networking allows Cloud Platform's services to implement networking features that fit their exact needs, such as secure firewalls for virtual machines in Google Compute Engine, fast connections between database nodes in Cloud Bigtable, or fast query results in BigQuery.
When you create virtual machine instances in a Cloud Platform project, Compute Engine automatically connects them to a default internal network. If needed, you can create additional networks as well. As with Amazon VPC, each network is private, and each supports firewall rules, routing, VPNs, private RFC 1918 address spaces, and subnetting.
Most of the networking entities in Cloud Platform, such as load balancers, firewall rules, and routing tables, have global scope. More importantly, networks themselves have a global scope. This means that you can create a single private IP space that is global, without having to connect multiple private networks and manage those spaces separately. Due to this single, global network, your Compute Engine instances can be addressed within your network by both IP address and name.
references:
https://cloud.google.com/docs/compare/aws/networking
Because most of Amazon's web services are deployed on Amazon Elastic Compute Cloud (EC2) instances, Amazon's networking services are heavily tied to Amazon EC2. Amazon Web Services (AWS) has two different networking stacks, both of which center on Amazon EC2:
Elastic Compute Cloud-Classic (EC2-Classic), their original offering.
Amazon Virtual Private Cloud (VPC), their current offering.
Amazon EC2-Classic launches all instance types into a public, shared network, where each instance has access to the Internet and is assigned a public IP address. This offering has been deprecated since late 2013, and can only be used by accounts created before that date.
Amazon VPC is a newer model, with support for a wider array of networking features. For example, Amazon VPC offers the following upgrades:
Support for creating private RFC 1918 address spaces and subnetting
Network access control lists (NACLs)
Inbound and outbound firewall rules
Routing
VPN
Google Cloud Platform
In contrast, Google Cloud Platform treats networking as a global feature that spans all services. Cloud Platform's networking is based on Google’s Andromeda architecture, which can create networking elements at any level with software. This software-defined networking allows Cloud Platform's services to implement networking features that fit their exact needs, such as secure firewalls for virtual machines in Google Compute Engine, fast connections between database nodes in Cloud Bigtable, or fast query results in BigQuery.
When you create virtual machine instances in a Cloud Platform project, Compute Engine automatically connects them to a default internal network. If needed, you can create additional networks as well. As with Amazon VPC, each network is private, and each supports firewall rules, routing, VPNs, private RFC 1918 address spaces, and subnetting.
Most of the networking entities in Cloud Platform, such as load balancers, firewall rules, and routing tables, have global scope. More importantly, networks themselves have a global scope. This means that you can create a single private IP space that is global, without having to connect multiple private networks and manage those spaces separately. Due to this single, global network, your Compute Engine instances can be addressed within your network by both IP address and name.
references:
https://cloud.google.com/docs/compare/aws/networking
No comments:
Post a Comment