aws_sdk_guardduty/client.rs
1// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
2#[derive(Debug)]
3pub(crate) struct Handle {
4 pub(crate) conf: crate::Config,
5 #[allow(dead_code)] // unused when a service does not provide any operations
6 pub(crate) runtime_plugins: ::aws_smithy_runtime_api::client::runtime_plugin::RuntimePlugins,
7}
8
9/// Client for Amazon GuardDuty
10///
11/// Client for invoking operations on Amazon GuardDuty. Each operation on Amazon GuardDuty is a method on this
12/// this struct. `.send()` MUST be invoked on the generated operations to dispatch the request to the service.
13/// ## Constructing a `Client`
14///
15/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
16/// crate should be used to automatically resolve this config using
17/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
18/// across multiple different AWS SDK clients. This config resolution process can be customized
19/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
20/// the [builder pattern] to customize the default config.
21///
22/// In the simplest case, creating a client looks as follows:
23/// ```rust,no_run
24/// # async fn wrapper() {
25/// let config = aws_config::load_from_env().await;
26/// let client = aws_sdk_guardduty::Client::new(&config);
27/// # }
28/// ```
29///
30/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
31/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
32/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
33/// done as follows:
34///
35/// ```rust,no_run
36/// # async fn wrapper() {
37/// let sdk_config = ::aws_config::load_from_env().await;
38/// let config = aws_sdk_guardduty::config::Builder::from(&sdk_config)
39/// # /*
40/// .some_service_specific_setting("value")
41/// # */
42/// .build();
43/// # }
44/// ```
45///
46/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
47///
48/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
49/// be done once at application start-up.
50///
51/// [`Config`]: crate::Config
52/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
53/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
54/// [`aws-config` docs]: https://docs.rs/aws-config/*
55/// [`aws-config`]: https://crates.io/crates/aws-config
56/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
57/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
58/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
59/// # Using the `Client`
60///
61/// A client has a function for every operation that can be performed by the service.
62/// For example, the [`AcceptAdministratorInvitation`](crate::operation::accept_administrator_invitation) operation has
63/// a [`Client::accept_administrator_invitation`], function which returns a builder for that operation.
64/// The fluent builder ultimately has a `send()` function that returns an async future that
65/// returns a result, as illustrated below:
66///
67/// ```rust,ignore
68/// let result = client.accept_administrator_invitation()
69/// .detector_id("example")
70/// .send()
71/// .await;
72/// ```
73///
74/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
75/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
76/// information.
77#[derive(::std::clone::Clone, ::std::fmt::Debug)]
78pub struct Client {
79 handle: ::std::sync::Arc<Handle>,
80}
81
82impl Client {
83 /// Creates a new client from the service [`Config`](crate::Config).
84 ///
85 /// # Panics
86 ///
87 /// This method will panic in the following cases:
88 ///
89 /// - Retries or timeouts are enabled without a `sleep_impl` configured.
90 /// - Identity caching is enabled without a `sleep_impl` and `time_source` configured.
91 /// - No `behavior_version` is provided.
92 ///
93 /// The panic message for each of these will have instructions on how to resolve them.
94 #[track_caller]
95 pub fn from_conf(conf: crate::Config) -> Self {
96 let handle = Handle {
97 conf: conf.clone(),
98 runtime_plugins: crate::config::base_client_runtime_plugins(conf),
99 };
100 if let Err(err) = Self::validate_config(&handle) {
101 panic!("Invalid client configuration: {err}");
102 }
103 Self {
104 handle: ::std::sync::Arc::new(handle),
105 }
106 }
107
108 /// Returns the client's configuration.
109 pub fn config(&self) -> &crate::Config {
110 &self.handle.conf
111 }
112
113 fn validate_config(handle: &Handle) -> ::std::result::Result<(), ::aws_smithy_runtime_api::box_error::BoxError> {
114 let mut cfg = ::aws_smithy_types::config_bag::ConfigBag::base();
115 handle
116 .runtime_plugins
117 .apply_client_configuration(&mut cfg)?
118 .validate_base_client_config(&cfg)?;
119 Ok(())
120 }
121}
122
123impl Client {
124 /// Creates a new client from an [SDK Config](::aws_types::sdk_config::SdkConfig).
125 ///
126 /// # Panics
127 ///
128 /// - This method will panic if the `sdk_config` is missing an async sleep implementation. If you experience this panic, set
129 /// the `sleep_impl` on the Config passed into this function to fix it.
130 /// - This method will panic if the `sdk_config` is missing an HTTP connector. If you experience this panic, set the
131 /// `http_connector` on the Config passed into this function to fix it.
132 /// - This method will panic if no `BehaviorVersion` is provided. If you experience this panic, set `behavior_version` on the Config or enable the `behavior-version-latest` Cargo feature.
133 #[track_caller]
134 pub fn new(sdk_config: &::aws_types::sdk_config::SdkConfig) -> Self {
135 Self::from_conf(sdk_config.into())
136 }
137}
138
139mod accept_administrator_invitation;
140
141mod accept_invitation;
142
143mod archive_findings;
144
145mod create_detector;
146
147mod create_filter;
148
149mod create_ip_set;
150
151mod create_malware_protection_plan;
152
153mod create_members;
154
155mod create_publishing_destination;
156
157mod create_sample_findings;
158
159mod create_threat_entity_set;
160
161mod create_threat_intel_set;
162
163mod create_trusted_entity_set;
164
165/// Operation customization and supporting types.
166///
167/// The underlying HTTP requests made during an operation can be customized
168/// by calling the `customize()` method on the builder returned from a client
169/// operation call. For example, this can be used to add an additional HTTP header:
170///
171/// ```ignore
172/// # async fn wrapper() -> ::std::result::Result<(), aws_sdk_guardduty::Error> {
173/// # let client: aws_sdk_guardduty::Client = unimplemented!();
174/// use ::http::header::{HeaderName, HeaderValue};
175///
176/// let result = client.accept_administrator_invitation()
177/// .customize()
178/// .mutate_request(|req| {
179/// // Add `x-example-header` with value
180/// req.headers_mut()
181/// .insert(
182/// HeaderName::from_static("x-example-header"),
183/// HeaderValue::from_static("1"),
184/// );
185/// })
186/// .send()
187/// .await;
188/// # }
189/// ```
190pub mod customize;
191
192mod decline_invitations;
193
194mod delete_detector;
195
196mod delete_filter;
197
198mod delete_invitations;
199
200mod delete_ip_set;
201
202mod delete_malware_protection_plan;
203
204mod delete_members;
205
206mod delete_publishing_destination;
207
208mod delete_threat_entity_set;
209
210mod delete_threat_intel_set;
211
212mod delete_trusted_entity_set;
213
214mod describe_malware_scans;
215
216mod describe_organization_configuration;
217
218mod describe_publishing_destination;
219
220mod disable_organization_admin_account;
221
222mod disassociate_from_administrator_account;
223
224mod disassociate_from_master_account;
225
226mod disassociate_members;
227
228mod enable_organization_admin_account;
229
230mod get_administrator_account;
231
232mod get_coverage_statistics;
233
234mod get_detector;
235
236mod get_filter;
237
238mod get_findings;
239
240mod get_findings_statistics;
241
242mod get_invitations_count;
243
244mod get_ip_set;
245
246mod get_malware_protection_plan;
247
248mod get_malware_scan;
249
250mod get_malware_scan_settings;
251
252mod get_master_account;
253
254mod get_member_detectors;
255
256mod get_members;
257
258mod get_organization_statistics;
259
260mod get_remaining_free_trial_days;
261
262mod get_threat_entity_set;
263
264mod get_threat_intel_set;
265
266mod get_trusted_entity_set;
267
268mod get_usage_statistics;
269
270mod invite_members;
271
272mod list_coverage;
273
274mod list_detectors;
275
276mod list_filters;
277
278mod list_findings;
279
280mod list_invitations;
281
282mod list_ip_sets;
283
284mod list_malware_protection_plans;
285
286mod list_malware_scans;
287
288mod list_members;
289
290mod list_organization_admin_accounts;
291
292mod list_publishing_destinations;
293
294mod list_tags_for_resource;
295
296mod list_threat_entity_sets;
297
298mod list_threat_intel_sets;
299
300mod list_trusted_entity_sets;
301
302mod send_object_malware_scan;
303
304mod start_malware_scan;
305
306mod start_monitoring_members;
307
308mod stop_monitoring_members;
309
310mod tag_resource;
311
312mod unarchive_findings;
313
314mod untag_resource;
315
316mod update_detector;
317
318mod update_filter;
319
320mod update_findings_feedback;
321
322mod update_ip_set;
323
324mod update_malware_protection_plan;
325
326mod update_malware_scan_settings;
327
328mod update_member_detectors;
329
330mod update_organization_configuration;
331
332mod update_publishing_destination;
333
334mod update_threat_entity_set;
335
336mod update_threat_intel_set;
337
338mod update_trusted_entity_set;