UpdateIPSet (smaws-clients.Smaws_Client

val request : 
  Smaws_Lib.Context.t ->
  update_ip_set_request ->
  (update_ip_set_response,
    [> Smaws_Lib.Protocols.AwsJson.error
    | `WAFDuplicateItemException of waf_duplicate_item_exception
    | `WAFInternalErrorException of waf_internal_error_exception
    | `WAFInvalidOperationException of waf_invalid_operation_exception
    | `WAFInvalidParameterException of waf_invalid_parameter_exception
    | `WAFLimitsExceededException of waf_limits_exceeded_exception
    | `WAFNonexistentItemException of waf_nonexistent_item_exception
    | `WAFOptimisticLockException of waf_optimistic_lock_exception ])
    Stdlib.result

Updates the specified IPSet.

This operation completely replaces the mutable specifications that you already have for the IP set with the ones that you provide to this call.

To modify an IP set, do the following:

Retrieve it by calling GetIPSet
Update its settings as needed
Provide the complete IP set specification to this call

Temporary inconsistencies during updates

When you create or change a web ACL or other WAF resources, the changes take a small amount of time to propagate to all areas where the resources are stored. The propagation time can be from a few seconds to a number of minutes.

The following are examples of the temporary inconsistencies that you might notice during change propagation:

After you create a web ACL, if you try to associate it with a resource, you might get an exception indicating that the web ACL is unavailable.
After you add a rule group to a web ACL, the new rule group rules might be in effect in one area where the web ACL is used and not in another.
After you change a rule action setting, you might see the old action in some places and the new action in others.
After you add an IP address to an IP set that is in use in a blocking rule, the new address might be blocked in one area while still allowed in another.