@nebius/js-sdk - v0.1.41
    Preparing search index...

    Interface SecurityRuleSpec

    interface SecurityRuleSpec {
        "[customJson]"?: () => unknown;
        "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>;
        $type: "nebius.vpc.v1.SecurityRuleSpec";
        access: RuleAccessAction;
        match?:
            | { $case: "ingress"; ingress: RuleIngress }
            | { $case: "egress"; egress: RuleEgress };
        priority: number;
        protocol: RuleProtocol;
        type: RuleType;
        [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined;
    }

    Indexable

    • [key: symbol]: Uint8Array<ArrayBufferLike> | (() => unknown) | undefined
    Index

    Properties

    [customJson]? [unknownFieldsSymbol]? $type access match? priority protocol type

    Properties

    "[customJson]"?: () => unknown
    "[unknownFieldsSymbol]"?: Uint8Array<ArrayBufferLike>
    $type: "nebius.vpc.v1.SecurityRuleSpec"
    access: RuleAccessAction

    Access action for the rule. Required. Determines whether matching traffic is allowed or denied.

    match?:
        | { $case: "ingress"; ingress: RuleIngress }
        | { $case: "egress"; egress: RuleEgress }

    Indicating whether the rule matches incoming or outgoing traffic.

    priority: number

    Priority of the rule. Valid range: 0-1000. Optional. If not specified or set to 0, defaults to 500. Rules are evaluated in priority order (lower numbers first) using a first-match algorithm: only the first matching rule takes effect (ALLOW or DENY), and subsequent rules are skipped.

    When multiple rules share the same priority, DENY rules are evaluated before ALLOW rules. The final evaluation order is reflected in 'effective_priority' (see SecurityRuleStatus).

    protocol: RuleProtocol

    Protocol used in the rule. Supported values: ANY, TCP, UDP, ICMP.

    type: RuleType

    Type of the rule (STATEFUL or STATELESS) Default value is STATEFUL

    Settings

    Member Visibility

    On This Page

    Properties