IAM and access control overview

By default, all Google Cloud projects come with a single user, the original project creator. No other users have access to the project, and therefore, access to Dataproc Metastore resources, until a user is added as a project member or is bound to a specific resource. This page describes the ways you can add new users to your project and how to set access control for your Dataproc Metastore resources.

What is IAM?

Google Cloud offers Identity and Access Management (IAM), which lets you give more granular access to specific Google Cloud resources and prevents unwanted access to other resources. IAM lets you adopt the security principle of least privilege, so you grant only the necessary access to your resources.

IAM also lets you control who (identity) has what (roles) permission to which resources by setting IAM policies. IAM policies grant specific role(s) to a project member, giving the identity certain permissions. For example, for a given resource, such as a project, you can assign the roles/metastore.admin role to a Google Account and that account can control Dataproc Metastore resources in the project, but cannot manage other resources. You can also use IAM to manage the basic roles granted to project team members.

Access control options for users

To give users the ability to create and manage your Dataproc Metastore resources, you can add users as team members to your project or to specific resources and grant them permissions using IAM roles.

A team member can be an individual user with a valid Google Account, a Google Group, a service account, or a Google Workspace domain. When you add a team member to a project or to a resource, you specify which roles to grant them. IAM provides three types of roles: predefined roles, basic roles, and custom roles.

To see a list of capabilities of each Dataproc Metastore role and API methods that a specific role grants permission to, review the Dataproc Metastore IAM roles documentation.

For other member types, such as service accounts and groups, refer to the Policy binding reference.

Service accounts

When you call Dataproc Metastore APIs to perform actions in a project where your service is located, Dataproc Metastore performs these actions on your behalf by using a service account that has the permissions required to perform the actions. The service accounts listed below have the permissions required to perform Dataproc Metastore actions in the project where your service is located:

  • service-CUSTOMER_PROJECT_NUMBER@gcp-sa-metastore.iam.gserviceaccount.com.

IAM policies for resources

You can grant access to Dataproc Metastore resources by attaching IAM policies directly to those resources, such as a Dataproc Metastore service. An IAM policy lets you manage IAM roles on those resources instead of, or in addition to, managing roles at the project level. This gives you flexibility to apply the principle of least privilege, which is to grant access only to the specific resources that collaborators need to do their work.

Resources also inherit the policies of their parent resources. If you set a policy at the project level, it's inherited by all its child resources. The effective policy for a resource is the union of the policy set at that resource and the policy inherited from higher up in the hierarchy. For more information, read about the IAM policy hierarchy.

You can get and set IAM policies using the Google Cloud Console, the IAM API, or the gcloud command-line tool.

What's next?