aws_sdk_ssm/
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 Simple Systems Manager (SSM)
10///
11/// Client for invoking operations on Amazon Simple Systems Manager (SSM). Each operation on Amazon Simple Systems Manager (SSM) 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_ssm::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_ssm::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 [`AddTagsToResource`](crate::operation::add_tags_to_resource) operation has
63/// a [`Client::add_tags_to_resource`], 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.add_tags_to_resource()
69///     .resource_type("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/// # Waiters
78///
79/// This client provides `wait_until` methods behind the [`Waiters`](crate::client::Waiters) trait.
80/// To use them, simply import the trait, and then call one of the `wait_until` methods. This will
81/// return a waiter fluent builder that takes various parameters, which are documented on the builder
82/// type. Once parameters have been provided, the `wait` method can be called to initiate waiting.
83///
84/// For example, if there was a `wait_until_thing` method, it could look like:
85/// ```rust,ignore
86/// let result = client.wait_until_thing()
87///     .thing_id("someId")
88///     .wait(Duration::from_secs(120))
89///     .await;
90/// ```
91#[derive(::std::clone::Clone, ::std::fmt::Debug)]
92pub struct Client {
93    handle: ::std::sync::Arc<Handle>,
94}
95
96impl Client {
97    /// Creates a new client from the service [`Config`](crate::Config).
98    ///
99    /// # Panics
100    ///
101    /// This method will panic in the following cases:
102    ///
103    /// - Retries or timeouts are enabled without a `sleep_impl` configured.
104    /// - Identity caching is enabled without a `sleep_impl` and `time_source` configured.
105    /// - No `behavior_version` is provided.
106    ///
107    /// The panic message for each of these will have instructions on how to resolve them.
108    #[track_caller]
109    pub fn from_conf(conf: crate::Config) -> Self {
110        let handle = Handle {
111            conf: conf.clone(),
112            runtime_plugins: crate::config::base_client_runtime_plugins(conf),
113        };
114        if let Err(err) = Self::validate_config(&handle) {
115            panic!("Invalid client configuration: {err}");
116        }
117        Self {
118            handle: ::std::sync::Arc::new(handle),
119        }
120    }
121
122    /// Returns the client's configuration.
123    pub fn config(&self) -> &crate::Config {
124        &self.handle.conf
125    }
126
127    fn validate_config(handle: &Handle) -> ::std::result::Result<(), ::aws_smithy_runtime_api::box_error::BoxError> {
128        let mut cfg = ::aws_smithy_types::config_bag::ConfigBag::base();
129        handle
130            .runtime_plugins
131            .apply_client_configuration(&mut cfg)?
132            .validate_base_client_config(&cfg)?;
133        Ok(())
134    }
135}
136
137///
138/// Waiter functions for the client.
139///
140/// Import this trait to get `wait_until` methods on the client.
141///
142pub trait Waiters {
143    /// Wait for `command_executed`
144    fn wait_until_command_executed(&self) -> crate::waiters::command_executed::CommandExecutedFluentBuilder;
145}
146impl Waiters for Client {
147    fn wait_until_command_executed(&self) -> crate::waiters::command_executed::CommandExecutedFluentBuilder {
148        crate::waiters::command_executed::CommandExecutedFluentBuilder::new(self.handle.clone())
149    }
150}
151
152impl Client {
153    /// Creates a new client from an [SDK Config](::aws_types::sdk_config::SdkConfig).
154    ///
155    /// # Panics
156    ///
157    /// - This method will panic if the `sdk_config` is missing an async sleep implementation. If you experience this panic, set
158    ///   the `sleep_impl` on the Config passed into this function to fix it.
159    /// - This method will panic if the `sdk_config` is missing an HTTP connector. If you experience this panic, set the
160    ///   `http_connector` on the Config passed into this function to fix it.
161    /// - 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.
162    #[track_caller]
163    pub fn new(sdk_config: &::aws_types::sdk_config::SdkConfig) -> Self {
164        Self::from_conf(sdk_config.into())
165    }
166}
167
168mod add_tags_to_resource;
169
170mod associate_ops_item_related_item;
171
172mod cancel_command;
173
174mod cancel_maintenance_window_execution;
175
176mod create_activation;
177
178mod create_association;
179
180mod create_association_batch;
181
182mod create_document;
183
184mod create_maintenance_window;
185
186mod create_ops_item;
187
188mod create_ops_metadata;
189
190mod create_patch_baseline;
191
192mod create_resource_data_sync;
193
194/// Operation customization and supporting types.
195///
196/// The underlying HTTP requests made during an operation can be customized
197/// by calling the `customize()` method on the builder returned from a client
198/// operation call. For example, this can be used to add an additional HTTP header:
199///
200/// ```ignore
201/// # async fn wrapper() -> ::std::result::Result<(), aws_sdk_ssm::Error> {
202/// # let client: aws_sdk_ssm::Client = unimplemented!();
203/// use ::http::header::{HeaderName, HeaderValue};
204///
205/// let result = client.add_tags_to_resource()
206///     .customize()
207///     .mutate_request(|req| {
208///         // Add `x-example-header` with value
209///         req.headers_mut()
210///             .insert(
211///                 HeaderName::from_static("x-example-header"),
212///                 HeaderValue::from_static("1"),
213///             );
214///     })
215///     .send()
216///     .await;
217/// # }
218/// ```
219pub mod customize;
220
221mod delete_activation;
222
223mod delete_association;
224
225mod delete_document;
226
227mod delete_inventory;
228
229mod delete_maintenance_window;
230
231mod delete_ops_item;
232
233mod delete_ops_metadata;
234
235mod delete_parameter;
236
237mod delete_parameters;
238
239mod delete_patch_baseline;
240
241mod delete_resource_data_sync;
242
243mod delete_resource_policy;
244
245mod deregister_managed_instance;
246
247mod deregister_patch_baseline_for_patch_group;
248
249mod deregister_target_from_maintenance_window;
250
251mod deregister_task_from_maintenance_window;
252
253mod describe_activations;
254
255mod describe_association;
256
257mod describe_association_execution_targets;
258
259mod describe_association_executions;
260
261mod describe_automation_executions;
262
263mod describe_automation_step_executions;
264
265mod describe_available_patches;
266
267mod describe_document;
268
269mod describe_document_permission;
270
271mod describe_effective_instance_associations;
272
273mod describe_effective_patches_for_patch_baseline;
274
275mod describe_instance_associations_status;
276
277mod describe_instance_information;
278
279mod describe_instance_patch_states;
280
281mod describe_instance_patch_states_for_patch_group;
282
283mod describe_instance_patches;
284
285mod describe_instance_properties;
286
287mod describe_inventory_deletions;
288
289mod describe_maintenance_window_execution_task_invocations;
290
291mod describe_maintenance_window_execution_tasks;
292
293mod describe_maintenance_window_executions;
294
295mod describe_maintenance_window_schedule;
296
297mod describe_maintenance_window_targets;
298
299mod describe_maintenance_window_tasks;
300
301mod describe_maintenance_windows;
302
303mod describe_maintenance_windows_for_target;
304
305mod describe_ops_items;
306
307mod describe_parameters;
308
309mod describe_patch_baselines;
310
311mod describe_patch_group_state;
312
313mod describe_patch_groups;
314
315mod describe_patch_properties;
316
317mod describe_sessions;
318
319mod disassociate_ops_item_related_item;
320
321mod get_access_token;
322
323mod get_automation_execution;
324
325mod get_calendar_state;
326
327mod get_command_invocation;
328
329mod get_connection_status;
330
331mod get_default_patch_baseline;
332
333mod get_deployable_patch_snapshot_for_instance;
334
335mod get_document;
336
337mod get_execution_preview;
338
339mod get_inventory;
340
341mod get_inventory_schema;
342
343mod get_maintenance_window;
344
345mod get_maintenance_window_execution;
346
347mod get_maintenance_window_execution_task;
348
349mod get_maintenance_window_execution_task_invocation;
350
351mod get_maintenance_window_task;
352
353mod get_ops_item;
354
355mod get_ops_metadata;
356
357mod get_ops_summary;
358
359mod get_parameter;
360
361mod get_parameter_history;
362
363mod get_parameters;
364
365mod get_parameters_by_path;
366
367mod get_patch_baseline;
368
369mod get_patch_baseline_for_patch_group;
370
371mod get_resource_policies;
372
373mod get_service_setting;
374
375mod label_parameter_version;
376
377mod list_association_versions;
378
379mod list_associations;
380
381mod list_command_invocations;
382
383mod list_commands;
384
385mod list_compliance_items;
386
387mod list_compliance_summaries;
388
389mod list_document_metadata_history;
390
391mod list_document_versions;
392
393mod list_documents;
394
395mod list_inventory_entries;
396
397mod list_nodes;
398
399mod list_nodes_summary;
400
401mod list_ops_item_events;
402
403mod list_ops_item_related_items;
404
405mod list_ops_metadata;
406
407mod list_resource_compliance_summaries;
408
409mod list_resource_data_sync;
410
411mod list_tags_for_resource;
412
413mod modify_document_permission;
414
415mod put_compliance_items;
416
417mod put_inventory;
418
419mod put_parameter;
420
421mod put_resource_policy;
422
423mod register_default_patch_baseline;
424
425mod register_patch_baseline_for_patch_group;
426
427mod register_target_with_maintenance_window;
428
429mod register_task_with_maintenance_window;
430
431mod remove_tags_from_resource;
432
433mod reset_service_setting;
434
435mod resume_session;
436
437mod send_automation_signal;
438
439mod send_command;
440
441mod start_access_request;
442
443mod start_associations_once;
444
445mod start_automation_execution;
446
447mod start_change_request_execution;
448
449mod start_execution_preview;
450
451mod start_session;
452
453mod stop_automation_execution;
454
455mod terminate_session;
456
457mod unlabel_parameter_version;
458
459mod update_association;
460
461mod update_association_status;
462
463mod update_document;
464
465mod update_document_default_version;
466
467mod update_document_metadata;
468
469mod update_maintenance_window;
470
471mod update_maintenance_window_target;
472
473mod update_maintenance_window_task;
474
475mod update_managed_instance_role;
476
477mod update_ops_item;
478
479mod update_ops_metadata;
480
481mod update_patch_baseline;
482
483mod update_resource_data_sync;
484
485mod update_service_setting;