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

# gcp_certificatemanager_trust_config{% #gcp_certificatemanager_trust_config %}

## `allowlisted_certificates`{% #allowlisted_certificates %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `allowlistedCertificates`**Description**: Optional. A certificate matching an allowlisted certificate is always considered valid as long as the certificate is parseable, proof of private key possession is established, and constraints on the certificate's SAN field are met.

- `pem_certificate`**Type**: `STRING`**Provider name**: `pemCertificate`**Description**: Required. PEM certificate that is allowlisted. The certificate can be up to 5k bytes, and must be a parseable X.509 certificate.

## `ancestors`{% #ancestors %}

**Type**: `UNORDERED_LIST_STRING`

## `create_time`{% #create_time %}

**Type**: `TIMESTAMP`**Provider name**: `createTime`**Description**: Output only. The creation timestamp of a TrustConfig.

## `description`{% #description %}

**Type**: `STRING`**Provider name**: `description`**Description**: Optional. One or more paragraphs of text description of a TrustConfig.

## `etag`{% #etag %}

**Type**: `STRING`**Provider name**: `etag`**Description**: This checksum is computed by the server based on the value of other fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding.

## `labels`{% #labels %}

**Type**: `UNORDERED_LIST_STRING`

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `name`**Description**: Identifier. A user-defined name of the trust config. TrustConfig names must be unique globally and match pattern `projects/*/locations/*/trustConfigs/*`.

## `organization_id`{% #organization_id %}

**Type**: `STRING`

## `parent`{% #parent %}

**Type**: `STRING`

## `project_id`{% #project_id %}

**Type**: `STRING`

## `project_number`{% #project_number %}

**Type**: `STRING`

## `region_id`{% #region_id %}

**Type**: `STRING`

## `resource_name`{% #resource_name %}

**Type**: `STRING`

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `trust_stores`{% #trust_stores %}

**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `trustStores`**Description**: Optional. Set of trust stores to perform validation against. This field is supported when TrustConfig is configured with Load Balancers, currently not supported for SPIFFE certificate validation. Only one TrustStore specified is currently allowed.

- `intermediate_cas`**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `intermediateCas`**Description**: Optional. Set of intermediate CA certificates used for the path building phase of chain validation. The field is currently not supported if TrustConfig is used for the workload certificate feature.
  - `pem_certificate`**Type**: `STRING`**Provider name**: `pemCertificate`**Description**: PEM intermediate certificate used for building up paths for validation. Each certificate provided in PEM format may occupy up to 5kB.
- `trust_anchors`**Type**: `UNORDERED_LIST_STRUCT`**Provider name**: `trustAnchors`**Description**: Optional. List of Trust Anchors to be used while performing validation against a given TrustStore.
  - `pem_certificate`**Type**: `STRING`**Provider name**: `pemCertificate`**Description**: PEM root certificate of the PKI used for validation. Each certificate provided in PEM format may occupy up to 5kB.

## `update_time`{% #update_time %}

**Type**: `TIMESTAMP`**Provider name**: `updateTime`**Description**: Output only. The last update timestamp of a TrustConfig.

## `zone_id`{% #zone_id %}

**Type**: `STRING`