---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# gcp_iam_service_account{% #gcp_iam_service_account %}

## `ancestors`{% #ancestors %}

**Type**: `UNORDERED_LIST_STRING`

## `description`{% #description %}

**Type**: `STRING`**Provider name**: `description`**Description**: Optional. A user-specified, human-readable description of the service account. The maximum length is 256 UTF-8 bytes.

## `disabled`{% #disabled %}

**Type**: `BOOLEAN`**Provider name**: `disabled`**Description**: Output only. Whether the service account is disabled.

## `email`{% #email %}

**Type**: `STRING`**Provider name**: `email`**Description**: Output only. The email address of the service account.

## `gcp_display_name`{% #gcp_display_name %}

**Type**: `STRING`**Provider name**: `displayName`**Description**: Optional. A user-specified, human-readable name for the service account. The maximum length is 100 UTF-8 bytes.

## `labels`{% #labels %}

**Type**: `UNORDERED_LIST_STRING`

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `name`**Description**: The resource name of the service account. Use one of the following formats:

- `projects/{PROJECT_ID}/serviceAccounts/{EMAIL_ADDRESS}`
- `projects/{PROJECT_ID}/serviceAccounts/{UNIQUE_ID}`

As an alternative, you can use the `-` wildcard character instead of the project ID:

- `projects/-/serviceAccounts/{EMAIL_ADDRESS}`
- `projects/-/serviceAccounts/{UNIQUE_ID}`

When possible, avoid using the `-` wildcard character, because it can cause response messages to contain misleading error codes. For example, if you try to get the service account `projects/-/serviceAccounts/fake@example.com`, which does not exist, the response contains an HTTP `403 Forbidden` error instead of a `404 Not Found` error.



## `oauth2_client_id`{% #oauth2_client_id %}

**Type**: `STRING`**Provider name**: `oauth2ClientId`**Description**: Output only. The OAuth 2.0 client ID for the service account.

## `organization_id`{% #organization_id %}

**Type**: `STRING`

## `parent`{% #parent %}

**Type**: `STRING`

## `project_id`{% #project_id %}

**Type**: `STRING`

## `project_number`{% #project_number %}

**Type**: `STRING`

## `resource_name`{% #resource_name %}

**Type**: `STRING`

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `unique_id`{% #unique_id %}

**Type**: `STRING`**Provider name**: `uniqueId`**Description**: Output only. The unique, stable numeric ID for the service account. Each service account retains its unique ID even if you delete the service account. For example, if you delete a service account, then create a new service account with the same name, the new service account has a different unique ID than the deleted service account.