Before you begin
Review how service accounts work in Identity and Access Management.
Tenant and customer projects
Cloud Data Fusion sets up service accounts to access resources in the following projects:
- Tenant project
Cloud Data Fusion creates a tenant project to hold the resources and services it needs to manage pipelines on your behalf. For example: running pipelines on your Dataproc clusters that reside in your customer project. A tenant project is not exposed to customers, but when you create a private instance, you might need to use the tenant project name to set up VPC peering.
For more information, see the Service Infrastructure documentation about tenant projects.
- Customer project
The customer creates and owns this project. By default, Cloud Data Fusion creates an ephemeral Dataproc cluster in this project to run the customer's pipelines.
The following diagram shows a Cloud Data Fusion instance running in a tenant project and a pipeline running on a Dataproc cluster in a customer project.
Service accounts in Cloud Data Fusion
A service account provides an identity for Cloud Data Fusion, which gives Cloud Data Fusion access to your resources.
When you enable the Cloud Data Fusion API, Cloud Data Fusion creates a Google-managed service account to get access to resources like Service Networking, Dataproc, Cloud Storage, BigQuery, Cloud Spanner, and Cloud Bigtable resources. This service account is called the Cloud Data Fusion API Service Agent. Roles are automatically granted to this service agent.
A service account is identified by its email address, which is unique to the account.
The following table lists the types of service accounts used in Cloud Data Fusion. For more information, see Types of service accounts in the IAM documentation.
||The Google-managed service account, called the Cloud Data Fusion API Service Agent, which Cloud Data Fusion creates to gain access to customer resources so that it can act on the customer's behalf. It is used in the tenant project to access customer project resources. For example, Preview runs in memory instead of in a Dataproc cluster.|
||The default Compute Engine service account that Cloud Data Fusion creates to deploy jobs that access other Google Cloud resources. By default, it attaches to a Dataproc cluster VM to enable Cloud Data Fusion to access Dataproc resources during a pipeline run. In the Cloud Data Fusion Enterprise edition, you can run pipelines from a user-managed service account by creating a profile from the Cloud Data Fusion console→System Admin→Configuration tab and adding the custom service account. In versions 6.2.3 and later, you can choose a custom service account to attach to the Dataproc cluster when creating a Cloud Data Fusion instance. For more information, see Service accounts in Dataproc.|
||Deprecated. This service account is not created or used. It is output as an API field for finding the tenant project name to be used in peering (see Set up VPC network peering).|
- Learn about controlling access to data.
- Grant service account user permission.
- See Cloud Data Fusion pricing.