It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Delete a ruleset
editDelete a ruleset
editDEPRECATED: Deletes the ruleset by ID. Deprecated in favor of traffic-filter endpoints.
Request
editDELETE /api/v1/deployments/ip-filtering/rulesets/{ruleset_id}
Path parameters
editName | Type | Required | Description |
---|---|---|---|
|
|
Y |
The mandatory ruleset ID |
Query parameters
editName | Type | Required | Description |
---|---|---|---|
|
|
N |
When true, ignores the associations and deletes the rule set. When false, recognizes the associations, which prevents the deletion of the rule set. |
Responses
edit-
200
-
(
EmptyResponse
) The IP filter ruleset was successfully deleted -
404
-
(
BasicFailedReply
) The IP filter ruleset specified by {ruleset_id} cannot be found (code: 'ip_filtering.ruleset_not_found') -
449
-
(
BasicFailedReply
) elevated permissions are required. (code: '"root.unauthorized.rbac.elevated_permissions_required"') -
500
-
(
BasicFailedReply
) The request execution failed (code: 'ip_filtering.request_execution_failed')
To perform this operation, you must be authenticated by means of one of the following methods: apiKey, basicAuth.
Request example
editcurl -XDELETE https://{{hostname}}/api/v1/deployments/ip-filtering/rulesets/{ruleset_id} \ -H "Authorization: ApiKey $ECE_API_KEY"