#[non_exhaustive]
pub enum UpdateRuleGroupErrorKind {
WafConfigurationWarningException(WafConfigurationWarningException),
WafDuplicateItemException(WafDuplicateItemException),
WafInternalErrorException(WafInternalErrorException),
WafInvalidOperationException(WafInvalidOperationException),
WafInvalidParameterException(WafInvalidParameterException),
WafLimitsExceededException(WafLimitsExceededException),
WafNonexistentItemException(WafNonexistentItemException),
WafOptimisticLockException(WafOptimisticLockException),
WafSubscriptionNotFoundException(WafSubscriptionNotFoundException),
WafUnavailableEntityException(WafUnavailableEntityException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdateRuleGroup
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
WafConfigurationWarningException(WafConfigurationWarningException)
The operation failed because you are inspecting the web request body, headers, or cookies without specifying how to handle oversize components. Rules that inspect the body must either provide an OversizeHandling
configuration or they must be preceded by a SizeConstraintStatement
that blocks the body content from being too large. Rules that inspect the headers or cookies must provide an OversizeHandling
configuration.
Provide the handling configuration and retry your operation.
Alternately, you can suppress this warning by adding the following tag to the resource that you provide to this operation: Tag
(key:WAF:OversizeFieldsHandlingConstraintOptOut
, value:true
).
WafDuplicateItemException(WafDuplicateItemException)
WAF couldn’t perform the operation because the resource that you tried to save is a duplicate of an existing one.
WafInternalErrorException(WafInternalErrorException)
Your request is valid, but WAF couldn’t perform the operation because of a system problem. Retry your request.
WafInvalidOperationException(WafInvalidOperationException)
The operation isn't valid.
WafInvalidParameterException(WafInvalidParameterException)
The operation failed because WAF didn't recognize a parameter in the request. For example:
-
You specified a parameter name or value that isn't valid.
-
Your nested statement isn't valid. You might have tried to nest a statement that can’t be nested.
-
You tried to update a
WebACL
with aDefaultAction
that isn't among the types available atDefaultAction
. -
Your request references an ARN that is malformed, or corresponds to a resource with which a web ACL can't be associated.
WafLimitsExceededException(WafLimitsExceededException)
WAF couldn’t perform the operation because you exceeded your resource limit. For example, the maximum number of WebACL
objects that you can create for an Amazon Web Services account. For more information, see WAF quotas in the WAF Developer Guide.
WafNonexistentItemException(WafNonexistentItemException)
WAF couldn’t perform the operation because your resource doesn't exist. If you've just created a resource that you're using in this operation, you might just need to wait a few minutes. It can take from a few seconds to a number of minutes for changes to propagate.
WafOptimisticLockException(WafOptimisticLockException)
WAF couldn’t save your changes because you tried to update or delete a resource that has changed since you last retrieved it. Get the resource again, make any changes you need to make to the new copy, and retry your operation.
WafSubscriptionNotFoundException(WafSubscriptionNotFoundException)
You tried to use a managed rule group that's available by subscription, but you aren't subscribed to it yet.
WAF couldn’t retrieve a resource that you specified for this operation. If you've just created a resource that you're using in this operation, you might just need to wait a few minutes. It can take from a few seconds to a number of minutes for changes to propagate. Verify the resources that you are specifying in your request parameters and then retry the operation.
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.