aws_sdk_computeoptimizer/lib.rs
1#![allow(deprecated)]
2#![allow(unknown_lints)]
3#![allow(clippy::module_inception)]
4#![allow(clippy::upper_case_acronyms)]
5#![allow(clippy::large_enum_variant)]
6#![allow(clippy::wrong_self_convention)]
7#![allow(clippy::should_implement_trait)]
8#![allow(clippy::disallowed_names)]
9#![allow(clippy::vec_init_then_push)]
10#![allow(clippy::type_complexity)]
11#![allow(clippy::needless_return)]
12#![allow(clippy::derive_partial_eq_without_eq)]
13#![allow(clippy::result_large_err)]
14#![allow(clippy::unnecessary_map_on_constructor)]
15#![allow(rustdoc::bare_urls)]
16#![allow(rustdoc::redundant_explicit_links)]
17#![forbid(unsafe_code)]
18#![warn(missing_docs)]
19#![cfg_attr(docsrs, feature(doc_auto_cfg))]
20//! Compute Optimizer is a service that analyzes the configuration and utilization metrics of your Amazon Web Services compute resources, such as Amazon EC2 instances, Amazon EC2 Auto Scaling groups, Lambda functions, Amazon EBS volumes, and Amazon ECS services on Fargate. It reports whether your resources are optimal, and generates optimization recommendations to reduce the cost and improve the performance of your workloads. Compute Optimizer also provides recent utilization metric data, in addition to projected utilization metric data for the recommendations, which you can use to evaluate which recommendation provides the best price-performance trade-off. The analysis of your usage patterns can help you decide when to move or resize your running resources, and still meet your performance and capacity requirements. For more information about Compute Optimizer, including the required permissions to use the service, see the [Compute Optimizer User Guide](https://docs.aws.amazon.com/compute-optimizer/latest/ug/).
21//!
22//! ## Getting Started
23//!
24//! > Examples are available for many services and operations, check out the
25//! > [examples folder in GitHub](https://github.com/awslabs/aws-sdk-rust/tree/main/examples).
26//!
27//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
28//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-computeoptimizer` to
29//! your project, add the following to your **Cargo.toml** file:
30//!
31//! ```toml
32//! [dependencies]
33//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
34//! aws-sdk-computeoptimizer = "1.70.0"
35//! tokio = { version = "1", features = ["full"] }
36//! ```
37//!
38//! Then in code, a client can be created with the following:
39//!
40//! ```rust,no_run
41//! use aws_sdk_computeoptimizer as computeoptimizer;
42//!
43//! #[::tokio::main]
44//! async fn main() -> Result<(), computeoptimizer::Error> {
45//! let config = aws_config::load_from_env().await;
46//! let client = aws_sdk_computeoptimizer::Client::new(&config);
47//!
48//! // ... make some calls with the client
49//!
50//! Ok(())
51//! }
52//! ```
53//!
54//! See the [client documentation](https://docs.rs/aws-sdk-computeoptimizer/latest/aws_sdk_computeoptimizer/client/struct.Client.html)
55//! for information on what calls can be made, and the inputs and outputs for each of those calls.
56//!
57//! ## Using the SDK
58//!
59//! Until the SDK is released, we will be adding information about using the SDK to the
60//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
61//! additional sections for the guide by opening an issue and describing what you are trying to do.
62//!
63//! ## Getting Help
64//!
65//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
66//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
67//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
68//! * [Usage examples](https://github.com/awslabs/aws-sdk-rust/tree/main/examples)
69//!
70//!
71//! # Crate Organization
72//!
73//! The entry point for most customers will be [`Client`], which exposes one method for each API
74//! offered by AWS Compute Optimizer. The return value of each of these methods is a "fluent builder",
75//! where the different inputs for that API are added by builder-style function call chaining,
76//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
77//! either a successful output or a [`SdkError`](crate::error::SdkError).
78//!
79//! Some of these API inputs may be structs or enums to provide more complex structured information.
80//! These structs and enums live in [`types`](crate::types). There are some simpler types for
81//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
82//!
83//! All types required to configure a client via the [`Config`](crate::Config) struct live
84//! in [`config`](crate::config).
85//!
86//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
87//! is the input, output, and error type for that API, as well as builders to construct each of those.
88//!
89//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
90//! client can return. Any other error type can be converted to this `Error` type via the
91//! [`From`](std::convert::From) trait.
92//!
93//! The other modules within this crate are not required for normal usage.
94
95// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
96pub use error_meta::Error;
97
98#[doc(inline)]
99pub use config::Config;
100
101/// Client for calling AWS Compute Optimizer.
102/// ## Constructing a `Client`
103///
104/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
105/// crate should be used to automatically resolve this config using
106/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
107/// across multiple different AWS SDK clients. This config resolution process can be customized
108/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
109/// the [builder pattern] to customize the default config.
110///
111/// In the simplest case, creating a client looks as follows:
112/// ```rust,no_run
113/// # async fn wrapper() {
114/// let config = aws_config::load_from_env().await;
115/// let client = aws_sdk_computeoptimizer::Client::new(&config);
116/// # }
117/// ```
118///
119/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
120/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
121/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
122/// done as follows:
123///
124/// ```rust,no_run
125/// # async fn wrapper() {
126/// let sdk_config = ::aws_config::load_from_env().await;
127/// let config = aws_sdk_computeoptimizer::config::Builder::from(&sdk_config)
128/// # /*
129/// .some_service_specific_setting("value")
130/// # */
131/// .build();
132/// # }
133/// ```
134///
135/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
136///
137/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
138/// be done once at application start-up.
139///
140/// [`Config`]: crate::Config
141/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
142/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
143/// [`aws-config` docs]: https://docs.rs/aws-config/*
144/// [`aws-config`]: https://crates.io/crates/aws-config
145/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
146/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
147/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
148/// # Using the `Client`
149///
150/// A client has a function for every operation that can be performed by the service.
151/// For example, the [`DeleteRecommendationPreferences`](crate::operation::delete_recommendation_preferences) operation has
152/// a [`Client::delete_recommendation_preferences`], function which returns a builder for that operation.
153/// The fluent builder ultimately has a `send()` function that returns an async future that
154/// returns a result, as illustrated below:
155///
156/// ```rust,ignore
157/// let result = client.delete_recommendation_preferences()
158/// .resource_type("example")
159/// .send()
160/// .await;
161/// ```
162///
163/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
164/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
165/// information.
166pub mod client;
167
168/// Configuration for AWS Compute Optimizer.
169pub mod config;
170
171/// Common errors and error handling utilities.
172pub mod error;
173
174mod error_meta;
175
176/// Information about this crate.
177pub mod meta;
178
179/// All operations that this crate can perform.
180pub mod operation;
181
182/// Primitives such as `Blob` or `DateTime` used by other types.
183pub mod primitives;
184
185/// Data structures used by operation inputs/outputs.
186pub mod types;
187
188mod auth_plugin;
189
190pub(crate) mod protocol_serde;
191
192mod sdk_feature_tracker;
193
194mod serialization_settings;
195
196mod endpoint_lib;
197
198mod lens;
199
200mod serde_util;
201
202mod json_errors;
203
204#[doc(inline)]
205pub use client::Client;