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

# aws_codepipeline_pipeline{% #aws_codepipeline_pipeline %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `created`{% #created %}

**Type**: `TIMESTAMP`**Provider name**: `created`**Description**: The date and time the pipeline was created, in timestamp format.

## `execution_mode`{% #execution_mode %}

**Type**: `STRING`**Provider name**: `executionMode`**Description**: The method that the pipeline will use to handle multiple executions. The default mode is SUPERSEDED.

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `name`**Description**: The name of the pipeline.

## `pipeline_arn`{% #pipeline_arn %}

**Type**: `STRING`

## `pipeline_type`{% #pipeline_type %}

**Type**: `STRING`**Provider name**: `pipelineType`**Description**: CodePipeline provides the following pipeline types, which differ in characteristics and price, so that you can tailor your pipeline features and cost to the needs of your applications.

- V1 type pipelines have a JSON structure that contains standard pipeline, stage, and action-level parameters.
- V2 type pipelines have the same structure as a V1 type, along with additional parameters for release safety and trigger configuration.
Including V2 parameters, such as triggers on Git tags, in the pipeline JSON when creating or updating a pipeline will result in the pipeline having the V2 type of pipeline and the associated costs.For information about pricing for CodePipeline, see [Pricing](http://aws.amazon.com/codepipeline/pricing/). For information about which type of pipeline to choose, see [What type of pipeline is right for me?](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipeline-types-planning.html).


## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `updated`{% #updated %}

**Type**: `TIMESTAMP`**Provider name**: `updated`**Description**: The date and time of the last update to the pipeline, in timestamp format.

## `version`{% #version %}

**Type**: `INT32`**Provider name**: `version`**Description**: The version number of the pipeline.