#[non_exhaustive]
pub enum DisableKinesisStreamingDestinationErrorKind {
InternalServerError(InternalServerError),
InvalidEndpointException(InvalidEndpointException),
LimitExceededException(LimitExceededException),
ResourceInUseException(ResourceInUseException),
ResourceNotFoundException(ResourceNotFoundException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the DisableKinesisStreamingDestination
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
InternalServerError(InternalServerError)
An error occurred on the server side.
InvalidEndpointException(InvalidEndpointException)
LimitExceededException(LimitExceededException)
There is no limit to the number of daily on-demand backups that can be taken.
For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include CreateTable
, UpdateTable
, DeleteTable
,UpdateTimeToLive
, RestoreTableFromBackup
, and RestoreTableToPointInTime
.
When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.
There is a soft account quota of 2,500 tables.
ResourceInUseException(ResourceInUseException)
The operation conflicts with the resource's availability. For example, you attempted to recreate an existing table, or tried to delete a table currently in the CREATING
state.
ResourceNotFoundException(ResourceNotFoundException)
The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE
.
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.