Data Transfer Essentials provides cost-effective data transfer between services of the same organization that are distributed across different cloud service providers (CSPs) and connected over public internet. This page provides an overview about Data Transfer Essentials.
When to use Data Transfer Essentials
In some architectures, services of the same organization might reside on different cloud platforms. Customers running such applications face a complex landscape of data transfer options, each with varying costs and performance trade-offs.
Data Transfer Essentials allows for cost-optimized data transfer between two services of an organization that are running on different cloud platforms. It's specifically designed for intra-organization traffic.
Data Transfer Essentials is designed for cross-cloud connectivity for essential supported services, tiers, and regions with external IP connectivity over the internet. For mission-critical services, other Google Cloud products, such as Cross-Cloud Interconnect or Cloud Interconnect, might be more suitable.
For more information, see Frequently asked questions.
How it works
Assume that one of your applications uses two CSPs, one of which is
Google Cloud and the other Cloud service provider A. In
Google Cloud, you use a service in a tier and region that Data Transfer Essentials
supports. You connect from the
Google Cloud service to the service on Cloud service provider A by
using external IP connectivity over the internet.
Data Transfer Essentials helps you configure billing for data
transferred from the Google Cloud service to the service on
Cloud service provider A. When the Data Transfer Essentials
configuration for your service is active, traffic between these resources uses
Data Transfer Essentials billing rather than billing according to
the default network pricing of outbound traffic to the internet for that
service, region, and tier.
Data Transfer Essentials resources
To enable Data Transfer Essentials for your services, create the following Data Transfer Essentials resources:
-
Specifies the services for which you want to enable Data Transfer Essentials. You can create only one Data Transfer Essentials configuration per region per project. You can include only supported services in a configuration.
Associated destinations.
Specifies the external IP addresses and destination CSPs that you want to include in the configuration. You can specify only recognized ASNs.
Auditing
Data Transfer Essentials is designed for intra-organization applications and not for serving third-party customers.
If a configured IP prefix doesn't meet the specified criteria, its associated endpoint is marked as invalid. If all endpoints linked to the IP prefix are considered to be invalid, the IP prefix is labeled as suspended and the traffic directed to it is billed as regular internet traffic.
Data Transfer Essentials is initially offered at no charge when used according to the guidance provided in the documentation. If Data Transfer Essentials becomes a billed service, Google will notify you in advance through Mandatory Service Announcements (MSAs).
To ensure compliance, Google Cloud reserves the right to validate an IP address as a legitimate intra-organization CSP destination.
SLA
No Service Level Agreement (SLA) applies to the Data Transfer Essentials service. If you use a service that supports Data Transfer Essentials, that service might offer its own SLA. For details, see the documentation for that service.
For services that require data transfer with SLA-backed performance and availability, use Network Service Tiers.