#[non_exhaustive]
pub enum ModifyDBSubnetGroupErrorKind {
DbSubnetGroupDoesNotCoverEnoughAZs(DbSubnetGroupDoesNotCoverEnoughAZs),
DbSubnetGroupNotFoundFault(DbSubnetGroupNotFoundFault),
DbSubnetQuotaExceededFault(DbSubnetQuotaExceededFault),
InvalidSubnet(InvalidSubnet),
SubnetAlreadyInUse(SubnetAlreadyInUse),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the ModifyDBSubnetGroup
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
DbSubnetGroupDoesNotCoverEnoughAZs(DbSubnetGroupDoesNotCoverEnoughAZs)
Subnets in the subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
DbSubnetGroupNotFoundFault(DbSubnetGroupNotFoundFault)
DBSubnetGroupName
doesn't refer to an existing subnet group.
DbSubnetQuotaExceededFault(DbSubnetQuotaExceededFault)
The request would cause you to exceed the allowed number of subnets in a subnet group.
InvalidSubnet(InvalidSubnet)
The requested subnet is not valid, or multiple subnets were requested that are not all in a common virtual private cloud (VPC).
SubnetAlreadyInUse(SubnetAlreadyInUse)
The subnet is already in use in the Availability Zone.
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.