1 1 | // Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
|
2 - | pub use crate::operation::request_spot_fleet::_request_spot_fleet_output::RequestSpotFleetOutputBuilder;
|
3 - |
|
4 2 | pub use crate::operation::request_spot_fleet::_request_spot_fleet_input::RequestSpotFleetInputBuilder;
|
5 3 |
|
4 + | pub use crate::operation::request_spot_fleet::_request_spot_fleet_output::RequestSpotFleetOutputBuilder;
|
5 + |
|
6 6 | impl crate::operation::request_spot_fleet::builders::RequestSpotFleetInputBuilder {
|
7 7 | /// Sends a request with this input using the given client.
|
8 8 | pub async fn send_with(
|
9 9 | self,
|
10 10 | client: &crate::Client,
|
11 11 | ) -> ::std::result::Result<
|
12 12 | crate::operation::request_spot_fleet::RequestSpotFleetOutput,
|
13 13 | ::aws_smithy_runtime_api::client::result::SdkError<
|
14 14 | crate::operation::request_spot_fleet::RequestSpotFleetError,
|
15 15 | ::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
|
16 16 | >,
|
17 17 | > {
|
18 18 | let mut fluent_builder = client.request_spot_fleet();
|
19 19 | fluent_builder.inner = self;
|
20 20 | fluent_builder.send().await
|
21 21 | }
|
22 22 | }
|
23 23 | /// Fluent builder constructing a request to `RequestSpotFleet`.
|
24 24 | ///
|
25 25 | /// <p>Creates a Spot Fleet request.</p>
|
26 26 | /// <p>The Spot Fleet request specifies the total target capacity and the On-Demand target capacity. Amazon EC2 calculates the difference between the total capacity and On-Demand capacity, and launches the difference as Spot capacity.</p>
|
27 27 | /// <p>You can submit a single request that includes multiple launch specifications that vary by instance type, AMI, Availability Zone, or subnet.</p>
|
28 28 | /// <p>By default, the Spot Fleet requests Spot Instances in the Spot Instance pool where the price per unit is the lowest. Each launch specification can include its own instance weighting that reflects the value of the instance type to your application workload.</p>
|
29 29 | /// <p>Alternatively, you can specify that the Spot Fleet distribute the target capacity across the Spot pools included in its launch specifications. By ensuring that the Spot Instances in your Spot Fleet are in different Spot pools, you can improve the availability of your fleet.</p>
|
30 30 | /// <p>You can specify tags for the Spot Fleet request and instances launched by the fleet. You cannot tag other resource types in a Spot Fleet request because only the <code>spot-fleet-request</code> and <code>instance</code> resource types are supported.</p>
|
31 31 | /// <p>For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet-requests.html">Spot Fleet requests</a> in the <i>Amazon EC2 User Guide</i>.</p><important>
|
32 32 | /// <p>We strongly discourage using the RequestSpotFleet API because it is a legacy API with no planned investment. For options for requesting Spot Instances, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-best-practices.html#which-spot-request-method-to-use">Which is the best Spot request method to use?</a> in the <i>Amazon EC2 User Guide</i>.</p>
|
33 33 | /// </important>
|
34 34 | #[derive(::std::clone::Clone, ::std::fmt::Debug)]
|
35 35 | pub struct RequestSpotFleetFluentBuilder {
|