pub struct UpdateContainerService<C = DynConnector, M = DefaultMiddleware, R = Standard> { /* private fields */ }
Expand description
Fluent builder constructing a request to UpdateContainerService
.
Updates the configuration of your Amazon Lightsail container service, such as its power, scale, and public domain names.
Implementations
impl<C, M, R> UpdateContainerService<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
impl<C, M, R> UpdateContainerService<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
pub async fn send(
self
) -> Result<UpdateContainerServiceOutput, SdkError<UpdateContainerServiceError>> where
R::Policy: SmithyRetryPolicy<UpdateContainerServiceInputOperationOutputAlias, UpdateContainerServiceOutput, UpdateContainerServiceError, UpdateContainerServiceInputOperationRetryAlias>,
pub async fn send(
self
) -> Result<UpdateContainerServiceOutput, SdkError<UpdateContainerServiceError>> where
R::Policy: SmithyRetryPolicy<UpdateContainerServiceInputOperationOutputAlias, UpdateContainerServiceOutput, UpdateContainerServiceError, UpdateContainerServiceInputOperationRetryAlias>,
Sends the request and returns the response.
If an error occurs, an SdkError
will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
The name of the container service to update.
The name of the container service to update.
The power for the container service.
The power specifies the amount of memory, vCPUs, and base monthly cost of each node of the container service. The power
and scale
of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power
with the scale
(the number of nodes) of the service.
Use the GetContainerServicePowers
action to view the specifications of each power option.
The power for the container service.
The power specifies the amount of memory, vCPUs, and base monthly cost of each node of the container service. The power
and scale
of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power
with the scale
(the number of nodes) of the service.
Use the GetContainerServicePowers
action to view the specifications of each power option.
The scale for the container service.
The scale specifies the allocated compute nodes of the container service. The power
and scale
of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power
with the scale
(the number of nodes) of the service.
The scale for the container service.
The scale specifies the allocated compute nodes of the container service. The power
and scale
of a container service makes up its configured capacity. To determine the monthly price of your container service, multiply the base price of the power
with the scale
(the number of nodes) of the service.
A Boolean value to indicate whether the container service is disabled.
A Boolean value to indicate whether the container service is disabled.
Adds a key-value pair to publicDomainNames
.
To override the contents of this collection use set_public_domain_names
.
The public domain names to use with the container service, such as example.com
and www.example.com
.
You can specify up to four public domain names for a container service. The domain names that you specify are used when you create a deployment with a container configured as the public endpoint of your container service.
If you don't specify public domain names, then you can use the default domain of the container service.
You must create and validate an SSL/TLS certificate before you can use public domain names with your container service. Use the CreateCertificate
action to create a certificate for the public domain names you want to use with your container service.
You can specify public domain names using a string to array map as shown in the example later on this page.
The public domain names to use with the container service, such as example.com
and www.example.com
.
You can specify up to four public domain names for a container service. The domain names that you specify are used when you create a deployment with a container configured as the public endpoint of your container service.
If you don't specify public domain names, then you can use the default domain of the container service.
You must create and validate an SSL/TLS certificate before you can use public domain names with your container service. Use the CreateCertificate
action to create a certificate for the public domain names you want to use with your container service.
You can specify public domain names using a string to array map as shown in the example later on this page.
Trait Implementations
Auto Trait Implementations
impl<C = DynConnector, M = DefaultMiddleware, R = Standard> !RefUnwindSafe for UpdateContainerService<C, M, R>
impl<C, M, R> Send for UpdateContainerService<C, M, R> where
C: Send + Sync,
M: Send + Sync,
R: Send + Sync,
impl<C, M, R> Sync for UpdateContainerService<C, M, R> where
C: Send + Sync,
M: Send + Sync,
R: Send + Sync,
impl<C, M, R> Unpin for UpdateContainerService<C, M, R>
impl<C = DynConnector, M = DefaultMiddleware, R = Standard> !UnwindSafe for UpdateContainerService<C, M, R>
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more