pulumi-alicloud-kotlin/com.pulumi.alicloud.ess.kotlin/ScalingConfigurationArgsBuilder/spotPriceLimits

spotPriceLimits

@JvmName(name = "msilmbbobxhvflud")
suspend fun spotPriceLimits(value: Output<List<ScalingConfigurationSpotPriceLimitArgs>>)
@JvmName(name = "hfbvrwyolnepregt")
suspend fun spotPriceLimits(value: List<ScalingConfigurationSpotPriceLimitArgs>?)

Parameters

value

Sets the maximum price hourly for instance types. See spot_price_limit below for details.

NOTE: Before enabling the scaling group, it must have a active scaling configuration. NOTE: If the number of attached ECS instances by instance_ids is smaller than MinSize, the Auto Scaling Service will automatically create ECS Pay-As-You-Go instance to cater to MinSize. For example, MinSize=5 and 2 existing ECS instances has been attached to the scaling group. When the scaling group is enabled, it will create 3 instnaces automatically based on its current active scaling configuration. NOTE: Restrictions on attaching ECS instances:

  • The attached ECS instances and the scaling group must have the same region and network type(Classic or VPC).

  • The attached ECS instances and the instance with active scaling configurations must have the same instance type.

  • The attached ECS instances must in the running state.

  • The attached ECS instances has not been attached to other scaling groups.

  • The attached ECS instances supports Subscription and Pay-As-You-Go payment methods.

NOTE: The last scaling configuration can't be set to inactive and deleted alone.

@JvmName(name = "qybijcdvuvtwqrgd")
suspend fun spotPriceLimits(vararg values: Output<ScalingConfigurationSpotPriceLimitArgs>)

@JvmName(name = "avqyqelwtaumpkjf")
suspend fun spotPriceLimits(values: List<Output<ScalingConfigurationSpotPriceLimitArgs>>)
@JvmName(name = "occxapwsanqnjbcy")
suspend fun spotPriceLimits(vararg values: ScalingConfigurationSpotPriceLimitArgs)

Parameters

values

Sets the maximum price hourly for instance types. See spot_price_limit below for details.

NOTE: Before enabling the scaling group, it must have a active scaling configuration. NOTE: If the number of attached ECS instances by instance_ids is smaller than MinSize, the Auto Scaling Service will automatically create ECS Pay-As-You-Go instance to cater to MinSize. For example, MinSize=5 and 2 existing ECS instances has been attached to the scaling group. When the scaling group is enabled, it will create 3 instnaces automatically based on its current active scaling configuration. NOTE: Restrictions on attaching ECS instances:

  • The attached ECS instances and the scaling group must have the same region and network type(Classic or VPC).

  • The attached ECS instances and the instance with active scaling configurations must have the same instance type.

  • The attached ECS instances must in the running state.

  • The attached ECS instances has not been attached to other scaling groups.

  • The attached ECS instances supports Subscription and Pay-As-You-Go payment methods.

NOTE: The last scaling configuration can't be set to inactive and deleted alone.

@JvmName(name = "oqswpycaikhceipp")
suspend fun spotPriceLimits(argument: List<suspend ScalingConfigurationSpotPriceLimitArgsBuilder.() -> Unit>)
@JvmName(name = "cboupnilrojkrsrq")
suspend fun spotPriceLimits(vararg argument: suspend ScalingConfigurationSpotPriceLimitArgsBuilder.() -> Unit)
@JvmName(name = "gngomsmjbysvvgab")
suspend fun spotPriceLimits(argument: suspend ScalingConfigurationSpotPriceLimitArgsBuilder.() -> Unit)

Parameters

argument

Sets the maximum price hourly for instance types. See spot_price_limit below for details.

NOTE: Before enabling the scaling group, it must have a active scaling configuration. NOTE: If the number of attached ECS instances by instance_ids is smaller than MinSize, the Auto Scaling Service will automatically create ECS Pay-As-You-Go instance to cater to MinSize. For example, MinSize=5 and 2 existing ECS instances has been attached to the scaling group. When the scaling group is enabled, it will create 3 instnaces automatically based on its current active scaling configuration. NOTE: Restrictions on attaching ECS instances:

  • The attached ECS instances and the scaling group must have the same region and network type(Classic or VPC).

  • The attached ECS instances and the instance with active scaling configurations must have the same instance type.

  • The attached ECS instances must in the running state.

  • The attached ECS instances has not been attached to other scaling groups.

  • The attached ECS instances supports Subscription and Pay-As-You-Go payment methods.

NOTE: The last scaling configuration can't be set to inactive and deleted alone.