Enum aws_sdk_sns::error::CreateTopicErrorKind
source · #[non_exhaustive]
pub enum CreateTopicErrorKind {
AuthorizationErrorException(AuthorizationErrorException),
ConcurrentAccessException(ConcurrentAccessException),
InternalErrorException(InternalErrorException),
InvalidParameterException(InvalidParameterException),
InvalidSecurityException(InvalidSecurityException),
StaleTagException(StaleTagException),
TagLimitExceededException(TagLimitExceededException),
TagPolicyException(TagPolicyException),
TopicLimitExceededException(TopicLimitExceededException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateTopic
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AuthorizationErrorException(AuthorizationErrorException)
Indicates that the user has been denied access to the requested resource.
ConcurrentAccessException(ConcurrentAccessException)
Can't perform multiple operations on a tag simultaneously. Perform the operations sequentially.
InternalErrorException(InternalErrorException)
Indicates an internal service error.
InvalidParameterException(InvalidParameterException)
Indicates that a request parameter does not comply with the associated constraints.
InvalidSecurityException(InvalidSecurityException)
The credential signature isn't valid. You must use an HTTPS endpoint and sign your request using Signature Version 4.
StaleTagException(StaleTagException)
A tag has been added to a resource with the same ARN as a deleted resource. Wait a short while and then retry the operation.
TagLimitExceededException(TagLimitExceededException)
Can't add more than 50 tags to a topic.
TagPolicyException(TagPolicyException)
The request doesn't comply with the IAM tag policy. Correct your request and then retry it.
TopicLimitExceededException(TopicLimitExceededException)
Indicates that the customer already owns the maximum allowed number of topics.
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.