aws_sdk_s3/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#![allow(rustdoc::invalid_html_tags)]
18#![forbid(unsafe_code)]
19#![warn(missing_docs)]
20#![cfg_attr(docsrs, feature(doc_auto_cfg))]
21//! ## Getting Started
22//!
23//! > Examples are available for many services and operations, check out the
24//! > [examples folder in GitHub](https://github.com/awslabs/aws-sdk-rust/tree/main/examples).
25//!
26//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
27//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-s3` to
28//! your project, add the following to your **Cargo.toml** file:
29//!
30//! ```toml
31//! [dependencies]
32//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
33//! aws-sdk-s3 = "1.100.0"
34//! tokio = { version = "1", features = ["full"] }
35//! ```
36//!
37//! Then in code, a client can be created with the following:
38//!
39//! ```rust,no_run
40//! use aws_sdk_s3 as s3;
41//!
42//! #[::tokio::main]
43//! async fn main() -> Result<(), s3::Error> {
44//! let config = aws_config::load_from_env().await;
45//! let client = aws_sdk_s3::Client::new(&config);
46//!
47//! // ... make some calls with the client
48//!
49//! Ok(())
50//! }
51//! ```
52//!
53//! See the [client documentation](https://docs.rs/aws-sdk-s3/latest/aws_sdk_s3/client/struct.Client.html)
54//! for information on what calls can be made, and the inputs and outputs for each of those calls.
55//!
56//! ## Using the SDK
57//!
58//! Until the SDK is released, we will be adding information about using the SDK to the
59//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
60//! additional sections for the guide by opening an issue and describing what you are trying to do.
61//!
62//! ## Getting Help
63//!
64//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
65//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
66//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
67//! * [Usage examples](https://github.com/awslabs/aws-sdk-rust/tree/main/examples)
68//!
69//!
70//! # Crate Organization
71//!
72//! The entry point for most customers will be [`Client`], which exposes one method for each API
73//! offered by Amazon Simple Storage Service. The return value of each of these methods is a "fluent builder",
74//! where the different inputs for that API are added by builder-style function call chaining,
75//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
76//! either a successful output or a [`SdkError`](crate::error::SdkError).
77//!
78//! Some of these API inputs may be structs or enums to provide more complex structured information.
79//! These structs and enums live in [`types`](crate::types). There are some simpler types for
80//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
81//!
82//! All types required to configure a client via the [`Config`](crate::Config) struct live
83//! in [`config`](crate::config).
84//!
85//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
86//! is the input, output, and error type for that API, as well as builders to construct each of those.
87//!
88//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
89//! client can return. Any other error type can be converted to this `Error` type via the
90//! [`From`](std::convert::From) trait.
91//!
92//! The other modules within this crate are not required for normal usage.
93
94// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
95pub use error_meta::Error;
96
97#[doc(inline)]
98pub use config::Config;
99
100/// Client for calling Amazon Simple Storage Service.
101/// ## Constructing a `Client`
102///
103/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
104/// crate should be used to automatically resolve this config using
105/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
106/// across multiple different AWS SDK clients. This config resolution process can be customized
107/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
108/// the [builder pattern] to customize the default config.
109///
110/// In the simplest case, creating a client looks as follows:
111/// ```rust,no_run
112/// # async fn wrapper() {
113/// let config = aws_config::load_from_env().await;
114/// let client = aws_sdk_s3::Client::new(&config);
115/// # }
116/// ```
117///
118/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
119/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
120/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
121/// done as follows:
122///
123/// ```rust,no_run
124/// # async fn wrapper() {
125/// let sdk_config = ::aws_config::load_from_env().await;
126/// let config = aws_sdk_s3::config::Builder::from(&sdk_config)
127/// # /*
128/// .some_service_specific_setting("value")
129/// # */
130/// .build();
131/// # }
132/// ```
133///
134/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
135///
136/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
137/// be done once at application start-up.
138///
139/// [`Config`]: crate::Config
140/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
141/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
142/// [`aws-config` docs]: https://docs.rs/aws-config/*
143/// [`aws-config`]: https://crates.io/crates/aws-config
144/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
145/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
146/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
147/// # Using the `Client`
148///
149/// A client has a function for every operation that can be performed by the service.
150/// For example, the [`AbortMultipartUpload`](crate::operation::abort_multipart_upload) operation has
151/// a [`Client::abort_multipart_upload`], function which returns a builder for that operation.
152/// The fluent builder ultimately has a `send()` function that returns an async future that
153/// returns a result, as illustrated below:
154///
155/// ```rust,ignore
156/// let result = client.abort_multipart_upload()
157/// .bucket("example")
158/// .send()
159/// .await;
160/// ```
161///
162/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
163/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
164/// information.
165/// # Waiters
166///
167/// This client provides `wait_until` methods behind the [`Waiters`](crate::client::Waiters) trait.
168/// To use them, simply import the trait, and then call one of the `wait_until` methods. This will
169/// return a waiter fluent builder that takes various parameters, which are documented on the builder
170/// type. Once parameters have been provided, the `wait` method can be called to initiate waiting.
171///
172/// For example, if there was a `wait_until_thing` method, it could look like:
173/// ```rust,ignore
174/// let result = client.wait_until_thing()
175/// .thing_id("someId")
176/// .wait(Duration::from_secs(120))
177/// .await;
178/// ```
179pub mod client;
180
181/// Configuration for Amazon Simple Storage Service.
182pub mod config;
183
184/// Common errors and error handling utilities.
185pub mod error;
186
187mod error_meta;
188
189/// Information about this crate.
190pub mod meta;
191
192/// All operations that this crate can perform.
193pub mod operation;
194
195/// Primitives such as `Blob` or `DateTime` used by other types.
196pub mod primitives;
197
198/// Data structures used by operation inputs/outputs.
199pub mod types;
200
201pub(crate) mod client_idempotency_token;
202
203mod event_receiver;
204
205pub(crate) mod http_request_checksum;
206
207pub(crate) mod http_response_checksum;
208
209mod idempotency_token;
210
211pub mod presigning;
212
213pub(crate) mod presigning_interceptors;
214
215pub(crate) mod protocol_serde;
216
217mod rest_xml_unwrapped_errors;
218
219mod s3_expires_interceptor;
220
221mod s3_express;
222
223mod s3_request_id;
224
225mod sdk_feature_tracker;
226
227mod serialization_settings;
228
229pub(crate) mod endpoint_auth;
230
231mod endpoint_lib;
232
233mod lens;
234
235mod serde_util;
236
237/// Supporting types for waiters.
238///
239/// Note: to use waiters, import the [`Waiters`](crate::client::Waiters) trait, which adds methods prefixed with `wait_until` to the client.
240pub mod waiters;
241
242mod event_stream_serde;
243
244#[doc(inline)]
245pub use client::Client;