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.
Create ruleset association
editCreate ruleset association
editApplies the ruleset to the specified deployment.
Request
editPOST /api/v1/deployments/traffic-filter/rulesets/{ruleset_id}/associations
Path parameters
editName | Type | Required | Description |
---|---|---|---|
|
|
Y |
The mandatory ruleset ID. |
Request body
edit(FilterAssociation
) (required) Mandatory ruleset association description
Responses
edit-
200
-
(
EmptyResponse
) Create association request was valid and the association already exists -
201
-
(
EmptyResponse
) Create association request was valid and the association has been created -
404
-
(
BasicFailedReply
) The traffic filter ruleset specified by {ruleset_id} cannot be found. (code:traffic_filter.not_found
)Headers
-
x-cloud-error-codes
(string
; allowed values: [traffic_filter.not_found
]) - The error codes associated with the response
-
-
500
-
(
BasicFailedReply
) Creation failed. (code:traffic_filter.request_execution_failed
)Headers
-
x-cloud-error-codes
(string
; allowed values: [traffic_filter.request_execution_failed
]) - The error codes associated with the response
-
Request example
editcurl -XPOST https://{{hostname}}/api/v1/deployments/traffic-filter/rulesets/{ruleset_id}/associations \ -H "Authorization: ApiKey $ECE_API_KEY" \ -H 'Content-Type: application/json' \ -d ' { "entity_type" : "string", "id" : "string" } '