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

# aws_codedeploy_deployment_config{% #aws_codedeploy_deployment_config %}

## `account_id`{% #account_id %}

**Type**: `STRING`

## `compute_platform`{% #compute_platform %}

**Type**: `STRING`**Provider name**: `computePlatform`**Description**: The destination platform type for the deployment (`Lambda`, `Server`, or `ECS`).

## `create_time`{% #create_time %}

**Type**: `TIMESTAMP`**Provider name**: `createTime`**Description**: The time at which the deployment configuration was created.

## `deployment_config_id`{% #deployment_config_id %}

**Type**: `STRING`**Provider name**: `deploymentConfigId`**Description**: The deployment configuration ID.

## `deployment_config_name`{% #deployment_config_name %}

**Type**: `STRING`**Provider name**: `deploymentConfigName`**Description**: The deployment configuration name.

## `minimum_healthy_hosts`{% #minimum_healthy_hosts %}

**Type**: `STRUCT`**Provider name**: `minimumHealthyHosts`**Description**: Information about the number or percentage of minimum healthy instances.

- `type`**Type**: `STRING`**Provider name**: `type`**Description**: The minimum healthy instance type:
  - `HOST_COUNT`: The minimum number of healthy instances as an absolute value.
  - `FLEET_PERCENT`: The minimum number of healthy instances as a percentage of the total number of instances in the deployment.
In an example of nine instances, if a HOST_COUNT of six is specified, deploy to up to three instances at a time. The deployment is successful if six or more instances are deployed to successfully. Otherwise, the deployment fails. If a FLEET_PERCENT of 40 is specified, deploy to up to five instances at a time. The deployment is successful if four or more instances are deployed to successfully. Otherwise, the deployment fails.In a call to the `GetDeploymentConfig`, CodeDeployDefault.OneAtATime returns a minimum healthy instance type of MOST_CONCURRENCY and a value of 1. This means a deployment to only one instance at a time. (You cannot set the type to MOST_CONCURRENCY, only to HOST_COUNT or FLEET_PERCENT.) In addition, with CodeDeployDefault.OneAtATime, CodeDeploy attempts to ensure that all instances but one are kept in a healthy state during the deployment. Although this allows one instance at a time to be taken offline for a new deployment, it also means that if the deployment to the last instance fails, the overall deployment is still successful.For more information, see [CodeDeploy Instance Health](https://docs.aws.amazon.com/codedeploy/latest/userguide/instances-health.html) in the CodeDeploy User Guide.
- `value`**Type**: `INT32`**Provider name**: `value`**Description**: The minimum healthy instance value.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `traffic_routing_config`{% #traffic_routing_config %}

**Type**: `STRUCT`**Provider name**: `trafficRoutingConfig`**Description**: The configuration that specifies how the deployment traffic is routed. Used for deployments with a Lambda or Amazon ECS compute platform only.

- `time_based_canary`**Type**: `STRUCT`**Provider name**: `timeBasedCanary`**Description**: A configuration that shifts traffic from one version of a Lambda function or ECS task set to another in two increments. The original and target Lambda function versions or ECS task sets are specified in the deployment's AppSpec file.
  - `canary_interval`**Type**: `INT32`**Provider name**: `canaryInterval`**Description**: The number of minutes between the first and second traffic shifts of a `TimeBasedCanary` deployment.
  - `canary_percentage`**Type**: `INT32`**Provider name**: `canaryPercentage`**Description**: The percentage of traffic to shift in the first increment of a `TimeBasedCanary` deployment.
- `time_based_linear`**Type**: `STRUCT`**Provider name**: `timeBasedLinear`**Description**: A configuration that shifts traffic from one version of a Lambda function or Amazon ECS task set to another in equal increments, with an equal number of minutes between each increment. The original and target Lambda function versions or Amazon ECS task sets are specified in the deployment's AppSpec file.
  - `linear_interval`**Type**: `INT32`**Provider name**: `linearInterval`**Description**: The number of minutes between each incremental traffic shift of a `TimeBasedLinear` deployment.
  - `linear_percentage`**Type**: `INT32`**Provider name**: `linearPercentage`**Description**: The percentage of traffic that is shifted at the start of each increment of a `TimeBasedLinear` deployment.
- `type`**Type**: `STRING`**Provider name**: `type`**Description**: The type of traffic shifting (`TimeBasedCanary` or `TimeBasedLinear`) used by a deployment configuration.

## `zonal_config`{% #zonal_config %}

**Type**: `STRUCT`**Provider name**: `zonalConfig`**Description**: Information about a zonal configuration.

- `first_zone_monitor_duration_in_seconds`**Type**: `INT64`**Provider name**: `firstZoneMonitorDurationInSeconds`**Description**: The period of time, in seconds, that CodeDeploy must wait after completing a deployment to the first Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the second Availability Zone. You might set this option if you want to allow extra bake time for the first Availability Zone. If you don't specify a value for `firstZoneMonitorDurationInSeconds`, then CodeDeploy uses the `monitorDurationInSeconds` value for the first Availability Zone. For more information about the zonal configuration feature, see [zonal configuration](https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations-create.html#zonal-config) in the CodeDeploy User Guide.
- `minimum_healthy_hosts_per_zone`**Type**: `STRUCT`**Provider name**: `minimumHealthyHostsPerZone`**Description**: The number or percentage of instances that must remain available per Availability Zone during a deployment. This option works in conjunction with the `MinimumHealthyHosts` option. For more information, see [About the minimum number of healthy hosts per Availability Zone](https://docs.aws.amazon.com/codedeploy/latest/userguide/instances-health.html#minimum-healthy-hosts-az) in the CodeDeploy User Guide. If you don't specify the `minimumHealthyHostsPerZone` option, then CodeDeploy uses a default value of `0` percent. For more information about the zonal configuration feature, see [zonal configuration](https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations-create.html#zonal-config) in the CodeDeploy User Guide.
  - `type`**Type**: `STRING`**Provider name**: `type`**Description**: The `type` associated with the `MinimumHealthyHostsPerZone` option.
  - `value`**Type**: `INT32`**Provider name**: `value`**Description**: The `value` associated with the `MinimumHealthyHostsPerZone` option.
- `monitor_duration_in_seconds`**Type**: `INT64`**Provider name**: `monitorDurationInSeconds`**Description**: The period of time, in seconds, that CodeDeploy must wait after completing a deployment to an Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the next Availability Zone. Consider adding a monitor duration to give the deployment some time to prove itself (or 'bake') in one Availability Zone before it is released in the next zone. If you don't specify a `monitorDurationInSeconds`, CodeDeploy starts deploying to the next Availability Zone immediately. For more information about the zonal configuration feature, see [zonal configuration](https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations-create.html#zonal-config) in the CodeDeploy User Guide.