#[non_exhaustive]
pub enum ModifyCacheSubnetGroupErrorKind {
CacheSubnetGroupNotFoundFault(CacheSubnetGroupNotFoundFault),
CacheSubnetQuotaExceededFault(CacheSubnetQuotaExceededFault),
InvalidSubnet(InvalidSubnet),
SubnetInUse(SubnetInUse),
SubnetNotAllowedFault(SubnetNotAllowedFault),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the ModifyCacheSubnetGroup
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
CacheSubnetGroupNotFoundFault(CacheSubnetGroupNotFoundFault)
The requested cache subnet group name does not refer to an existing cache subnet group.
CacheSubnetQuotaExceededFault(CacheSubnetQuotaExceededFault)
The request cannot be processed because it would exceed the allowed number of subnets in a cache subnet group.
InvalidSubnet(InvalidSubnet)
An invalid subnet identifier was specified.
SubnetInUse(SubnetInUse)
The requested subnet is being used by another cache subnet group.
SubnetNotAllowedFault(SubnetNotAllowedFault)
At least one subnet ID does not match the other subnet IDs. This mismatch typically occurs when a user sets one subnet ID to a regional Availability Zone and a different one to an outpost. Or when a user sets the subnet ID to an Outpost when not subscribed on this service.
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.