aws_sdk_storagegateway/
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//! Amazon FSx File Gateway is no longer available to new customers. Existing customers of FSx File Gateway can continue to use the service normally. For capabilities similar to FSx File Gateway, visit [this blog post](https://aws.amazon.com/blogs/storage/switch-your-file-share-access-from-amazon-fsx-file-gateway-to-amazon-fsx-for-windows-file-server/).
22//!
23//! Storage Gateway is the service that connects an on-premises software appliance with cloud-based storage to provide seamless and secure integration between an organization's on-premises IT environment and the Amazon Web Services storage infrastructure. The service enables you to securely upload data to the Amazon Web Services Cloud for cost effective backup and rapid disaster recovery.
24//!
25//! Use the following links to get started using the _Storage Gateway Service API Reference_:
26//!   - [Storage Gateway required request headers](https://docs.aws.amazon.com/storagegateway/latest/userguide/AWSStorageGatewayAPI.html#AWSStorageGatewayHTTPRequestsHeaders): Describes the required headers that you must send with every POST request to Storage Gateway.
27//!   - [Signing requests](https://docs.aws.amazon.com/storagegateway/latest/userguide/AWSStorageGatewayAPI.html#AWSStorageGatewaySigningRequests): Storage Gateway requires that you authenticate every request you send; this topic describes how sign such a request.
28//!   - [Error responses](https://docs.aws.amazon.com/storagegateway/latest/userguide/AWSStorageGatewayAPI.html#APIErrorResponses): Provides reference information about Storage Gateway errors.
29//!   - [Operations in Storage Gateway](https://docs.aws.amazon.com/storagegateway/latest/APIReference/API_Operations.html): Contains detailed descriptions of all Storage Gateway operations, their request parameters, response elements, possible errors, and examples of requests and responses.
30//!   - [Storage Gateway endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/sg.html): Provides a list of each Amazon Web Services Region and the endpoints available for use with Storage Gateway.
31//!
32//! IDs for Storage Gateway volumes and Amazon EBS snapshots created from gateway volumes are changing to a longer format. Starting in December 2016, all new volumes and snapshots will be created with a 17-character string. Starting in April 2016, you will be able to use these longer IDs so you can test your systems with the new format. For more information, see [Longer EC2 and EBS resource IDs](http://aws.amazon.com/ec2/faqs/#longer-ids).
33//!
34//! For example, a volume Amazon Resource Name (ARN) with the longer volume ID format looks like the following:
35//!
36//! arn:aws:storagegateway:us-west-2:111122223333:gateway/sgw-12A3456B/volume/vol-1122AABBCCDDEEFFG.
37//!
38//! A snapshot ID with the longer ID format looks like the following: snap-78e226633445566ee.
39//!
40//! For more information, see [Announcement: Heads-up – Longer Storage Gateway volume and snapshot IDs coming in 2016](http://forums.aws.amazon.com/ann.jspa?annID=3557).
41//!
42//! ## Getting Started
43//!
44//! > Examples are available for many services and operations, check out the
45//! > [examples folder in GitHub](https://github.com/awslabs/aws-sdk-rust/tree/main/examples).
46//!
47//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
48//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-storagegateway` to
49//! your project, add the following to your **Cargo.toml** file:
50//!
51//! ```toml
52//! [dependencies]
53//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
54//! aws-sdk-storagegateway = "1.90.0"
55//! tokio = { version = "1", features = ["full"] }
56//! ```
57//!
58//! Then in code, a client can be created with the following:
59//!
60//! ```rust,no_run
61//! use aws_sdk_storagegateway as storagegateway;
62//!
63//! #[::tokio::main]
64//! async fn main() -> Result<(), storagegateway::Error> {
65//!     let config = aws_config::load_from_env().await;
66//!     let client = aws_sdk_storagegateway::Client::new(&config);
67//!
68//!     // ... make some calls with the client
69//!
70//!     Ok(())
71//! }
72//! ```
73//!
74//! See the [client documentation](https://docs.rs/aws-sdk-storagegateway/latest/aws_sdk_storagegateway/client/struct.Client.html)
75//! for information on what calls can be made, and the inputs and outputs for each of those calls.
76//!
77//! ## Using the SDK
78//!
79//! Until the SDK is released, we will be adding information about using the SDK to the
80//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
81//! additional sections for the guide by opening an issue and describing what you are trying to do.
82//!
83//! ## Getting Help
84//!
85//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
86//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
87//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
88//! * [Usage examples](https://github.com/awslabs/aws-sdk-rust/tree/main/examples)
89//!
90//!
91//! # Crate Organization
92//!
93//! The entry point for most customers will be [`Client`], which exposes one method for each API
94//! offered by AWS Storage Gateway. The return value of each of these methods is a "fluent builder",
95//! where the different inputs for that API are added by builder-style function call chaining,
96//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
97//! either a successful output or a [`SdkError`](crate::error::SdkError).
98//!
99//! Some of these API inputs may be structs or enums to provide more complex structured information.
100//! These structs and enums live in [`types`](crate::types). There are some simpler types for
101//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
102//!
103//! All types required to configure a client via the [`Config`](crate::Config) struct live
104//! in [`config`](crate::config).
105//!
106//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
107//! is the input, output, and error type for that API, as well as builders to construct each of those.
108//!
109//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
110//! client can return. Any other error type can be converted to this `Error` type via the
111//! [`From`](std::convert::From) trait.
112//!
113//! The other modules within this crate are not required for normal usage.
114
115// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
116pub use error_meta::Error;
117
118#[doc(inline)]
119pub use config::Config;
120
121/// Client for calling AWS Storage Gateway.
122/// ## Constructing a `Client`
123///
124/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
125/// crate should be used to automatically resolve this config using
126/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
127/// across multiple different AWS SDK clients. This config resolution process can be customized
128/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
129/// the [builder pattern] to customize the default config.
130///
131/// In the simplest case, creating a client looks as follows:
132/// ```rust,no_run
133/// # async fn wrapper() {
134/// let config = aws_config::load_from_env().await;
135/// let client = aws_sdk_storagegateway::Client::new(&config);
136/// # }
137/// ```
138///
139/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
140/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
141/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
142/// done as follows:
143///
144/// ```rust,no_run
145/// # async fn wrapper() {
146/// let sdk_config = ::aws_config::load_from_env().await;
147/// let config = aws_sdk_storagegateway::config::Builder::from(&sdk_config)
148/// # /*
149///     .some_service_specific_setting("value")
150/// # */
151///     .build();
152/// # }
153/// ```
154///
155/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
156///
157/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
158/// be done once at application start-up.
159///
160/// [`Config`]: crate::Config
161/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
162/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
163/// [`aws-config` docs]: https://docs.rs/aws-config/*
164/// [`aws-config`]: https://crates.io/crates/aws-config
165/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
166/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
167/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
168/// # Using the `Client`
169///
170/// A client has a function for every operation that can be performed by the service.
171/// For example, the [`ActivateGateway`](crate::operation::activate_gateway) operation has
172/// a [`Client::activate_gateway`], function which returns a builder for that operation.
173/// The fluent builder ultimately has a `send()` function that returns an async future that
174/// returns a result, as illustrated below:
175///
176/// ```rust,ignore
177/// let result = client.activate_gateway()
178///     .activation_key("example")
179///     .send()
180///     .await;
181/// ```
182///
183/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
184/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
185/// information.
186pub mod client;
187
188/// Configuration for AWS Storage Gateway.
189pub mod config;
190
191/// Common errors and error handling utilities.
192pub mod error;
193
194mod error_meta;
195
196/// Information about this crate.
197pub mod meta;
198
199/// All operations that this crate can perform.
200pub mod operation;
201
202/// Primitives such as `Blob` or `DateTime` used by other types.
203pub mod primitives;
204
205/// Data structures used by operation inputs/outputs.
206pub mod types;
207
208pub(crate) mod protocol_serde;
209
210mod sdk_feature_tracker;
211
212mod serialization_settings;
213
214mod endpoint_lib;
215
216mod lens;
217
218mod json_errors;
219
220mod serde_util;
221
222#[doc(inline)]
223pub use client::Client;