#[non_exhaustive]
pub enum CreateReplicationInstanceErrorKind {
AccessDeniedFault(AccessDeniedFault),
InsufficientResourceCapacityFault(InsufficientResourceCapacityFault),
InvalidResourceStateFault(InvalidResourceStateFault),
InvalidSubnet(InvalidSubnet),
KmsKeyNotAccessibleFault(KmsKeyNotAccessibleFault),
ReplicationSubnetGroupDoesNotCoverEnoughAZs(ReplicationSubnetGroupDoesNotCoverEnoughAZs),
ResourceAlreadyExistsFault(ResourceAlreadyExistsFault),
ResourceNotFoundFault(ResourceNotFoundFault),
ResourceQuotaExceededFault(ResourceQuotaExceededFault),
StorageQuotaExceededFault(StorageQuotaExceededFault),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateReplicationInstance
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedFault(AccessDeniedFault)
DMS was denied access to the endpoint. Check that the role is correctly configured.
InsufficientResourceCapacityFault(InsufficientResourceCapacityFault)
There are not enough resources allocated to the database migration.
InvalidResourceStateFault(InvalidResourceStateFault)
The resource is in a state that prevents it from being used for database migration.
InvalidSubnet(InvalidSubnet)
The subnet provided is invalid.
KmsKeyNotAccessibleFault(KmsKeyNotAccessibleFault)
DMS cannot access the KMS key.
ReplicationSubnetGroupDoesNotCoverEnoughAZs(ReplicationSubnetGroupDoesNotCoverEnoughAZs)
The replication subnet group does not cover enough Availability Zones (AZs). Edit the replication subnet group and add more AZs.
ResourceAlreadyExistsFault(ResourceAlreadyExistsFault)
The resource you are attempting to create already exists.
ResourceNotFoundFault(ResourceNotFoundFault)
The resource could not be found.
ResourceQuotaExceededFault(ResourceQuotaExceededFault)
The quota for this resource quota has been exceeded.
StorageQuotaExceededFault(StorageQuotaExceededFault)
The storage quota has been exceeded.
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.