1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
//! <fullname>Elastic Load Balancing</fullname>
//!
//! <p>A load balancer distributes incoming traffic across targets, such as your EC2 instances.
//! This enables you to increase the availability of your application. The load balancer also
//! monitors the health of its registered targets and ensures that it routes traffic only to
//! healthy targets. You configure your load balancer to accept incoming traffic by specifying one
//! or more listeners, which are configured with a protocol and port number for connections from
//! clients to the load balancer. You configure a target group with a protocol and port number for
//! connections from the load balancer to the targets, and with health check settings to be used
//! when checking the health status of the targets.</p>
//!
//! <p>Elastic Load Balancing supports the following types of load balancers: Application Load
//! Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers. This
//! reference covers the following load balancer types:</p>
//! <ul>
//! <li>
//! <p>Application Load Balancer - Operates at the application layer (layer 7) and supports
//! HTTP and HTTPS.</p>
//! </li>
//! <li>
//! <p>Network Load Balancer - Operates at the transport layer (layer 4) and supports TCP,
//! TLS, and UDP.</p>
//! </li>
//! <li>
//! <p>Gateway Load Balancer - Operates at the network layer (layer 3).</p>
//! </li>
//! </ul>
//!
//! <p>For more information, see the <a href="https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/">Elastic Load Balancing User
//! Guide</a>.</p>
//!
//!
//!
//!
//!
//!
//!
//! <p>All Elastic Load Balancing operations are idempotent, which means that they complete at
//! most one time. If you repeat an operation, it succeeds.</p>
//!
//! # Crate Organization
//!
//! The entry point for most customers will be [`Client`]. [`Client`] exposes one method for each API offered
//! by the service.
//!
//! Some APIs require complex or nested arguments. These exist in [`model`](crate::model).
//!
//! Lastly, errors that can be returned by the service are contained within [`error`]. [`Error`] defines a meta
//! error encompassing all possible errors that can be returned by the service.
//!
//! The other modules within this crate are not required for normal usage.
// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
pub use Error;
pub use Config;
/// Client and fluent builders for calling the service.
/// Configuration for the service.
/// Endpoint resolution functionality
/// All error types that operations can return. Documentation on these types is copied from the model.
/// Input structures for operations. Documentation on these types is copied from the model.
/// Data structures used by operation inputs/outputs. Documentation on these types is copied from the model.
/// All operations that this crate can perform.
/// Output structures for operations. Documentation on these types is copied from the model.
/// Data primitives referenced by other data types.
/// Paginators for the service
/// Generated accessors for nested fields
/// Endpoints standard library functions
/// Crate version number.
pub static PKG_VERSION: &str = env!;
pub use Endpoint;
static API_METADATA: ApiMetadata =
new;
pub use Credentials;
pub use AppName;
pub use Region;
pub use Client;