ZonalConfigProperty Struct
Configure the ZonalConfig object if you want AWS CodeDeploy to deploy your application to one Availability Zone at a time, within an AWS Region. By deploying to one Availability Zone at a time, you can expose your deployment to a progressively larger audience as confidence in the deployment's performance and viability grows. If you don't configure the ZonalConfig object, CodeDeploy deploys your application to a random selection of hosts across a Region.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_codedeploy as codedeploy } from 'aws-cdk-lib';
const zonalConfigProperty: codedeploy.CfnDeploymentConfig.ZonalConfigProperty = {
firstZoneMonitorDurationInSeconds: 123,
minimumHealthyHostsPerZone: {
type: 'type',
value: 123,
},
monitorDurationInSeconds: 123,
};
# The code below shows an example of how to instantiate this type.
# The values are placeholders you should change.
from aws_cdk import aws_codedeploy as codedeploy
zonal_config_property = codedeploy.CfnDeploymentConfig.ZonalConfigProperty(
first_zone_monitor_duration_in_seconds=123,
minimum_healthy_hosts_per_zone=codedeploy.CfnDeploymentConfig.MinimumHealthyHostsPerZoneProperty(
type="type",
value=123
),
monitor_duration_in_seconds=123
)
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import software.amazon.awscdk.services.codedeploy.*;
ZonalConfigProperty zonalConfigProperty = ZonalConfigProperty.builder()
.firstZoneMonitorDurationInSeconds(123)
.minimumHealthyHostsPerZone(MinimumHealthyHostsPerZoneProperty.builder()
.type("type")
.value(123)
.build())
.monitorDurationInSeconds(123)
.build();
// Install: dotnet add package Amazon.CDK.Lib
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
using Amazon.CDK.AWS.CodeDeploy;
var zonalConfigProperty = new ZonalConfigProperty {
FirstZoneMonitorDurationInSeconds = 123,
MinimumHealthyHostsPerZone = new MinimumHealthyHostsPerZoneProperty {
Type = "type",
Value = 123
},
MonitorDurationInSeconds = 123
};
// Install: go get github.com/aws/aws-cdk-go/awscdk/v2
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import "github.com/aws/aws-cdk-go/awscdk"
zonalConfigProperty := &ZonalConfigProperty{
FirstZoneMonitorDurationInSeconds: jsii.Number(123),
MinimumHealthyHostsPerZone: &MinimumHealthyHostsPerZoneProperty{
Type: jsii.String("type"),
Value: jsii.Number(123),
},
MonitorDurationInSeconds: jsii.Number(123),
}
Properties
firstZoneMonitorDurationInSecondsoptionalnumberfirst_zone_monitor_duration_in_secondsoptionalint | floatfirstZoneMonitorDurationInSecondsoptionalNumberFirstZoneMonitorDurationInSecondsoptionaldoubleFirstZoneMonitorDurationInSecondsoptional*float64#notes
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 in the CodeDeploy User Guide .
minimumHealthyHostsPerZoneoptionalIResolvable | CfnDeploymentConfig.MinimumHealthyHostsPerZonePropertyminimum_healthy_hosts_per_zoneoptionaltyping.Union[IResolvable, MinimumHealthyHostsPerZoneProperty]minimumHealthyHostsPerZoneoptionalIResolvableMinimumHealthyHostsPerZoneoptionalIResolvableMinimumHealthyHostsPerZoneoptionalinterface{}#notes
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 of 0 percent.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide .
monitorDurationInSecondsoptionalnumbermonitor_duration_in_secondsoptionalint | floatmonitorDurationInSecondsoptionalNumberMonitorDurationInSecondsoptionaldoubleMonitorDurationInSecondsoptional*float64#notes
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 .