Optional
additionalOptional
Readonly
allowOptional
Readonly
associateWhether instances in the Auto Scaling Group should have public IP addresses associated with them.
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
Optional
Readonly
autoThe name of the Auto Scaling group. This name must be unique per Region per account.
Optional
Readonly
blockSpecifies how block devices are exposed to the instance. You can specify virtual devices and EBS volumes.
Each instance that is launched has an associated root device volume, either an Amazon EBS volume or an instance store volume. You can use block device mappings to specify additional EBS volumes or instance store volumes to attach to an instance when it is launched.
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
Optional
Readonly
capacityIndicates whether Capacity Rebalancing is enabled. When you turn on Capacity Rebalancing, Amazon EC2 Auto Scaling attempts to launch a Spot Instance whenever Amazon EC2 notifies that a Spot Instance is at an elevated risk of interruption. After launching a new instance, it then terminates an old instance.
Optional
Readonly
cooldownDefault scaling cooldown for this AutoScalingGroup
Optional
defaultThe amount of time, in seconds, until a newly launched instance can contribute to the Amazon CloudWatch metrics. This delay lets an instance finish initializing before Amazon EC2 Auto Scaling aggregates instance metrics, resulting in more reliable usage data. Set this value equal to the amount of time that it takes for resource consumption to become stable after an instance reaches the InService state.
To optimize the performance of scaling policies that scale continuously, such as target tracking and step scaling policies, we strongly recommend that you enable the default instance warmup, even if its value is set to 0 seconds
Default instance warmup will not be added if no value is specified
Optional
enabledOptional
Readonly
groupEnable monitoring for group metrics, these metrics describe the group rather than any of its instances.
To report all group metrics use GroupMetrics.all()
Group metrics are reported in a granularity of 1 minute at no additional charge.
Optional
Readonly
healthConfiguration for health checks
Optional
httpOptional
Readonly
ignoreIf the ASG has scheduled actions, don't reset unchanged group sizes
Only used if the ASG has scheduled actions (which may scale your ASG up or down regardless of cdk deployments). If true, the size of the group will only be reset if it has been changed in the CDK app. If false, the sizes will always be changed back to what they were in the CDK app on deployment.
Optional
imageOptional
imageIf you are using GuCDK to generate your riff-raff.yaml file, specify AMIgo props here. If you are using a hardcoded riff-raff.yaml file (usually found in project root) then providing a value here has no effect.
Optional
Readonly
initApply the given CloudFormation Init configuration to the instances in the AutoScalingGroup at startup
If you specify init
, you must also specify signals
to configure
the number of instances to wait for and the timeout for waiting for the
init process.
Optional
Readonly
initUse the given options for applying CloudFormation Init
Describes the configsets to use and the timeout to wait
Optional
Readonly
instanceControls whether instances in this group are launched with detailed or basic monitoring.
When detailed monitoring is enabled, Amazon CloudWatch generates metrics every minute and your account is charged a fee. When you disable detailed monitoring, CloudWatch generates metrics every 5 minutes.
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
Type of instance to launch
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
Optional
Readonly
keyName of SSH keypair to grant access to instances
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
You can either specify keyPair
or keyName
, not both.
Optional
Readonly
keyThe SSH keypair to grant access to the instance.
Feature flag AUTOSCALING_GENERATE_LAUNCH_TEMPLATE
must be enabled to use this property.
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified.
You can either specify keyPair
or keyName
, not both.
Optional
Readonly
launchLaunch template to use.
Launch configuration related settings and MixedInstancesPolicy must not be specified when a launch template is specified.
Optional
Readonly
maxSpecifies the upper threshold as a percentage of the desired capacity of the Auto Scaling group. It represents the maximum percentage of the group that can be in service and healthy, or pending, to support your workload when replacing instances.
Value range is 0 to 100. After it's set, both minHealthyPercentage
and maxHealthyPercentage
to
-1 will clear the previously set value.
Both or neither of minHealthyPercentage
and maxHealthyPercentage
must be specified, and the
difference between them cannot be greater than 100. A large range increases the number of
instances that can be replaced at the same time.
Optional
maximumThe maximum number of EC2 instances.
If omitted, this will be set to minimumInstances * 2
.
This allows us to support Riff-Raff's autoscaling deployment type by default.
Should only be set if you need to scale beyond the default limit (e.g. due to heavy traffic), or restrict scaling for a specific reason.
Note: If minimumInstances
is defined with a Mapping maximumInstances
must also be defined as a Mapping.
Optional
Readonly
maxThe maximum amount of time that an instance can be in service. The maximum duration applies to all current and future instances in the group. As an instance approaches its maximum duration, it is terminated and replaced, and cannot be used again.
You must specify a value of at least 604,800 seconds (7 days). To clear a previously set value, leave this property undefined.
Optional
Readonly
minSpecifies the lower threshold as a percentage of the desired capacity of the Auto Scaling group. It represents the minimum percentage of the group to keep in service, healthy, and ready to use to support your workload when replacing instances.
Value range is 0 to 100. After it's set, both minHealthyPercentage
and maxHealthyPercentage
to
-1 will clear the previously set value.
Both or neither of minHealthyPercentage
and maxHealthyPercentage
must be specified, and the
difference between them cannot be greater than 100. A large range increases the number of
instances that can be replaced at the same time.
The number of EC2 instances running under normal circumstances, i.e. when there are no deployment or scaling events in progress.
Optional
Readonly
mixedMixed Instances Policy to use.
Launch configuration related settings and Launch Template must not be specified when a MixedInstancesPolicy is specified.
Optional
Readonly
newWhether newly-launched instances are protected from termination by Amazon EC2 Auto Scaling when scaling in.
By default, Auto Scaling can terminate an instance at any time after launch when scaling in an Auto Scaling Group, subject to the group's termination policy. However, you may wish to protect newly-launched instances from being scaled in if they are going to run critical applications that should not be prematurely terminated.
This flag must be enabled if the Auto Scaling Group will be associated with an ECS Capacity Provider with managed termination protection.
Optional
Readonly
notificationsConfigure autoscaling group to send notifications about fleet changes to an SNS topic(s)
Optional
Readonly
roleAn IAM role to associate with the instance profile assigned to this Auto Scaling Group.
The role must be assumable by the service principal ec2.amazonaws.com
:
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
Optional
Readonly
signalsConfigure waiting for signals during deployment
Use this to pause the CloudFormation deployment to wait for the instances
in the AutoScalingGroup to report successful startup during
creation and updates. The UserData script needs to invoke cfn-signal
with a success or failure code after it is done setting up the instance.
Without waiting for signals, the CloudFormation deployment will proceed as soon as the AutoScalingGroup has been created or updated but before the instances in the group have been started.
For example, to have instances wait for an Elastic Load Balancing health check before they signal success, add a health-check verification by using the cfn-init helper script. For an example, see the verify_instance_health command in the Auto Scaling rolling updates sample template:
Optional
Readonly
spotThe maximum hourly price (in USD) to be paid for any Spot Instance launched to fulfill the request. Spot Instances are launched when the price you specify exceeds the current Spot market price.
launchTemplate
and mixedInstancesPolicy
must not be specified when this property is specified
Optional
Readonly
ssmAdd SSM session permissions to the instance role
Setting this to true
adds the necessary permissions to connect
to the instance using SSM Session Manager. You can do this
from the AWS Console.
NOTE: Setting this flag to true
may not be enough by itself.
You must also use an AMI that comes with the SSM Agent, or install
the SSM Agent yourself. See
Working with SSM Agent
in the SSM Developer Guide.
Optional
targetOptional
Readonly
terminationA policy or a list of policies that are used to select the instances to terminate. The policies are executed in the order that you list them.
Optional
Readonly
terminationA lambda function Arn that can be used as a custom termination policy to select the instances to terminate. This property must be specified if the TerminationPolicy.CUSTOM_LAMBDA_FUNCTION is used.
Optional
Readonly
updateWhat to do when an AutoScalingGroup's instance configuration is changed
This is applied when any of the settings on the ASG are changed that affect how the instances should be created (VPC, instance type, startup scripts, etc.). It indicates how the existing instances should be replaced with new instances matching the new config. By default, nothing is done and only new instances are launched with the new config.
Readonly
vpcVPC to launch these instances in.
Optional
Readonly
vpcWhere to place instances within the VPC
Optional
without
Whether the instances can initiate connections to anywhere by default