Tuesday, 19 September 2017

Cloud Interconnect

Choosing a network connection option


Different applications and workloads require different network connectivity solutions. Google supports multiple ways to connect your infrastructure to Google Cloud Platform.






INTERCONNECTPEERING
Direct access to RFC1918 IPs in your VPC – with SLAAccess to Google public IPs only – without SLA
Includes:
  • Dedicated Interconnect

  • IPsec VPN

Includes:
  • Direct Peering

  • Carrier Peering

Interconnect Options


Dedicated Interconnect


If you would like to extend your data center network into their Google Cloud projects, Dedicated Interconnect offers enterprise-grade connections to GCP. This solution allows you to directly connect your on-premises network to your GCP VPC. You must meet Google at one of our peering locations.

Useful for hybrid environments, to extend your corporate data center’s IP space into the Google cloud, or for high-bandwidth traffic (greater than 2Gbps), for example when transferring large data sets.

Dedicated Interconnect can be configured to offer a 99.9% or a 99.99% uptime SLA. Please see the Dedicated Interconnect documentation for details on how to achieve these SLAs.

IPsec VPN


Google Cloud VPN securely connects your on-premises network to your GCP Virtual Private Cloud (VPC) network through an IPsec VPN connection. Traffic traveling between the two networks is encrypted by one VPN gateway, then decrypted by the other VPN gateway. This protects your data as it travels over the Internet.

Useful to connect to your VPC over the public internet for low volume data connections

Peering Connection Options


Direct Peering


If you require access to Google and Google Cloud properties and can satisfy Google’s peering requirements, Direct Peering is the solution. Direct peering does not have an SLA.

Useful to connect directly to Google, and to save up to 67% on egress fees compared to VPN or public access over the Internet.

Carrier Peering


If you require access to Google public infrastructure and cannot satisfy Google’s peering requirements, you can connect via a Carrier Peering partner. Carrier Peering does not have an SLA.

Useful if you like the benefits of Direct Peering, but are unable to meet the peering requirements without a partner.

Here is a side by side comparison of the Interconnect options.




















CONNECTIONACCESS TYPECAPACITYCOSTOTHER CONSIDERATIONS
Dedicated Interconnect
Dedicated, direct connection to VPC networksInternal IP addresses in RFC 1918 addresss space10 Gbps for each linkReduced egress costs, fee for each link and VLANRequires you to have a connection in a Google supported colocation facility, either directly or through a carrier
IPsec VPN tunnel
Encrypted tunnel to VPC networks through the public InternetInternal IP addresses in RFC 1918 address space1.5-3 Gbps for each tunnelEgress is billed the same as general network pricing, fee for each tunnelRequires a VPN device on your on-premises network

Here is a side by side comparison of the Peering options.




















CONNECTIONACCESS TYPECAPACITYCOSTOTHER CONSIDERATIONS
Direct Peering
Dedicated, direct connection to Google's networkPublic IP addresses10 Gbps for each linkSettlement free peering, reduced cost for egressRequires you to have a connection in a colocation facility, either directly or through a carrier provided wave service
Carrier Peering
Peering through service provider to Google’s public network (list of partners)Public IP AddressesVaries based on partner offeringCost based on partner offering, reduced cost for egressRequirements vary by partner



Dedicated Interconnect Pricing









RESOURCEPRICE
Interconnect$1,700 a month per 10 Gbps link
VLAN attachment$72 a month per attachment

Egress traffic from a VPC network through an interconnect:














REGIONPRICE
Asia (asia-east1, asia-northeast1, asia-southeast1)$0.042 per GB
Europe (europe-west1, europe-west2, europe-west3)$0.02 per GB
NA (us-central1, us-east1, us-east4, us-west1, us-west2)$0.02 per GB
Australia (austrailia-southeast1)$0.042 per GB

Learn more at the Dedicated Interconnect pricing page.



Direct Peering Pricing


Google does not charge for peering. Establishing a direct peering connection with Google is free. There is no ongoing cost per port or fractional port involved, and no per hour charges.

Google Cloud Platform traffic egressing direct peering connections within a geolocation is billed at the rate listed in the table below. Traffic within a geolocation will be billed at standard Google Cloud Platform rates for traffic egress to the Internet.

Traffic from Google services that is not part of Google Cloud Platform is free of charge.

Carrier Peering Pricing


Google does not charge for Carrier peering, however your service provider may charge for their services. Please consult with your Carrier Peering service provider for details on their specific offering.

Google Cloud Platform traffic egressing Carrier Peering connections within a geolocation is billed at the rate listed below. Pricing is applicable for traffic within a region. Interregional traffic will be billed at standard Google Cloud Platform rates for traffic egressed to the Internet.

Traffic from Google services (e.g. G Suite) that is not part of Google Cloud Platform is free of charge.









PRICINGINGRESSINTRA-REGION GOOGLE CLOUD PLATFORM TRAFFIC EGRESS
Direct PeeringFree for all regions.NA: $0.04/GB
EU: $0.05/GB
APAC: $0.06/GB
Carrier PeeringFree for all regions.NA: $0.04/GB
EU: $0.05/GB
APAC: $0.06/GB


“ Accessing GCP with high bandwidth, low latency, and consistent network connectivity is critical for our business objectives. Google's Dedicated Interconnect allows us to successfully achieve higher reliability, higher throughput, and lower latency while reducing the total cost of ownership by more than 60%, compared to solutions over the public internet. ”

—Nhan Phan, VP of Engineering at Metamarkets




google cloud direct connect, google direct connect setup, google plus direct connect
Source: http://docphy.com/technology/computers/software/cloud-interconnect.html

No comments:

Post a Comment