Paws::EC2::SpotFleetRequestConfigData
This class represents one of two things:
Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.
As an example, if Att1 is expected to be a Paws::EC2::SpotFleetRequestConfigData object:
$service_obj->Method(Att1 => { AllocationStrategy => $value, ..., ValidUntil => $value });
Use accessors for each attribute. If Att1 is expected to be an Paws::EC2::SpotFleetRequestConfigData object:
$result = $service_obj->Method(...); $result->Att1->AllocationStrategy
This class has no description
Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the Spot Fleet request.
If the allocation strategy is lowestPrice, Spot Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.
lowestPrice
If the allocation strategy is diversified, Spot Fleet launches instances from all the Spot Instance pools that you specify.
diversified
If the allocation strategy is capacityOptimized, Spot Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching.
capacityOptimized
A unique, case-sensitive identifier that you provide to ensure the idempotency of your listings. This helps to avoid duplicate listings. For more information, see Ensuring Idempotency (https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Run_Instance_Idempotency.html).
Indicates whether running Spot Instances should be terminated if you decrease the target capacity of the Spot Fleet request below the current size of the Spot Fleet.
The number of units fulfilled by this request compared to the set target capacity. You cannot set this value.
The Amazon Resource Name (ARN) of an AWS Identity and Access Management (IAM) role that grants the Spot Fleet the permission to request, launch, terminate, and tag instances on your behalf. For more information, see Spot Fleet Prerequisites (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-requests.html#spot-fleet-prerequisites) in the I<Amazon EC2 User Guide for Linux Instances>. Spot Fleet can terminate Spot Instances on your behalf when you cancel its Spot Fleet request using CancelSpotFleetRequests or when the Spot Fleet request expires, if you set C<TerminateInstancesWithExpiration>.
The behavior when a Spot Instance is interrupted. The default is C<terminate>.
The number of Spot pools across which to allocate your target Spot capacity. Valid only when Spot B<AllocationStrategy> is set to C<lowest-price>. Spot Fleet selects the cheapest Spot pools and evenly allocates your target Spot capacity across the number of Spot pools that you specify.
The launch specifications for the Spot Fleet request. If you specify C<LaunchSpecifications>, you can't specify C<LaunchTemplateConfigs>. If you include On-Demand capacity in your request, you must use C<LaunchTemplateConfigs>.
The launch template and overrides. If you specify C<LaunchTemplateConfigs>, you can't specify C<LaunchSpecifications>. If you include On-Demand capacity in your request, you must use C<LaunchTemplateConfigs>.
One or more Classic Load Balancers and target groups to attach to the Spot Fleet request. Spot Fleet registers the running Spot Instances with the specified Classic Load Balancers and target groups.
With Network Load Balancers, Spot Fleet cannot register instances that have the following instance types: C1, CC1, CC2, CG1, CG2, CR1, CS1, G1, G2, HI1, HS1, M1, M2, M3, and T1.
The order of the launch template overrides to use in fulfilling On-Demand capacity. If you specify C<lowestPrice>, Spot Fleet uses price to determine the order, launching the lowest price first. If you specify C<prioritized>, Spot Fleet uses the priority that you assign to each Spot Fleet launch template override, launching the highest priority first. If you do not specify a value, Spot Fleet defaults to C<lowestPrice>.
The number of On-Demand units fulfilled by this request compared to the set target On-Demand capacity.
The maximum amount per hour for On-Demand Instances that you're willing to pay. You can use the C<onDemandMaxTotalPrice> parameter, the C<spotMaxTotalPrice> parameter, or both parameters to ensure that your fleet cost does not exceed your budget. If you set a maximum price per hour for the On-Demand Instances and Spot Instances in your request, Spot Fleet will launch instances until it reaches the maximum amount you're willing to pay. When the maximum amount you're willing to pay is reached, the fleet stops launching instances even if it hasnE<rsquo>t met the target capacity.
The number of On-Demand units to request. You can choose to set the target capacity in terms of instances or a performance characteristic that is important to your application workload, such as vCPUs, memory, or I/O. If the request type is C<maintain>, you can specify a target capacity of 0 and add capacity later.
Indicates whether Spot Fleet should replace unhealthy instances.
The maximum amount per hour for Spot Instances that you're willing to pay. You can use the C<spotdMaxTotalPrice> parameter, the C<onDemandMaxTotalPrice> parameter, or both parameters to ensure that your fleet cost does not exceed your budget. If you set a maximum price per hour for the On-Demand Instances and Spot Instances in your request, Spot Fleet will launch instances until it reaches the maximum amount you're willing to pay. When the maximum amount you're willing to pay is reached, the fleet stops launching instances even if it hasnE<rsquo>t met the target capacity.
The maximum price per unit hour that you are willing to pay for a Spot Instance. The default is the On-Demand price.
The key-value pair for tagging the Spot Fleet request on creation. The value for C<ResourceType> must be C<spot-fleet-request>, otherwise the Spot Fleet request fails. To tag instances at launch, specify the tags in the launch template (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html#create-launch-template). For information about tagging after launch, see Tagging Your Resources (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html#tag-resources).
The number of units to request for the Spot Fleet. You can choose to set the target capacity in terms of instances or a performance characteristic that is important to your application workload, such as vCPUs, memory, or I/O. If the request type is C<maintain>, you can specify a target capacity of 0 and add capacity later.
Indicates whether running Spot Instances are terminated when the Spot Fleet request expires.
The type of request. Indicates whether the Spot Fleet only requests the target capacity or also attempts to maintain it. When this value is C<request>, the Spot Fleet only places the required requests. It does not attempt to replenish Spot Instances if capacity is diminished, nor does it submit requests in alternative Spot pools if capacity is not available. When this value is C<maintain>, the Spot Fleet maintains the target capacity. The Spot Fleet places the required requests to meet capacity and automatically replenishes any interrupted instances. Default: C<maintain>. C<instant> is listed but is not used by Spot Fleet.
The start date and time of the request, in UTC format (I<YYYY>-I<MM>-I<DD>TI<HH>:I<MM>:I<SS>Z). By default, Amazon EC2 starts fulfilling the request immediately.
The end date and time of the request, in UTC format (I<YYYY>-I<MM>-I<DD>TI<HH>:I<MM>:I<SS>Z). After the end date and time, no new Spot Instance requests are placed or able to fulfill the request. If no value is specified, the Spot Fleet request remains until you cancel it.
This class forms part of Paws, describing an object used in Paws::EC2
The source code is located here: https://github.com/pplu/aws-sdk-perl
Please report bugs to: https://github.com/pplu/aws-sdk-perl/issues
To install Paws::SDK::Config, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Paws::SDK::Config
CPAN shell
perl -MCPAN -e shell install Paws::SDK::Config
For more information on module installation, please visit the detailed CPAN module installation guide.