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