Interface CfnFirewallPolicy.StatefulEngineOptionsProperty
- All Superinterfaces:
software.amazon.jsii.JsiiSerializable
- All Known Implementing Classes:
CfnFirewallPolicy.StatefulEngineOptionsProperty.Jsii$Proxy
- Enclosing class:
CfnFirewallPolicy
Example:
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import software.amazon.awscdk.services.networkfirewall.*;
StatefulEngineOptionsProperty statefulEngineOptionsProperty = StatefulEngineOptionsProperty.builder()
.ruleOrder("ruleOrder")
.streamExceptionPolicy("streamExceptionPolicy")
.build();
- See Also:
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic final classA builder forCfnFirewallPolicy.StatefulEngineOptionsPropertystatic final classAn implementation forCfnFirewallPolicy.StatefulEngineOptionsProperty -
Method Summary
Methods inherited from interface software.amazon.jsii.JsiiSerializable
$jsii$toJson
-
Method Details
-
getRuleOrder
Indicates how to manage the order of stateful rule evaluation for the policy.STRICT_ORDERis 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_ORDERto have the stateful rules engine determine the evaluation order of your rules. The default action for this rule order isPASS, followed byDROP,REJECT, andALERTactions. 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 AWS Network Firewall Developer Guide .- See Also:
-
getStreamExceptionPolicy
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 httptraffic, 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:statelessrule would still match, as would theaws:drop_strictdefault 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.
- See Also:
-
builder
-