[Video](https://www.youtube.com/watch?v=HUm0BiRDYf8)

Partner Cross-Cloud Interconnect for managed cloud partners provides multicloud connectivity between Google Cloud
and another cloud service provider (CSP). It lets you connect any
Google Cloud and CSP resources privately in
[available paired locations](https://docs.cloud.google.com/network-connectivity/docs/interconnect/how-to/partner-cci-for-csp/paired-locations).
Partner Cross-Cloud Interconnect for managed cloud partners
supports connections at multiple speeds
for traffic that is exchanged between Google Cloud and other
CSPs.

Partner Cross-Cloud Interconnect supports
the following partners:

- Amazon Web Services (AWS)

Partner Cross-Cloud Interconnect for managed cloud partners
provides an on demand and reliable method
for establishing cross-cloud transport, without having to manually set up
networking components.

This connectivity is represented as region-to-region transport with an
SLA-protected, coordinated underlay built with the managed cloud provider
that can be set up on demand, and sized up and down based on your needs.

Partner Cross-Cloud Interconnect for managed cloud partners is
intended for you if you meet one or more
of the following criteria:

- Run workloads in distributed regions
- Have low bandwidth needs
- Are an application owner with no networking expertise
- Want cross-cloud connectivity without having to manage the physical infrastructure

Partner Cross-Cloud Interconnect for managed cloud partners is an
evolution of Cross-Cloud Interconnect. The partner
Cross-Cloud Interconnect for managed cloud partners API
incorporates redundancy directly into the underlying resources. Unlike
Cross-Cloud Interconnect, where you have to establish and manage
redundancy for your connections, Google Cloud can handle this at the
service level with partner Cross-Cloud Interconnect for
managed cloud partners. This means that the
partner Cross-Cloud Interconnect for managed cloud partners service
is designed with inherent fault tolerance, ensuring a more stable and reliable
connection without requiring you to configure complex redundant setups. Although
Google Cloud and the remote CSP each offer their own SLAs for their
respective portions of the connection, these are fully managed and abstracted
away on both sides, ensuring a unified and simplified reliability experience.

Partner Cross-Cloud Interconnect for managed cloud partners provides
the following benefits:

- Lower bandwidth options when you don't need increments of 10 Gbps or 100 Gbps:
  partner Cross-Cloud Interconnect for managed cloud partners offers
  greater flexibility with bandwidth options. Unlike
  Dedicated Interconnect connections that typically require
  high-capacity links (10 Gbps and 100 Gbps increments), partner
  Cross-Cloud Interconnect for managed cloud partners
  provides lower bandwidth options. This flexibility lets you select bandwidth
  amounts that precisely match your needs, leading to potential cost savings
  for use cases that don't require large data transfer capabilities. The
  ability to size bandwidth up and down on demand further enhances your
  flexibility.

- Fully managed reliability characteristics, avoiding nuances in per-cloud
  SLA definitions.

- Minimal lead time due to prebuilt connectivity: by pre-building and managing
  the cross-cloud connectivity infrastructure, Google Cloud
  reduces the time it takes for you to establish your connections. You don't
  have to wait for physical links or set up complex provisioning processes.

- Eliminates the need for coordination or third-party involvement for physical
  connection issues: Google Cloud takes on the responsibility for the
  underlying physical infrastructure and its reliability, eliminating the need to
  deal with potential issues or coordinate with multiple third-party providers.

- Minimal networking knowledge: route exchange between the two cloud service
  providers (CSPs) is handled automatically, rather than copying and pasting
  resource information between the two or maintaining large, complex
  configurations to deploy region-to-region connectivity across the clouds.

You can use [Network Connectivity Center (NCC)](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/overview)
or [VPC Network Peering](https://docs.cloud.google.com/vpc/docs/vpc-peering)
to connect the partner Cross-Cloud Interconnect for
managed cloud partners attachment.

## Comparison to Cross-Cloud Interconnect

The following table describes the differences between
partner Cross-Cloud Interconnect for managed cloud partners and Cross-Cloud Interconnect.

| Interconnect connection type | Cross-Cloud Interconnect | Partner Cross-Cloud Interconnect for managed cloud partners |
|---|---|---|
| **Description** | Provides dedicated connectivity between Google Cloud and providers like OCI, AWS, Azure, and Alibaba | Provides dedicated connectivity between Google Cloud and providers like AWS |
| **Needs physical provisioning** | Yes | No |
| **Needs physical attachments and ports** | Yes | No |
| **Connection increments** | 10 Gbps or 100 Gbps | Granular pre approved speeds starting from 1 Gbps to 100 Gbps |
| **Provisioning time** | 1-4 weeks | Minutes |
| **Connection ordering** | Must be initiated from Google Cloud | Bidirectional; can be initiated from Google Cloud or remote managed cloud partner |
| **Resiliency** | Must be configured manually | Built into the product |

## Private Service Connect support

Partner Cross-Cloud Interconnect for managed cloud partners supports
[Private Service Connect](https://docs.cloud.google.com/vpc/docs/private-service-connect). This
feature lets you access managed services privately from inside your
VPC network.

You can enable Private Service Connect by using the
`--psc-routing-enabled` flag when you create the `transport` resource.

For more information about Private Service Connect connection
propagation using NCC, see
[Private Service Connect connection propagation through
NCC](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/psc-propagated-connection-overview).

## Quota

Transport resources are enforced by a per project per region quota. By default,
each project is limited to a single transport resource per region.

For detailed information about quotas, see
[Cloud Interconnect quotas and limits](https://docs.cloud.google.com/network-connectivity/docs/interconnect/quotas).

## Metrics

> [!WARNING]
>
> **Preview**
>
>
> This feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the
> [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

Traffic metrics for the `transport` resource are available in
Cloud Monitoring. For more information about viewing metrics, see
[Monitor connections](https://docs.cloud.google.com/network-connectivity/docs/interconnect/how-to/monitoring).

## What's next

- To find answers to common questions about Cloud Interconnect architecture and features, see the [Cloud Interconnect FAQ](https://docs.cloud.google.com/network-connectivity/docs/interconnect/support/faq).
- To find out more about Cloud Interconnect, see the [Cloud Interconnect overview](https://docs.cloud.google.com/network-connectivity/docs/interconnect/concepts/overview).
- To learn about best practices when planning for and configuring Cloud Interconnect, see [Best practices](https://docs.cloud.google.com/network-connectivity/docs/interconnect/concepts/best-practices).
- To find Google Cloud resource names, see the [Cloud Interconnect APIs](https://docs.cloud.google.com/network-connectivity/docs/interconnect/reference/apis).