Filters, rules and taint

Set the outbound connection rules

Replaces one scope's outbound connection policy: its three settings and its whole ordered rule list, in one step. mode is untrusted (check only destinations that untrusted input chose) or all (check every connection); default is allow or deny (what happens when no rule matches); on_violation is block or report. Null or an empty string for any of the three means inherit. Each rule is {action: allow|deny, target, note}; a target is *, an IP address, a CIDR range, a host name, *.domain, @internal, @metadata, or an http(s) URL prefix, with an optional :port. Targets come back in canonical form. A bad row is a 400 naming the row number. At most 128 rules per scope. Machines pick the change up on their next config fetch, within about 30 seconds. Cookie callers must pass CSRF.

This is a write: a read-only API key is refused with 403.

put/api/egress/

Request

  • Base URL: https://eyalsec.com
  • URL: https://eyalsec.com/api/egress/
  • Auth: one of:
    • API key in header X-API-Key
    • API key in cookie __Host-es2session

Request body

machinestring

An es-python machine public_id; omit/empty for the account policy.

modestring nullable

untrusted, all, or null to inherit.

defaultstring nullable

allow, deny, or null to inherit.

on_violationstring nullable

block, report, or null to inherit.

Response

OK. For example:

200 with the same body as GET, carrying the stored values.
number required

Changes

No recorded changes to this operation across all 1 revision of this API.