Module aws_sdk_wafv2::types::error
source · Expand description
Error types that AWS WAFV2 can respond with.
Modules§
- Builders
Structs§
WAF couldn’t perform the operation because your resource is being used by another resource or it’s associated with another resource.
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 aSizeConstraintStatement
that blocks the body content from being too large. Rules that inspect the headers or cookies must provide anOversizeHandling
configuration.WAF couldn’t perform the operation because the resource that you tried to save is a duplicate of an existing one.
The operation failed because the specified version for the managed rule group has expired. You can retrieve the available versions for the managed rule group by calling
ListAvailableManagedRuleGroupVersions
.Your request is valid, but WAF couldn’t perform the operation because of a system problem. Retry your request.
The operation isn't valid.
The operation failed because WAF didn't recognize a parameter in the request. For example:
The operation failed because the specified policy isn't in the proper format.
WAF couldn’t perform the operation because the resource that you requested isn’t valid. Check the resource, and try again.
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.The operation failed because you don't have the permissions that your logging configuration requires. For information, see Logging web ACL traffic information in the WAF Developer Guide.
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.
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.
WAF is not able to access the service linked role. This can be caused by a previous
PutLoggingConfiguration
request, which can lock the service linked role for about 20 seconds. Please try your request again. The service linked role can also be locked by a previousDeleteServiceLinkedRole
request, which can lock the role for 15 minutes or more. If you recently made a call toDeleteServiceLinkedRole
, wait at least 15 minutes and try the request again. If you receive this same exception again, you will have to wait additional time until the role is unlocked.You tried to use a managed rule group that's available by subscription, but you aren't subscribed to it yet.
An error occurred during the tagging operation. Retry your request.
WAF couldn’t perform your tagging operation because of an internal error. Retry your request.
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.
The rule that you've named doesn't aggregate solely on the IP address or solely on the forwarded IP address. This call is only available for rate-based rules with an
AggregateKeyType
setting ofIP
orFORWARDED_IP
.