Interface StatefulEngineOptions.Builder
- All Superinterfaces:
Buildable
,CopyableBuilder<StatefulEngineOptions.Builder,
,StatefulEngineOptions> SdkBuilder<StatefulEngineOptions.Builder,
,StatefulEngineOptions> SdkPojo
- Enclosing class:
StatefulEngineOptions
-
Method Summary
Modifier and TypeMethodDescriptionIndicates how to manage the order of stateful rule evaluation for the policy.Indicates how to manage the order of stateful rule evaluation for the policy.streamExceptionPolicy
(String streamExceptionPolicy) Configures how Network Firewall processes traffic when a network connection breaks midstream.streamExceptionPolicy
(StreamExceptionPolicy streamExceptionPolicy) Configures how Network Firewall processes traffic when a network connection breaks midstream.Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFields
-
Method Details
-
ruleOrder
Indicates how to manage the order of stateful rule evaluation for the policy.
STRICT_ORDER
is the default and recommended option. WithSTRICT_ORDER
, provide your rules in the order that you want them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. ChooseSTRICT_ORDER
to have the stateful rules engine determine the evaluation order of your rules. The default action for this rule order isPASS
, followed byDROP
,REJECT
, andALERT
actions. Stateful rules are provided to the rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide.- Parameters:
ruleOrder
- Indicates how to manage the order of stateful rule evaluation for the policy.STRICT_ORDER
is the default and recommended option. WithSTRICT_ORDER
, provide your rules in the order that you want them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. ChooseSTRICT_ORDER
to have the stateful rules engine determine the evaluation order of your rules. The default action for this rule order isPASS
, followed byDROP
,REJECT
, andALERT
actions. Stateful rules are provided to the rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
ruleOrder
Indicates how to manage the order of stateful rule evaluation for the policy.
STRICT_ORDER
is the default and recommended option. WithSTRICT_ORDER
, provide your rules in the order that you want them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. ChooseSTRICT_ORDER
to have the stateful rules engine determine the evaluation order of your rules. The default action for this rule order isPASS
, followed byDROP
,REJECT
, andALERT
actions. Stateful rules are provided to the rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide.- Parameters:
ruleOrder
- Indicates how to manage the order of stateful rule evaluation for the policy.STRICT_ORDER
is the default and recommended option. WithSTRICT_ORDER
, provide your rules in the order that you want them to be evaluated. You can then choose one or more default actions for packets that don't match any rules. ChooseSTRICT_ORDER
to have the stateful rules engine determine the evaluation order of your rules. The default action for this rule order isPASS
, followed byDROP
,REJECT
, andALERT
actions. Stateful rules are provided to the rule engine as Suricata compatible strings, and Suricata evaluates them based on your settings. For more information, see Evaluation order for stateful rules in the Network Firewall Developer Guide.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
streamExceptionPolicy
Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections can break due to disruptions in external networks or within the firewall itself.
-
DROP
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is the default behavior. -
CONTINUE
- Network Firewall continues to apply rules to the subsequent traffic without context from traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you have a stateful rule todrop http
traffic, Network Firewall won't match the traffic for this rule because the service won't have the context from session initialization defining the application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using aflow:stateless
rule would still match, as would theaws:drop_strict
default action. -
REJECT
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish a new session. Network Firewall will have context about the new session and will apply rules to the subsequent traffic.
- Parameters:
streamExceptionPolicy
- Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections can break due to disruptions in external networks or within the firewall itself.-
DROP
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is the default behavior. -
CONTINUE
- Network Firewall continues to apply rules to the subsequent traffic without context from traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you have a stateful rule todrop http
traffic, Network Firewall won't match the traffic for this rule because the service won't have the context from session initialization defining the application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using aflow:stateless
rule would still match, as would theaws:drop_strict
default action. -
REJECT
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish a new session. Network Firewall will have context about the new session and will apply rules to the subsequent traffic.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
streamExceptionPolicy
Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections can break due to disruptions in external networks or within the firewall itself.
-
DROP
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is the default behavior. -
CONTINUE
- Network Firewall continues to apply rules to the subsequent traffic without context from traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you have a stateful rule todrop http
traffic, Network Firewall won't match the traffic for this rule because the service won't have the context from session initialization defining the application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using aflow:stateless
rule would still match, as would theaws:drop_strict
default action. -
REJECT
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish a new session. Network Firewall will have context about the new session and will apply rules to the subsequent traffic.
- Parameters:
streamExceptionPolicy
- Configures how Network Firewall processes traffic when a network connection breaks midstream. Network connections can break due to disruptions in external networks or within the firewall itself.-
DROP
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. This is the default behavior. -
CONTINUE
- Network Firewall continues to apply rules to the subsequent traffic without context from traffic before the break. This impacts the behavior of rules that depend on this context. For example, if you have a stateful rule todrop http
traffic, Network Firewall won't match the traffic for this rule because the service won't have the context from session initialization defining the application layer protocol as HTTP. However, this behavior is rule dependent—a TCP-layer rule using aflow:stateless
rule would still match, as would theaws:drop_strict
default action. -
REJECT
- Network Firewall fails closed and drops all subsequent traffic going to the firewall. Network Firewall also sends a TCP reject packet back to your client so that the client can immediately establish a new session. Network Firewall will have context about the new session and will apply rules to the subsequent traffic.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-