create_auto_scaling_group ¶

create_auto_scaling_group(
    *,
    config_overrides: Optional[AutoScalingClientConfig] = None,
    auto_scaling_group_name: Optional[XmlStringMaxLen255] = None,
    launch_configuration_name: Optional[XmlStringMaxLen255] = None,
    launch_template: Optional[LaunchTemplateSpecification] = None,
    mixed_instances_policy: Optional[MixedInstancesPolicy] = None,
    instance_id: Optional[XmlStringMaxLen19] = None,
    min_size: Optional[AutoScalingGroupMinSize] = None,
    max_size: Optional[AutoScalingGroupMaxSize] = None,
    desired_capacity: Optional[AutoScalingGroupDesiredCapacity] = None,
    default_cooldown: Optional[Cooldown] = None,
    availability_zones: Optional[AvailabilityZones] = None,
    availability_zone_ids: Optional[AvailabilityZoneIds] = None,
    load_balancer_names: Optional[LoadBalancerNames] = None,
    target_group_ar_ns: Optional[TargetGroupARNs] = None,
    health_check_type: Optional[XmlStringMaxLen32] = None,
    health_check_grace_period: Optional[HealthCheckGracePeriod] = None,
    placement_group: Optional[XmlStringMaxLen255] = None,
    vpc_zone_identifier: Optional[XmlStringMaxLen5000] = None,
    termination_policies: Optional[TerminationPolicies] = None,
    new_instances_protected_from_scale_in: Optional[InstanceProtected] = None,
    capacity_rebalance: Optional[CapacityRebalanceEnabled] = None,
    lifecycle_hook_specification_list: Optional[LifecycleHookSpecifications] = None,
    deletion_protection: Optional[DeletionProtection] = None,
    tags: Optional[Tags] = None,
    service_linked_role_arn: Optional[ResourceName] = None,
    max_instance_lifetime: Optional[MaxInstanceLifetime] = None,
    context: Optional[Context] = None,
    desired_capacity_type: Optional[XmlStringMaxLen255] = None,
    default_instance_warmup: Optional[DefaultInstanceWarmup] = None,
    traffic_sources: Optional[TrafficSources] = None,
    instance_maintenance_policy: Optional[InstanceMaintenancePolicy] = None,
    availability_zone_distribution: Optional[AvailabilityZoneDistribution] = None,
    availability_zone_impairment_policy: Optional[
        AvailabilityZoneImpairmentPolicy
    ] = None,
    skip_zonal_shift_validation: Optional[SkipZonalShiftValidation] = None,
    capacity_reservation_specification: Optional[
        CapacityReservationSpecification
    ] = None,
    instance_lifecycle_policy: Optional[InstanceLifecyclePolicy] = None,
    operator: Optional[Operator] = None,
) -> None

We strongly recommend using a launch template when calling this operation to ensure full functionality for Amazon EC2 Auto Scaling and Amazon EC2.

Creates an Auto Scaling group with the specified name and attributes.

If you exceed your maximum limit of Auto Scaling groups, the call fails. To query this limit, call the DescribeAccountLimits API. For information about updating this limit, see Quotas for Amazon EC2 Auto Scaling in the Amazon EC2 Auto Scaling User Guide.

If you're new to Amazon EC2 Auto Scaling, see the introductory tutorials in Get started with Amazon EC2 Auto Scaling in the Amazon EC2 Auto Scaling User Guide.

Every Auto Scaling group has three size properties (DesiredCapacity, MaxSize, and MinSize). Usually, you set these sizes based on a specific number of instances. However, if you configure a mixed instances policy that defines weights for the instance types, you must specify these sizes with the same units that you use for weighting instances.

Parameters:

auto_scaling_group_name (Optional[XmlStringMaxLen255], default: None ) –

The name of the Auto Scaling group. This name must be unique per Region per account.

The name can contain any ASCII character 33 to 126 including most punctuation characters, digits, and upper and lowercased letters.

You cannot use a colon (:) in the name.
launch_configuration_name (Optional[XmlStringMaxLen255], default: None ) –

The name of the launch configuration to use to launch instances.

Conditional: You must specify either a launch template (LaunchTemplate or MixedInstancesPolicy) or a launch configuration (LaunchConfigurationName or InstanceId).
launch_template (Optional[LaunchTemplateSpecification], default: None ) –

Information used to specify the launch template and version to use to launch instances.

Conditional: You must specify either a launch template (LaunchTemplate or MixedInstancesPolicy) or a launch configuration (LaunchConfigurationName or InstanceId).

The launch template that is specified must be configured for use with an Auto Scaling group. For more information, see Create a launch template for an Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.
mixed_instances_policy (Optional[MixedInstancesPolicy], default: None ) –

The mixed instances policy. For more information, see Auto Scaling groups with multiple instance types and purchase options in the Amazon EC2 Auto Scaling User Guide. To learn how to prioritize multiple capacity types, see Use Distribution Segments to target multiple capacity types in the Amazon EC2 Auto Scaling User Guide.
instance_id (Optional[XmlStringMaxLen19], default: None ) –

The ID of the instance used to base the launch configuration on. If specified, Amazon EC2 Auto Scaling uses the configuration values from the specified instance to create a new launch configuration. To get the instance ID, use the Amazon EC2 DescribeInstances API operation. For more information, see Create an Auto Scaling group using parameters from an existing instance in the Amazon EC2 Auto Scaling User Guide.
min_size (Optional[AutoScalingGroupMinSize], default: None ) –

The minimum size of the group.
max_size (Optional[AutoScalingGroupMaxSize], default: None ) –

The maximum size of the group.

With a mixed instances policy that uses instance weighting, Amazon EC2 Auto Scaling may need to go above MaxSize to meet your capacity requirements. In this event, Amazon EC2 Auto Scaling will never go above MaxSize by more than your largest instance weight (weights that define how many units each instance contributes to the desired capacity of the group).
desired_capacity (Optional[AutoScalingGroupDesiredCapacity], default: None ) –

The desired capacity is the initial capacity of the Auto Scaling group at the time of its creation and the capacity it attempts to maintain. It can scale beyond this capacity if you configure auto scaling. This number must be greater than or equal to the minimum size of the group and less than or equal to the maximum size of the group. If you do not specify a desired capacity, the default is the minimum size of the group.
default_cooldown (Optional[Cooldown], default: None ) –

Only needed if you use simple scaling policies.

The amount of time, in seconds, between one scaling activity ending and another one starting due to simple scaling policies. For more information, see Scaling cooldowns for Amazon EC2 Auto Scaling in the Amazon EC2 Auto Scaling User Guide.

Default: 300 seconds
availability_zones (Optional[AvailabilityZones], default: None ) –

A list of Availability Zones where instances in the Auto Scaling group can be created. Used for launching into the default VPC subnet in each Availability Zone when not using the VPCZoneIdentifier property, or for attaching a network interface when an existing network interface ID is specified in a launch template.
availability_zone_ids (Optional[AvailabilityZoneIds], default: None ) –

A list of Availability Zone IDs where the Auto Scaling group can launch instances. You cannot specify both AvailabilityZones and AvailabilityZoneIds in the same request.
load_balancer_names (Optional[LoadBalancerNames], default: None ) –

A list of Classic Load Balancers associated with this Auto Scaling group. For Application Load Balancers, Network Load Balancers, and Gateway Load Balancers, specify the TargetGroupARNs property instead.
target_group_ar_ns (Optional[TargetGroupARNs], default: None ) –

The Amazon Resource Names (ARN) of the Elastic Load Balancing target groups to associate with the Auto Scaling group. Instances are registered as targets with the target groups. The target groups receive incoming traffic and route requests to one or more registered targets. For more information, see Use Elastic Load Balancing to distribute traffic across the instances in your Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.
health_check_type (Optional[XmlStringMaxLen32], default: None ) –

A comma-separated value string of one or more health check types.

The valid values are EC2, EBS, ELB, and VPC_LATTICE. EC2 is the default health check and cannot be disabled. For more information, see Health checks for instances in an Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.

Only specify EC2 if you must clear a value that was previously set.
health_check_grace_period (Optional[HealthCheckGracePeriod], default: None ) –

The amount of time, in seconds, that Amazon EC2 Auto Scaling waits before checking the health status of an EC2 instance that has come into service and marking it unhealthy due to a failed health check. This is useful if your instances do not immediately pass their health checks after they enter the InService state. For more information, see Set the health check grace period for an Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.

Default: 0 seconds
placement_group (Optional[XmlStringMaxLen255], default: None ) –

The name of the placement group into which to launch your instances. For more information, see Placement groups in the Amazon EC2 User Guide.

A cluster placement group is a logical grouping of instances within a single Availability Zone. You cannot specify multiple Availability Zones and a cluster placement group.
vpc_zone_identifier (Optional[XmlStringMaxLen5000], default: None ) –

A comma-separated list of subnet IDs for a virtual private cloud (VPC) where instances in the Auto Scaling group can be created. If you specify VPCZoneIdentifier with AvailabilityZones, the subnets that you specify must reside in those Availability Zones.
termination_policies (Optional[TerminationPolicies], default: None ) –

A policy or a list of policies that are used to select the instance to terminate. These policies are executed in the order that you list them. For more information, see Configure termination policies for Amazon EC2 Auto Scaling in the Amazon EC2 Auto Scaling User Guide.

Valid values: Default | AllocationStrategy | ClosestToNextInstanceHour | NewestInstance | OldestInstance | OldestLaunchConfiguration | OldestLaunchTemplate | arn:aws:lambda:region:account-id:function:my-function:my-alias
new_instances_protected_from_scale_in (Optional[InstanceProtected], default: None ) –

Indicates whether newly launched instances are protected from termination by Amazon EC2 Auto Scaling when scaling in. For more information about preventing instances from terminating on scale in, see Use instance scale-in protection in the Amazon EC2 Auto Scaling User Guide.
capacity_rebalance (Optional[CapacityRebalanceEnabled], default: None ) –

Indicates whether Capacity Rebalancing is enabled. Otherwise, Capacity Rebalancing is disabled. 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. For more information, see Use Capacity Rebalancing to handle Amazon EC2 Spot Interruptions in the in the Amazon EC2 Auto Scaling User Guide.
lifecycle_hook_specification_list (Optional[LifecycleHookSpecifications], default: None ) –

One or more lifecycle hooks to add to the Auto Scaling group before instances are launched.
deletion_protection (Optional[DeletionProtection], default: None ) –

The deletion protection setting for the Auto Scaling group. This setting helps safeguard your Auto Scaling group and its instances by controlling whether the DeleteAutoScalingGroup operation is allowed. When deletion protection is enabled, users cannot delete the Auto Scaling group according to the specified protection level until the setting is changed back to a less restrictive level.

The valid values are none, prevent-force-deletion, and prevent-all-deletion.

Default: none

For more information, see Configure deletion protection for your Amazon EC2 Auto Scaling resources in the Amazon EC2 Auto Scaling User Guide.
tags (Optional[Tags], default: None ) –

One or more tags. You can tag your Auto Scaling group and propagate the tags to the Amazon EC2 instances it launches. Tags are not propagated to Amazon EBS volumes. To add tags to Amazon EBS volumes, specify the tags in a launch template but use caution. If the launch template specifies an instance tag with a key that is also specified for the Auto Scaling group, Amazon EC2 Auto Scaling overrides the value of that instance tag with the value specified by the Auto Scaling group. For more information, see Tag Auto Scaling groups and instances in the Amazon EC2 Auto Scaling User Guide.
service_linked_role_arn (Optional[ResourceName], default: None ) –

The Amazon Resource Name (ARN) of the service-linked role that the Auto Scaling group uses to call other Amazon Web Services service on your behalf. By default, Amazon EC2 Auto Scaling uses a service-linked role named AWSServiceRoleForAutoScaling, which it creates if it does not exist. For more information, see Service-linked roles in the Amazon EC2 Auto Scaling User Guide.
max_instance_lifetime (Optional[MaxInstanceLifetime], default: None ) –

The maximum amount of time, in seconds, that an instance can be in service. The default is null. If specified, the value must be either 0 or a number equal to or greater than 86,400 seconds (1 day). For more information, see Replace Auto Scaling instances based on maximum instance lifetime in the Amazon EC2 Auto Scaling User Guide.
context (Optional[Context], default: None ) –

Reserved.
desired_capacity_type (Optional[XmlStringMaxLen255], default: None ) –

The unit of measurement for the value specified for desired capacity. Amazon EC2 Auto Scaling supports DesiredCapacityType for attribute-based instance type selection only. For more information, see Create a mixed instances group using attribute-based instance type selection in the Amazon EC2 Auto Scaling User Guide.

By default, Amazon EC2 Auto Scaling specifies units, which translates into number of instances.

Valid values: units | vcpu | memory-mib
default_instance_warmup (Optional[DefaultInstanceWarmup], default: None ) –

The amount of time, in seconds, until a new instance is considered to have finished initializing and resource consumption to become stable after it enters the InService state.

During an instance refresh, Amazon EC2 Auto Scaling waits for the warm-up period after it replaces an instance before it moves on to replacing the next instance. Amazon EC2 Auto Scaling also waits for the warm-up period before aggregating the metrics for new instances with existing instances in the Amazon CloudWatch metrics that are used for scaling, resulting in more reliable usage data. For more information, see Set the default instance warmup for an Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.

To manage various warm-up settings at the group level, we recommend that you set the default instance warmup, even if it is set to 0 seconds. To remove a value that you previously set, include the property but specify -1 for the value. However, we strongly recommend keeping the default instance warmup enabled by specifying a value of 0 or other nominal value.

Default: None
traffic_sources (Optional[TrafficSources], default: None ) –

The list of traffic sources to attach to this Auto Scaling group. You can use any of the following as traffic sources for an Auto Scaling group: Classic Load Balancer, Application Load Balancer, Gateway Load Balancer, Network Load Balancer, and VPC Lattice.
instance_maintenance_policy (Optional[InstanceMaintenancePolicy], default: None ) –

An instance maintenance policy. For more information, see Set instance maintenance policy in the Amazon EC2 Auto Scaling User Guide.
availability_zone_distribution (Optional[AvailabilityZoneDistribution], default: None ) –

The instance capacity distribution across Availability Zones.
availability_zone_impairment_policy (Optional[AvailabilityZoneImpairmentPolicy], default: None ) –

The policy for Availability Zone impairment.
skip_zonal_shift_validation (Optional[SkipZonalShiftValidation], default: None ) –

If you enable zonal shift with cross-zone disabled load balancers, capacity could become imbalanced across Availability Zones. To skip the validation, specify true. For more information, see Auto Scaling group zonal shift in the Amazon EC2 Auto Scaling User Guide.
capacity_reservation_specification (Optional[CapacityReservationSpecification], default: None ) –

The capacity reservation specification for the Auto Scaling group.
instance_lifecycle_policy (Optional[InstanceLifecyclePolicy], default: None ) –

The instance lifecycle policy for the Auto Scaling group. This policy controls instance behavior when an instance transitions through its lifecycle states. Configure retention triggers to specify when instances should move to a Retained state instead of automatic termination.

For more information, see Control instance retention with instance lifecycle policies in the Amazon EC2 Auto Scaling User Guide.

Instances in a Retained state will continue to incur standard EC2 charges until terminated.
operator (Optional[Operator], default: None ) –

The entity that manages the Auto Scaling group. If you specify this parameter, Amazon EC2 Auto Scaling passes the operator identity to EC2 for instance launches and only allows the designated operator to make changes to the Auto Scaling group. All mutating API calls from non-operator callers are rejected with an AccessDenied exception.

Raises:

AlreadyExistsFault –

You already have an Auto Scaling group or launch configuration with this name.
LimitExceededFault –

You have already reached a limit for your Amazon EC2 Auto Scaling resources (for example, Auto Scaling groups, launch configurations, or lifecycle hooks). For more information, see DescribeAccountLimits in the Amazon EC2 Auto Scaling API Reference.
ResourceContentionFault –

You already have a pending update to an Amazon EC2 Auto Scaling resource (for example, an Auto Scaling group, instance, or load balancer).
ServiceLinkedRoleFailure –

The service-linked role is not yet ready for use.
UnknownServiceError –

The service returned an error code this client does not model.

Examples:

To create an Auto Scaling group with an attached target group This example creates an Auto Scaling group and attaches the specified target group.

>>> client.create_auto_scaling_group(auto_scaling_group_name='my-auto-scaling-group', launch_template={'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, min_size=1, max_size=3, target_group_ar_ns=['arn:aws:elasticloadbalancing:us-west-2:123456789012:targetgroup/my-targets/73e2d6bc24d8a067'], health_check_type='ELB', health_check_grace_period=300, vpc_zone_identifier='subnet-057fa0918fEXAMPLE, subnet-610acd08EXAMPLE')
To create an Auto Scaling group with a mixed instances policy
This example creates an Auto Scaling group with a mixed instances policy. It specifies the c5.large, c5a.large, and c6g.large instance types and defines a different launch template for the c6g.large instance type.

>>> client.create_auto_scaling_group(auto_scaling_group_name='my-asg', mixed_instances_policy={'LaunchTemplate': {'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-launch-template-for-x86', 'Version': '$Default'}, 'Overrides': [{'InstanceType': 'c6g.large', 'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-launch-template-for-arm', 'Version': '$Default'}}, {'InstanceType': 'c5.large'}, {'InstanceType': 'c5a.large'}]}, 'InstancesDistribution': {'OnDemandBaseCapacity': 1, 'OnDemandPercentageAboveBaseCapacity': 50, 'SpotAllocationStrategy': 'price-capacity-optimized'}}, min_size=1, max_size=5, desired_capacity=3, vpc_zone_identifier='subnet-057fa0918fEXAMPLE, subnet-610acd08EXAMPLE')
To create an Auto Scaling group using attribute-based instance type selection
This example creates an Auto Scaling group using attribute-based instance type selection. It requires the instance types to have a minimum of four vCPUs and a maximum of eight vCPUs, a minimum of 16,384 MiB of memory, and an Intel manufactured CPU.

>>> client.create_auto_scaling_group(auto_scaling_group_name='my-asg', mixed_instances_policy={'LaunchTemplate': {'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, 'Overrides': [{'InstanceRequirements': {'VCpuCount': {'Min': 4, 'Max': 8}, 'MemoryMiB': {'Min': 16384}, 'CpuManufacturers': ['intel']}}]}, 'InstancesDistribution': {'OnDemandPercentageAboveBaseCapacity': 50, 'SpotAllocationStrategy': 'price-capacity-optimized'}}, min_size=0, max_size=100, desired_capacity=4, desired_capacity_type='units', vpc_zone_identifier='subnet-057fa0918fEXAMPLE, subnet-610acd08EXAMPLE')
To create an Auto Scaling group using Distribution Segments
This example creates an Auto Scaling group that uses Distribution Segments to prioritize On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and then On-Demand capacity.

>>> client.create_auto_scaling_group(auto_scaling_group_name='my-asg', mixed_instances_policy={'LaunchTemplate': {'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, 'Overrides': [{'InstanceType': 'm5.24xlarge'}, {'InstanceType': 'p5.48xlarge'}]}, 'InstancesDistribution': {'OnDemandAllocationStrategy': 'prioritized', 'DistributionSegments': [{'TargetCapacityTypes': ['on-demand-capacity-reservation', 'capacity-block', 'interruptible-capacity-reservation', 'on-demand']}]}}, capacity_reservation_specification={'CapacityReservationTarget': {'CapacityReservationResourceGroupArns': ['arn:aws:resource-groups:us-east-1:123456789012:group/my-capacity-reservation-group']}}, min_size=0, max_size=10, desired_capacity=5, vpc_zone_identifier='subnet-057fa0918fEXAMPLE')
To create an Auto Scaling group
This example creates an Auto Scaling group.

>>> client.create_auto_scaling_group(auto_scaling_group_name='my-auto-scaling-group', launch_template={'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, min_size=1, max_size=3, max_instance_lifetime=2592000, default_instance_warmup=120, vpc_zone_identifier='subnet-057fa0918fEXAMPLE')

Source code in docs_src/capo_auto_scaling/_services/auto_scaling.py

def create_auto_scaling_group(
    self,
    *,
    config_overrides: Optional[AutoScalingClientConfig] = None,
    auto_scaling_group_name: Optional[
        "capo_auto_scaling.types.xml_string_max_len255.XmlStringMaxLen255"
    ] = None,
    launch_configuration_name: Optional[
        "capo_auto_scaling.types.xml_string_max_len255.XmlStringMaxLen255"
    ] = None,
    launch_template: Optional[
        "capo_auto_scaling.types.launch_template_specification.LaunchTemplateSpecification"
    ] = None,
    mixed_instances_policy: Optional[
        "capo_auto_scaling.types.mixed_instances_policy.MixedInstancesPolicy"
    ] = None,
    instance_id: Optional[
        "capo_auto_scaling.types.xml_string_max_len19.XmlStringMaxLen19"
    ] = None,
    min_size: Optional[
        "capo_auto_scaling.types.auto_scaling_group_min_size.AutoScalingGroupMinSize"
    ] = None,
    max_size: Optional[
        "capo_auto_scaling.types.auto_scaling_group_max_size.AutoScalingGroupMaxSize"
    ] = None,
    desired_capacity: Optional[
        "capo_auto_scaling.types.auto_scaling_group_desired_capacity.AutoScalingGroupDesiredCapacity"
    ] = None,
    default_cooldown: Optional["capo_auto_scaling.types.cooldown.Cooldown"] = None,
    availability_zones: Optional[
        "capo_auto_scaling.types.availability_zones.AvailabilityZones"
    ] = None,
    availability_zone_ids: Optional[
        "capo_auto_scaling.types.availability_zone_ids.AvailabilityZoneIds"
    ] = None,
    load_balancer_names: Optional[
        "capo_auto_scaling.types.load_balancer_names.LoadBalancerNames"
    ] = None,
    target_group_ar_ns: Optional[
        "capo_auto_scaling.types.target_group_ar_ns.TargetGroupARNs"
    ] = None,
    health_check_type: Optional[
        "capo_auto_scaling.types.xml_string_max_len32.XmlStringMaxLen32"
    ] = None,
    health_check_grace_period: Optional[
        "capo_auto_scaling.types.health_check_grace_period.HealthCheckGracePeriod"
    ] = None,
    placement_group: Optional[
        "capo_auto_scaling.types.xml_string_max_len255.XmlStringMaxLen255"
    ] = None,
    vpc_zone_identifier: Optional[
        "capo_auto_scaling.types.xml_string_max_len5000.XmlStringMaxLen5000"
    ] = None,
    termination_policies: Optional[
        "capo_auto_scaling.types.termination_policies.TerminationPolicies"
    ] = None,
    new_instances_protected_from_scale_in: Optional[
        "capo_auto_scaling.types.instance_protected.InstanceProtected"
    ] = None,
    capacity_rebalance: Optional[
        "capo_auto_scaling.types.capacity_rebalance_enabled.CapacityRebalanceEnabled"
    ] = None,
    lifecycle_hook_specification_list: Optional[
        "capo_auto_scaling.types.lifecycle_hook_specifications.LifecycleHookSpecifications"
    ] = None,
    deletion_protection: Optional[
        "capo_auto_scaling.types.deletion_protection.DeletionProtection"
    ] = None,
    tags: Optional["capo_auto_scaling.types.tags.Tags"] = None,
    service_linked_role_arn: Optional[
        "capo_auto_scaling.types.resource_name.ResourceName"
    ] = None,
    max_instance_lifetime: Optional[
        "capo_auto_scaling.types.max_instance_lifetime.MaxInstanceLifetime"
    ] = None,
    context: Optional["capo_auto_scaling.types.context.Context"] = None,
    desired_capacity_type: Optional[
        "capo_auto_scaling.types.xml_string_max_len255.XmlStringMaxLen255"
    ] = None,
    default_instance_warmup: Optional[
        "capo_auto_scaling.types.default_instance_warmup.DefaultInstanceWarmup"
    ] = None,
    traffic_sources: Optional[
        "capo_auto_scaling.types.traffic_sources.TrafficSources"
    ] = None,
    instance_maintenance_policy: Optional[
        "capo_auto_scaling.types.instance_maintenance_policy.InstanceMaintenancePolicy"
    ] = None,
    availability_zone_distribution: Optional[
        "capo_auto_scaling.types.availability_zone_distribution.AvailabilityZoneDistribution"
    ] = None,
    availability_zone_impairment_policy: Optional[
        "capo_auto_scaling.types.availability_zone_impairment_policy.AvailabilityZoneImpairmentPolicy"
    ] = None,
    skip_zonal_shift_validation: Optional[
        "capo_auto_scaling.types.skip_zonal_shift_validation.SkipZonalShiftValidation"
    ] = None,
    capacity_reservation_specification: Optional[
        "capo_auto_scaling.types.capacity_reservation_specification.CapacityReservationSpecification"
    ] = None,
    instance_lifecycle_policy: Optional[
        "capo_auto_scaling.types.instance_lifecycle_policy.InstanceLifecyclePolicy"
    ] = None,
    operator: Optional["capo_auto_scaling.types.operator.Operator"] = None,
) -> None:
    """<p> <b>We strongly recommend using a launch template when calling this operation to ensure full functionality for Amazon EC2 Auto Scaling and Amazon EC2.</b> </p> <p>Creates an Auto Scaling group with the specified name and attributes. </p> <p>If you exceed your maximum limit of Auto Scaling groups, the call fails. To query this limit, call the <a href="https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_DescribeAccountLimits.html">DescribeAccountLimits</a> API. For information about updating this limit, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-quotas.html">Quotas for Amazon EC2 Auto Scaling</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>If you're new to Amazon EC2 Auto Scaling, see the introductory tutorials in <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/get-started-with-ec2-auto-scaling.html">Get started with Amazon EC2 Auto Scaling</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>Every Auto Scaling group has three size properties (<code>DesiredCapacity</code>, <code>MaxSize</code>, and <code>MinSize</code>). Usually, you set these sizes based on a specific number of instances. However, if you configure a mixed instances policy that defines weights for the instance types, you must specify these sizes with the same units that you use for weighting instances.</p>

    Args:
        auto_scaling_group_name: <p>The name of the Auto Scaling group. This name must be unique per Region per account.</p> <p>The name can contain any ASCII character 33 to 126 including most punctuation characters, digits, and upper and lowercased letters.</p> <note> <p>You cannot use a colon (:) in the name.</p> </note>
        launch_configuration_name: <p>The name of the launch configuration to use to launch instances. </p> <p>Conditional: You must specify either a launch template (<code>LaunchTemplate</code> or <code>MixedInstancesPolicy</code>) or a launch configuration (<code>LaunchConfigurationName</code> or <code>InstanceId</code>).</p>
        launch_template: <p>Information used to specify the launch template and version to use to launch instances. </p> <p>Conditional: You must specify either a launch template (<code>LaunchTemplate</code> or <code>MixedInstancesPolicy</code>) or a launch configuration (<code>LaunchConfigurationName</code> or <code>InstanceId</code>).</p> <note> <p>The launch template that is specified must be configured for use with an Auto Scaling group. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html">Create a launch template for an Auto Scaling group</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> </note>
        mixed_instances_policy: <p>The mixed instances policy. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-mixed-instances-groups.html">Auto Scaling groups with multiple instance types and purchase options</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>. To learn how to prioritize multiple capacity types, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/use-distribution-segments.html">Use Distribution Segments to target multiple capacity types</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        instance_id: <p>The ID of the instance used to base the launch configuration on. If specified, Amazon EC2 Auto Scaling uses the configuration values from the specified instance to create a new launch configuration. To get the instance ID, use the Amazon EC2 <a href="https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstances.html">DescribeInstances</a> API operation. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-from-instance.html">Create an Auto Scaling group using parameters from an existing instance</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        min_size: <p>The minimum size of the group.</p>
        max_size: <p>The maximum size of the group.</p> <note> <p>With a mixed instances policy that uses instance weighting, Amazon EC2 Auto Scaling may need to go above <code>MaxSize</code> to meet your capacity requirements. In this event, Amazon EC2 Auto Scaling will never go above <code>MaxSize</code> by more than your largest instance weight (weights that define how many units each instance contributes to the desired capacity of the group).</p> </note>
        desired_capacity: <p>The desired capacity is the initial capacity of the Auto Scaling group at the time of its creation and the capacity it attempts to maintain. It can scale beyond this capacity if you configure auto scaling. This number must be greater than or equal to the minimum size of the group and less than or equal to the maximum size of the group. If you do not specify a desired capacity, the default is the minimum size of the group.</p>
        default_cooldown: <p> <i>Only needed if you use simple scaling policies.</i> </p> <p>The amount of time, in seconds, between one scaling activity ending and another one starting due to simple scaling policies. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-scaling-cooldowns.html">Scaling cooldowns for Amazon EC2 Auto Scaling</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>Default: <code>300</code> seconds</p>
        availability_zones: <p>A list of Availability Zones where instances in the Auto Scaling group can be created. Used for launching into the default VPC subnet in each Availability Zone when not using the <code>VPCZoneIdentifier</code> property, or for attaching a network interface when an existing network interface ID is specified in a launch template.</p>
        availability_zone_ids: <p> A list of Availability Zone IDs where the Auto Scaling group can launch instances. You cannot specify both AvailabilityZones and AvailabilityZoneIds in the same request. </p>
        load_balancer_names: <p>A list of Classic Load Balancers associated with this Auto Scaling group. For Application Load Balancers, Network Load Balancers, and Gateway Load Balancers, specify the <code>TargetGroupARNs</code> property instead.</p>
        target_group_ar_ns: <p>The Amazon Resource Names (ARN) of the Elastic Load Balancing target groups to associate with the Auto Scaling group. Instances are registered as targets with the target groups. The target groups receive incoming traffic and route requests to one or more registered targets. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/autoscaling-load-balancer.html">Use Elastic Load Balancing to distribute traffic across the instances in your Auto Scaling group</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        health_check_type: <p>A comma-separated value string of one or more health check types.</p> <p>The valid values are <code>EC2</code>, <code>EBS</code>, <code>ELB</code>, and <code>VPC_LATTICE</code>. <code>EC2</code> is the default health check and cannot be disabled. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-health-checks.html">Health checks for instances in an Auto Scaling group</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>Only specify <code>EC2</code> if you must clear a value that was previously set.</p>
        health_check_grace_period: <p>The amount of time, in seconds, that Amazon EC2 Auto Scaling waits before checking the health status of an EC2 instance that has come into service and marking it unhealthy due to a failed health check. This is useful if your instances do not immediately pass their health checks after they enter the <code>InService</code> state. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/health-check-grace-period.html">Set the health check grace period for an Auto Scaling group</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>Default: <code>0</code> seconds</p>
        placement_group: <p>The name of the placement group into which to launch your instances. For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html">Placement groups</a> in the <i>Amazon EC2 User Guide</i>.</p> <note> <p>A <i>cluster</i> placement group is a logical grouping of instances within a single Availability Zone. You cannot specify multiple Availability Zones and a cluster placement group. </p> </note>
        vpc_zone_identifier: <p>A comma-separated list of subnet IDs for a virtual private cloud (VPC) where instances in the Auto Scaling group can be created. If you specify <code>VPCZoneIdentifier</code> with <code>AvailabilityZones</code>, the subnets that you specify must reside in those Availability Zones.</p>
        termination_policies: <p>A policy or a list of policies that are used to select the instance to terminate. These policies are executed in the order that you list them. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-termination-policies.html">Configure termination policies for Amazon EC2 Auto Scaling</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>Valid values: <code>Default</code> | <code>AllocationStrategy</code> | <code>ClosestToNextInstanceHour</code> | <code>NewestInstance</code> | <code>OldestInstance</code> | <code>OldestLaunchConfiguration</code> | <code>OldestLaunchTemplate</code> | <code>arn:aws:lambda:region:account-id:function:my-function:my-alias</code> </p>
        new_instances_protected_from_scale_in: <p>Indicates whether newly launched instances are protected from termination by Amazon EC2 Auto Scaling when scaling in. For more information about preventing instances from terminating on scale in, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html">Use instance scale-in protection</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        capacity_rebalance: <p>Indicates whether Capacity Rebalancing is enabled. Otherwise, Capacity Rebalancing is disabled. 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. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-capacity-rebalancing.html">Use Capacity Rebalancing to handle Amazon EC2 Spot Interruptions</a> in the in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        lifecycle_hook_specification_list: <p>One or more lifecycle hooks to add to the Auto Scaling group before instances are launched.</p>
        deletion_protection: <p> The deletion protection setting for the Auto Scaling group. This setting helps safeguard your Auto Scaling group and its instances by controlling whether the <code>DeleteAutoScalingGroup</code> operation is allowed. When deletion protection is enabled, users cannot delete the Auto Scaling group according to the specified protection level until the setting is changed back to a less restrictive level. </p> <p> The valid values are <code>none</code>, <code>prevent-force-deletion</code>, and <code>prevent-all-deletion</code>. </p> <p> Default: <code>none</code> </p> <p> For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/resource-deletion-protection.html"> Configure deletion protection for your Amazon EC2 Auto Scaling resources</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>. </p>
        tags: <p>One or more tags. You can tag your Auto Scaling group and propagate the tags to the Amazon EC2 instances it launches. Tags are not propagated to Amazon EBS volumes. To add tags to Amazon EBS volumes, specify the tags in a launch template but use caution. If the launch template specifies an instance tag with a key that is also specified for the Auto Scaling group, Amazon EC2 Auto Scaling overrides the value of that instance tag with the value specified by the Auto Scaling group. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-tagging.html">Tag Auto Scaling groups and instances</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        service_linked_role_arn: <p>The Amazon Resource Name (ARN) of the service-linked role that the Auto Scaling group uses to call other Amazon Web Services service on your behalf. By default, Amazon EC2 Auto Scaling uses a service-linked role named <code>AWSServiceRoleForAutoScaling</code>, which it creates if it does not exist. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/autoscaling-service-linked-role.html">Service-linked roles</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        max_instance_lifetime: <p>The maximum amount of time, in seconds, that an instance can be in service. The default is null. If specified, the value must be either 0 or a number equal to or greater than 86,400 seconds (1 day). For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-max-instance-lifetime.html">Replace Auto Scaling instances based on maximum instance lifetime</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        context: <p>Reserved.</p>
        desired_capacity_type: <p>The unit of measurement for the value specified for desired capacity. Amazon EC2 Auto Scaling supports <code>DesiredCapacityType</code> for attribute-based instance type selection only. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-mixed-instances-group-attribute-based-instance-type-selection.html">Create a mixed instances group using attribute-based instance type selection</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <p>By default, Amazon EC2 Auto Scaling specifies <code>units</code>, which translates into number of instances.</p> <p>Valid values: <code>units</code> | <code>vcpu</code> | <code>memory-mib</code> </p>
        default_instance_warmup: <p>The amount of time, in seconds, until a new instance is considered to have finished initializing and resource consumption to become stable after it enters the <code>InService</code> state. </p> <p>During an instance refresh, Amazon EC2 Auto Scaling waits for the warm-up period after it replaces an instance before it moves on to replacing the next instance. Amazon EC2 Auto Scaling also waits for the warm-up period before aggregating the metrics for new instances with existing instances in the Amazon CloudWatch metrics that are used for scaling, resulting in more reliable usage data. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-default-instance-warmup.html">Set the default instance warmup for an Auto Scaling group</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p> <important> <p>To manage various warm-up settings at the group level, we recommend that you set the default instance warmup, <i>even if it is set to 0 seconds</i>. To remove a value that you previously set, include the property but specify <code>-1</code> for the value. However, we strongly recommend keeping the default instance warmup enabled by specifying a value of <code>0</code> or other nominal value.</p> </important> <p>Default: None </p>
        traffic_sources: <p>The list of traffic sources to attach to this Auto Scaling group. You can use any of the following as traffic sources for an Auto Scaling group: Classic Load Balancer, Application Load Balancer, Gateway Load Balancer, Network Load Balancer, and VPC Lattice.</p>
        instance_maintenance_policy: <p>An instance maintenance policy. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-maintenance-policy.html">Set instance maintenance policy</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>.</p>
        availability_zone_distribution: <p>The instance capacity distribution across Availability Zones.</p>
        availability_zone_impairment_policy: <p> The policy for Availability Zone impairment. </p>
        skip_zonal_shift_validation: <p> If you enable zonal shift with cross-zone disabled load balancers, capacity could become imbalanced across Availability Zones. To skip the validation, specify <code>true</code>. For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-zonal-shift.html">Auto Scaling group zonal shift</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>. </p>
        capacity_reservation_specification: <p> The capacity reservation specification for the Auto Scaling group. </p>
        instance_lifecycle_policy: <p> The instance lifecycle policy for the Auto Scaling group. This policy controls instance behavior when an instance transitions through its lifecycle states. Configure retention triggers to specify when instances should move to a <code>Retained</code> state instead of automatic termination. </p> <p>For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/instance-lifecycle-policy.html"> Control instance retention with instance lifecycle policies</a> in the <i>Amazon EC2 Auto Scaling User Guide</i>. </p> <note> <p>Instances in a Retained state will continue to incur standard EC2 charges until terminated.</p> </note>
        operator: <p>The entity that manages the Auto Scaling group. If you specify this parameter, Amazon EC2 Auto Scaling passes the operator identity to EC2 for instance launches and only allows the designated operator to make changes to the Auto Scaling group. All mutating API calls from non-operator callers are rejected with an <code>AccessDenied</code> exception.</p>

    Raises:
        capo_auto_scaling.errors.already_exists_fault.AlreadyExistsFault: <p>You already have an Auto Scaling group or launch configuration with this name.</p>
        capo_auto_scaling.errors.limit_exceeded_fault.LimitExceededFault: <p>You have already reached a limit for your Amazon EC2 Auto Scaling resources (for example, Auto Scaling groups, launch configurations, or lifecycle hooks). For more information, see <a href="https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_DescribeAccountLimits.html">DescribeAccountLimits</a> in the <i>Amazon EC2 Auto Scaling API Reference</i>.</p>
        capo_auto_scaling.errors.resource_contention_fault.ResourceContentionFault: <p>You already have a pending update to an Amazon EC2 Auto Scaling resource (for example, an Auto Scaling group, instance, or load balancer).</p>
        capo_auto_scaling.errors.service_linked_role_failure.ServiceLinkedRoleFailure: <p>The service-linked role is not yet ready for use.</p>
        capo_auto_scaling.errors.UnknownServiceError: The service returned an error code this client does not model.

    Examples:
        To create an Auto Scaling group with an attached target group
        This example creates an Auto Scaling group and attaches the specified target group.

        >>> client.create_auto_scaling_group(auto_scaling_group_name='my-auto-scaling-group', launch_template={'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, min_size=1, max_size=3, target_group_ar_ns=['arn:aws:elasticloadbalancing:us-west-2:123456789012:targetgroup/my-targets/73e2d6bc24d8a067'], health_check_type='ELB', health_check_grace_period=300, vpc_zone_identifier='subnet-057fa0918fEXAMPLE, subnet-610acd08EXAMPLE')
        To create an Auto Scaling group with a mixed instances policy
        This example creates an Auto Scaling group with a mixed instances policy. It specifies the c5.large, c5a.large, and c6g.large instance types and defines a different launch template for the c6g.large instance type.

        >>> client.create_auto_scaling_group(auto_scaling_group_name='my-asg', mixed_instances_policy={'LaunchTemplate': {'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-launch-template-for-x86', 'Version': '$Default'}, 'Overrides': [{'InstanceType': 'c6g.large', 'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-launch-template-for-arm', 'Version': '$Default'}}, {'InstanceType': 'c5.large'}, {'InstanceType': 'c5a.large'}]}, 'InstancesDistribution': {'OnDemandBaseCapacity': 1, 'OnDemandPercentageAboveBaseCapacity': 50, 'SpotAllocationStrategy': 'price-capacity-optimized'}}, min_size=1, max_size=5, desired_capacity=3, vpc_zone_identifier='subnet-057fa0918fEXAMPLE, subnet-610acd08EXAMPLE')
        To create an Auto Scaling group using attribute-based instance type selection
        This example creates an Auto Scaling group using attribute-based instance type selection. It requires the instance types to have a minimum of four vCPUs and a maximum of eight vCPUs, a minimum of 16,384 MiB of memory, and an Intel manufactured CPU.

        >>> client.create_auto_scaling_group(auto_scaling_group_name='my-asg', mixed_instances_policy={'LaunchTemplate': {'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, 'Overrides': [{'InstanceRequirements': {'VCpuCount': {'Min': 4, 'Max': 8}, 'MemoryMiB': {'Min': 16384}, 'CpuManufacturers': ['intel']}}]}, 'InstancesDistribution': {'OnDemandPercentageAboveBaseCapacity': 50, 'SpotAllocationStrategy': 'price-capacity-optimized'}}, min_size=0, max_size=100, desired_capacity=4, desired_capacity_type='units', vpc_zone_identifier='subnet-057fa0918fEXAMPLE, subnet-610acd08EXAMPLE')
        To create an Auto Scaling group using Distribution Segments
        This example creates an Auto Scaling group that uses Distribution Segments to prioritize On-Demand Capacity Reservations, Capacity Blocks, interruptible Capacity Reservations, and then On-Demand capacity.

        >>> client.create_auto_scaling_group(auto_scaling_group_name='my-asg', mixed_instances_policy={'LaunchTemplate': {'LaunchTemplateSpecification': {'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, 'Overrides': [{'InstanceType': 'm5.24xlarge'}, {'InstanceType': 'p5.48xlarge'}]}, 'InstancesDistribution': {'OnDemandAllocationStrategy': 'prioritized', 'DistributionSegments': [{'TargetCapacityTypes': ['on-demand-capacity-reservation', 'capacity-block', 'interruptible-capacity-reservation', 'on-demand']}]}}, capacity_reservation_specification={'CapacityReservationTarget': {'CapacityReservationResourceGroupArns': ['arn:aws:resource-groups:us-east-1:123456789012:group/my-capacity-reservation-group']}}, min_size=0, max_size=10, desired_capacity=5, vpc_zone_identifier='subnet-057fa0918fEXAMPLE')
        To create an Auto Scaling group
        This example creates an Auto Scaling group.

        >>> client.create_auto_scaling_group(auto_scaling_group_name='my-auto-scaling-group', launch_template={'LaunchTemplateName': 'my-template-for-auto-scaling', 'Version': '$Default'}, min_size=1, max_size=3, max_instance_lifetime=2592000, default_instance_warmup=120, vpc_zone_identifier='subnet-057fa0918fEXAMPLE')
    """

    def _handler(
        req: "OperationRequest[capo_auto_scaling.types.create_auto_scaling_group_type.CreateAutoScalingGroupType]",
    ) -> OperationResponse[None]:
        import capo_auto_scaling._operations.auto_scaling_2011_01_01.create_auto_scaling_group

        output, http_response = (
            capo_auto_scaling._operations.auto_scaling_2011_01_01.create_auto_scaling_group.create_auto_scaling_group(
                req.options, req.input
            )
        )
        return OperationResponse(output=output, response=http_response)

    interceptors_, options_ = self.operation_options(
        config_overrides, OperationLogging("CreateAutoScalingGroup")
    )
    input_: capo_auto_scaling.types.create_auto_scaling_group_type.CreateAutoScalingGroupType = {}
    if auto_scaling_group_name is not None:
        input_["auto_scaling_group_name"] = auto_scaling_group_name
    if launch_configuration_name is not None:
        input_["launch_configuration_name"] = launch_configuration_name
    if launch_template is not None:
        input_["launch_template"] = launch_template
    if mixed_instances_policy is not None:
        input_["mixed_instances_policy"] = mixed_instances_policy
    if instance_id is not None:
        input_["instance_id"] = instance_id
    if min_size is not None:
        input_["min_size"] = min_size
    if max_size is not None:
        input_["max_size"] = max_size
    if desired_capacity is not None:
        input_["desired_capacity"] = desired_capacity
    if default_cooldown is not None:
        input_["default_cooldown"] = default_cooldown
    if availability_zones is not None:
        input_["availability_zones"] = availability_zones
    if availability_zone_ids is not None:
        input_["availability_zone_ids"] = availability_zone_ids
    if load_balancer_names is not None:
        input_["load_balancer_names"] = load_balancer_names
    if target_group_ar_ns is not None:
        input_["target_group_ar_ns"] = target_group_ar_ns
    if health_check_type is not None:
        input_["health_check_type"] = health_check_type
    if health_check_grace_period is not None:
        input_["health_check_grace_period"] = health_check_grace_period
    if placement_group is not None:
        input_["placement_group"] = placement_group
    if vpc_zone_identifier is not None:
        input_["vpc_zone_identifier"] = vpc_zone_identifier
    if termination_policies is not None:
        input_["termination_policies"] = termination_policies
    if new_instances_protected_from_scale_in is not None:
        input_["new_instances_protected_from_scale_in"] = (
            new_instances_protected_from_scale_in
        )
    if capacity_rebalance is not None:
        input_["capacity_rebalance"] = capacity_rebalance
    if lifecycle_hook_specification_list is not None:
        input_["lifecycle_hook_specification_list"] = (
            lifecycle_hook_specification_list
        )
    if deletion_protection is not None:
        input_["deletion_protection"] = deletion_protection
    if tags is not None:
        input_["tags"] = tags
    if service_linked_role_arn is not None:
        input_["service_linked_role_arn"] = service_linked_role_arn
    if max_instance_lifetime is not None:
        input_["max_instance_lifetime"] = max_instance_lifetime
    if context is not None:
        input_["context"] = context
    if desired_capacity_type is not None:
        input_["desired_capacity_type"] = desired_capacity_type
    if default_instance_warmup is not None:
        input_["default_instance_warmup"] = default_instance_warmup
    if traffic_sources is not None:
        input_["traffic_sources"] = traffic_sources
    if instance_maintenance_policy is not None:
        input_["instance_maintenance_policy"] = instance_maintenance_policy
    if availability_zone_distribution is not None:
        input_["availability_zone_distribution"] = availability_zone_distribution
    if availability_zone_impairment_policy is not None:
        input_["availability_zone_impairment_policy"] = (
            availability_zone_impairment_policy
        )
    if skip_zonal_shift_validation is not None:
        input_["skip_zonal_shift_validation"] = skip_zonal_shift_validation
    if capacity_reservation_specification is not None:
        input_["capacity_reservation_specification"] = (
            capacity_reservation_specification
        )
    if instance_lifecycle_policy is not None:
        input_["instance_lifecycle_policy"] = instance_lifecycle_policy
    if operator is not None:
        input_["operator"] = operator

    response = execute_pipeline(
        OperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    response.response.close()
    return response.output