#[non_exhaustive]
pub enum UpdateAssociationStatusErrorKind {
AssociationDoesNotExist(AssociationDoesNotExist),
InternalServerError(InternalServerError),
InvalidDocument(InvalidDocument),
InvalidInstanceId(InvalidInstanceId),
StatusUnchanged(StatusUnchanged),
TooManyUpdates(TooManyUpdates),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdateAssociationStatus
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AssociationDoesNotExist(AssociationDoesNotExist)
The specified association doesn't exist.
InternalServerError(InternalServerError)
An error occurred on the server side.
InvalidDocument(InvalidDocument)
The specified SSM document doesn't exist.
InvalidInstanceId(InvalidInstanceId)
The following problems can cause this exception:
-
You don't have permission to access the managed node.
-
Amazon Web Services Systems Manager Agent(SSM Agent) isn't running. Verify that SSM Agent is running.
-
SSM Agent isn't registered with the SSM endpoint. Try reinstalling SSM Agent.
-
The managed node isn't in valid state. Valid states are:
Running
,Pending
,Stopped
, andStopping
. Invalid states are:Shutting-down
andTerminated
.
StatusUnchanged(StatusUnchanged)
The updated status is the same as the current status.
TooManyUpdates(TooManyUpdates)
There are concurrent updates for a resource that supports one update at a time.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.