We recommend new projects start with resources from the AWS provider.
aws-native.codedeploy.DeploymentConfig
Explore with Pulumi AI
We recommend new projects start with resources from the AWS provider.
Resource Type definition for AWS::CodeDeploy::DeploymentConfig
Create DeploymentConfig Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new DeploymentConfig(name: string, args?: DeploymentConfigArgs, opts?: CustomResourceOptions);
@overload
def DeploymentConfig(resource_name: str,
args: Optional[DeploymentConfigArgs] = None,
opts: Optional[ResourceOptions] = None)
@overload
def DeploymentConfig(resource_name: str,
opts: Optional[ResourceOptions] = None,
compute_platform: Optional[str] = None,
deployment_config_name: Optional[str] = None,
minimum_healthy_hosts: Optional[DeploymentConfigMinimumHealthyHostsArgs] = None,
traffic_routing_config: Optional[DeploymentConfigTrafficRoutingConfigArgs] = None,
zonal_config: Optional[DeploymentConfigZonalConfigArgs] = None)
func NewDeploymentConfig(ctx *Context, name string, args *DeploymentConfigArgs, opts ...ResourceOption) (*DeploymentConfig, error)
public DeploymentConfig(string name, DeploymentConfigArgs? args = null, CustomResourceOptions? opts = null)
public DeploymentConfig(String name, DeploymentConfigArgs args)
public DeploymentConfig(String name, DeploymentConfigArgs args, CustomResourceOptions options)
type: aws-native:codedeploy:DeploymentConfig
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args DeploymentConfigArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args DeploymentConfigArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args DeploymentConfigArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args DeploymentConfigArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args DeploymentConfigArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
DeploymentConfig Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The DeploymentConfig resource accepts the following input properties:
- Compute
Platform string - The destination platform type for the deployment (Lambda, Server, or ECS).
- Deployment
Config stringName - A name for the deployment configuration. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the deployment configuration name. For more information, see Name Type.
- Minimum
Healthy Pulumi.Hosts Aws Native. Code Deploy. Inputs. Deployment Config Minimum Healthy Hosts - The minimum number of healthy instances that should be available at any time during the deployment. There are two parameters expected in the input: type and value.
- Traffic
Routing Pulumi.Config Aws Native. Code Deploy. Inputs. Deployment Config Traffic Routing Config - The configuration that specifies how the deployment traffic is routed.
- Zonal
Config Pulumi.Aws Native. Code Deploy. Inputs. Deployment Config Zonal Config - The zonal deployment config that specifies how the zonal deployment behaves
- Compute
Platform string - The destination platform type for the deployment (Lambda, Server, or ECS).
- Deployment
Config stringName - A name for the deployment configuration. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the deployment configuration name. For more information, see Name Type.
- Minimum
Healthy DeploymentHosts Config Minimum Healthy Hosts Args - The minimum number of healthy instances that should be available at any time during the deployment. There are two parameters expected in the input: type and value.
- Traffic
Routing DeploymentConfig Config Traffic Routing Config Args - The configuration that specifies how the deployment traffic is routed.
- Zonal
Config DeploymentConfig Zonal Config Args - The zonal deployment config that specifies how the zonal deployment behaves
- compute
Platform String - The destination platform type for the deployment (Lambda, Server, or ECS).
- deployment
Config StringName - A name for the deployment configuration. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the deployment configuration name. For more information, see Name Type.
- minimum
Healthy DeploymentHosts Config Minimum Healthy Hosts - The minimum number of healthy instances that should be available at any time during the deployment. There are two parameters expected in the input: type and value.
- traffic
Routing DeploymentConfig Config Traffic Routing Config - The configuration that specifies how the deployment traffic is routed.
- zonal
Config DeploymentConfig Zonal Config - The zonal deployment config that specifies how the zonal deployment behaves
- compute
Platform string - The destination platform type for the deployment (Lambda, Server, or ECS).
- deployment
Config stringName - A name for the deployment configuration. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the deployment configuration name. For more information, see Name Type.
- minimum
Healthy DeploymentHosts Config Minimum Healthy Hosts - The minimum number of healthy instances that should be available at any time during the deployment. There are two parameters expected in the input: type and value.
- traffic
Routing DeploymentConfig Config Traffic Routing Config - The configuration that specifies how the deployment traffic is routed.
- zonal
Config DeploymentConfig Zonal Config - The zonal deployment config that specifies how the zonal deployment behaves
- compute_
platform str - The destination platform type for the deployment (Lambda, Server, or ECS).
- deployment_
config_ strname - A name for the deployment configuration. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the deployment configuration name. For more information, see Name Type.
- minimum_
healthy_ Deploymenthosts Config Minimum Healthy Hosts Args - The minimum number of healthy instances that should be available at any time during the deployment. There are two parameters expected in the input: type and value.
- traffic_
routing_ Deploymentconfig Config Traffic Routing Config Args - The configuration that specifies how the deployment traffic is routed.
- zonal_
config DeploymentConfig Zonal Config Args - The zonal deployment config that specifies how the zonal deployment behaves
- compute
Platform String - The destination platform type for the deployment (Lambda, Server, or ECS).
- deployment
Config StringName - A name for the deployment configuration. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the deployment configuration name. For more information, see Name Type.
- minimum
Healthy Property MapHosts - The minimum number of healthy instances that should be available at any time during the deployment. There are two parameters expected in the input: type and value.
- traffic
Routing Property MapConfig - The configuration that specifies how the deployment traffic is routed.
- zonal
Config Property Map - The zonal deployment config that specifies how the zonal deployment behaves
Outputs
All input properties are implicitly available as output properties. Additionally, the DeploymentConfig resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Supporting Types
DeploymentConfigMinimumHealthyHosts, DeploymentConfigMinimumHealthyHostsArgs
- Type string
The minimum healthy instance type:
- HOST_COUNT: The minimum number of healthy instance as an absolute value.
- FLEET_PERCENT: The minimum number of healthy instance as a percentage of the total number of instance in the deployment.
In an example of nine instance, 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 instance at a time. The deployment is successful if four or more instance are deployed to successfully. Otherwise, the deployment fails.
In a call to
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, AWS 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 AWS CodeDeploy Instance Health in the AWS CodeDeploy User Guide .
- Value int
- The minimum healthy instance value.
- Type string
The minimum healthy instance type:
- HOST_COUNT: The minimum number of healthy instance as an absolute value.
- FLEET_PERCENT: The minimum number of healthy instance as a percentage of the total number of instance in the deployment.
In an example of nine instance, 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 instance at a time. The deployment is successful if four or more instance are deployed to successfully. Otherwise, the deployment fails.
In a call to
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, AWS 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 AWS CodeDeploy Instance Health in the AWS CodeDeploy User Guide .
- Value int
- The minimum healthy instance value.
- type String
The minimum healthy instance type:
- HOST_COUNT: The minimum number of healthy instance as an absolute value.
- FLEET_PERCENT: The minimum number of healthy instance as a percentage of the total number of instance in the deployment.
In an example of nine instance, 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 instance at a time. The deployment is successful if four or more instance are deployed to successfully. Otherwise, the deployment fails.
In a call to
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, AWS 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 AWS CodeDeploy Instance Health in the AWS CodeDeploy User Guide .
- value Integer
- The minimum healthy instance value.
- type string
The minimum healthy instance type:
- HOST_COUNT: The minimum number of healthy instance as an absolute value.
- FLEET_PERCENT: The minimum number of healthy instance as a percentage of the total number of instance in the deployment.
In an example of nine instance, 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 instance at a time. The deployment is successful if four or more instance are deployed to successfully. Otherwise, the deployment fails.
In a call to
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, AWS 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 AWS CodeDeploy Instance Health in the AWS CodeDeploy User Guide .
- value number
- The minimum healthy instance value.
- type str
The minimum healthy instance type:
- HOST_COUNT: The minimum number of healthy instance as an absolute value.
- FLEET_PERCENT: The minimum number of healthy instance as a percentage of the total number of instance in the deployment.
In an example of nine instance, 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 instance at a time. The deployment is successful if four or more instance are deployed to successfully. Otherwise, the deployment fails.
In a call to
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, AWS 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 AWS CodeDeploy Instance Health in the AWS CodeDeploy User Guide .
- value int
- The minimum healthy instance value.
- type String
The minimum healthy instance type:
- HOST_COUNT: The minimum number of healthy instance as an absolute value.
- FLEET_PERCENT: The minimum number of healthy instance as a percentage of the total number of instance in the deployment.
In an example of nine instance, 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 instance at a time. The deployment is successful if four or more instance are deployed to successfully. Otherwise, the deployment fails.
In a call to
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, AWS 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 AWS CodeDeploy Instance Health in the AWS CodeDeploy User Guide .
- value Number
- The minimum healthy instance value.
DeploymentConfigMinimumHealthyHostsPerZone, DeploymentConfigMinimumHealthyHostsPerZoneArgs
DeploymentConfigTimeBasedCanary, DeploymentConfigTimeBasedCanaryArgs
- Canary
Interval int - The number of minutes between the first and second traffic shifts of a
TimeBasedCanary
deployment. - Canary
Percentage int - The percentage of traffic to shift in the first increment of a
TimeBasedCanary
deployment.
- Canary
Interval int - The number of minutes between the first and second traffic shifts of a
TimeBasedCanary
deployment. - Canary
Percentage int - The percentage of traffic to shift in the first increment of a
TimeBasedCanary
deployment.
- canary
Interval Integer - The number of minutes between the first and second traffic shifts of a
TimeBasedCanary
deployment. - canary
Percentage Integer - The percentage of traffic to shift in the first increment of a
TimeBasedCanary
deployment.
- canary
Interval number - The number of minutes between the first and second traffic shifts of a
TimeBasedCanary
deployment. - canary
Percentage number - The percentage of traffic to shift in the first increment of a
TimeBasedCanary
deployment.
- canary_
interval int - The number of minutes between the first and second traffic shifts of a
TimeBasedCanary
deployment. - canary_
percentage int - The percentage of traffic to shift in the first increment of a
TimeBasedCanary
deployment.
- canary
Interval Number - The number of minutes between the first and second traffic shifts of a
TimeBasedCanary
deployment. - canary
Percentage Number - The percentage of traffic to shift in the first increment of a
TimeBasedCanary
deployment.
DeploymentConfigTimeBasedLinear, DeploymentConfigTimeBasedLinearArgs
- Linear
Interval int - The number of minutes between each incremental traffic shift of a
TimeBasedLinear
deployment. - Linear
Percentage int - The percentage of traffic that is shifted at the start of each increment of a
TimeBasedLinear
deployment.
- Linear
Interval int - The number of minutes between each incremental traffic shift of a
TimeBasedLinear
deployment. - Linear
Percentage int - The percentage of traffic that is shifted at the start of each increment of a
TimeBasedLinear
deployment.
- linear
Interval Integer - The number of minutes between each incremental traffic shift of a
TimeBasedLinear
deployment. - linear
Percentage Integer - The percentage of traffic that is shifted at the start of each increment of a
TimeBasedLinear
deployment.
- linear
Interval number - The number of minutes between each incremental traffic shift of a
TimeBasedLinear
deployment. - linear
Percentage number - The percentage of traffic that is shifted at the start of each increment of a
TimeBasedLinear
deployment.
- linear_
interval int - The number of minutes between each incremental traffic shift of a
TimeBasedLinear
deployment. - linear_
percentage int - The percentage of traffic that is shifted at the start of each increment of a
TimeBasedLinear
deployment.
- linear
Interval Number - The number of minutes between each incremental traffic shift of a
TimeBasedLinear
deployment. - linear
Percentage Number - The percentage of traffic that is shifted at the start of each increment of a
TimeBasedLinear
deployment.
DeploymentConfigTrafficRoutingConfig, DeploymentConfigTrafficRoutingConfigArgs
- Type string
- The type of traffic shifting (
TimeBasedCanary
orTimeBasedLinear
) used by a deployment configuration. - Time
Based Pulumi.Canary Aws Native. Code Deploy. Inputs. Deployment Config Time Based Canary - 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.
- Time
Based Pulumi.Linear Aws Native. Code Deploy. Inputs. Deployment Config Time Based Linear - 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.
- Type string
- The type of traffic shifting (
TimeBasedCanary
orTimeBasedLinear
) used by a deployment configuration. - Time
Based DeploymentCanary Config Time Based Canary - 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.
- Time
Based DeploymentLinear Config Time Based Linear - 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.
- type String
- The type of traffic shifting (
TimeBasedCanary
orTimeBasedLinear
) used by a deployment configuration. - time
Based DeploymentCanary Config Time Based Canary - 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.
- time
Based DeploymentLinear Config Time Based Linear - 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.
- type string
- The type of traffic shifting (
TimeBasedCanary
orTimeBasedLinear
) used by a deployment configuration. - time
Based DeploymentCanary Config Time Based Canary - 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.
- time
Based DeploymentLinear Config Time Based Linear - 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.
- type str
- The type of traffic shifting (
TimeBasedCanary
orTimeBasedLinear
) used by a deployment configuration. - time_
based_ Deploymentcanary Config Time Based Canary - 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.
- time_
based_ Deploymentlinear Config Time Based Linear - 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.
- type String
- The type of traffic shifting (
TimeBasedCanary
orTimeBasedLinear
) used by a deployment configuration. - time
Based Property MapCanary - 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.
- time
Based Property MapLinear - 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.
DeploymentConfigZonalConfig, DeploymentConfigZonalConfigArgs
- First
Zone intMonitor Duration In Seconds 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 themonitorDurationInSeconds
value for the first Availability Zone.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- Minimum
Healthy Pulumi.Hosts Per Zone Aws Native. Code Deploy. Inputs. Deployment Config Minimum Healthy Hosts Per Zone 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 in the CodeDeploy User Guide .If you don't specify the
minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of0
percent.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- Monitor
Duration intIn Seconds 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 in the CodeDeploy User Guide .
- First
Zone intMonitor Duration In Seconds 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 themonitorDurationInSeconds
value for the first Availability Zone.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- Minimum
Healthy DeploymentHosts Per Zone Config Minimum Healthy Hosts Per Zone 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 in the CodeDeploy User Guide .If you don't specify the
minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of0
percent.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- Monitor
Duration intIn Seconds 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 in the CodeDeploy User Guide .
- first
Zone IntegerMonitor Duration In Seconds 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 themonitorDurationInSeconds
value for the first Availability Zone.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- minimum
Healthy DeploymentHosts Per Zone Config Minimum Healthy Hosts Per Zone 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 in the CodeDeploy User Guide .If you don't specify the
minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of0
percent.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- monitor
Duration IntegerIn Seconds 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 in the CodeDeploy User Guide .
- first
Zone numberMonitor Duration In Seconds 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 themonitorDurationInSeconds
value for the first Availability Zone.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- minimum
Healthy DeploymentHosts Per Zone Config Minimum Healthy Hosts Per Zone 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 in the CodeDeploy User Guide .If you don't specify the
minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of0
percent.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- monitor
Duration numberIn Seconds 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 in the CodeDeploy User Guide .
- first_
zone_ intmonitor_ duration_ in_ seconds 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 themonitorDurationInSeconds
value for the first Availability Zone.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- minimum_
healthy_ Deploymenthosts_ per_ zone Config Minimum Healthy Hosts Per Zone 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 in the CodeDeploy User Guide .If you don't specify the
minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of0
percent.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- monitor_
duration_ intin_ seconds 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 in the CodeDeploy User Guide .
- first
Zone NumberMonitor Duration In Seconds 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 themonitorDurationInSeconds
value for the first Availability Zone.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- minimum
Healthy Property MapHosts Per Zone 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 in the CodeDeploy User Guide .If you don't specify the
minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of0
percent.For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
- monitor
Duration NumberIn Seconds 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 in the CodeDeploy User Guide .
Package Details
- Repository
- AWS Native pulumi/pulumi-aws-native
- License
- Apache-2.0
We recommend new projects start with resources from the AWS provider.