interface RulesSourceListProperty
| Language | Type name |
|---|---|
.NET | Amazon.CDK.Mixins.Preview.AWS.NetworkFirewall.Mixins.CfnRuleGroupPropsMixin.RulesSourceListProperty |
Go | github.com/aws/aws-cdk-go/awscdkmixinspreview/v2/awsnetworkfirewall/mixins#CfnRuleGroupPropsMixin_RulesSourceListProperty |
Java | software.amazon.awscdk.mixins.preview.services.networkfirewall.mixins.CfnRuleGroupPropsMixin.RulesSourceListProperty |
Python | aws_cdk.mixins_preview.aws_networkfirewall.mixins.CfnRuleGroupPropsMixin.RulesSourceListProperty |
TypeScript | @aws-cdk/mixins-preview » aws_networkfirewall » mixins » CfnRuleGroupPropsMixin » RulesSourceListProperty |
Stateful inspection criteria for a domain list rule group.
For HTTPS traffic, domain filtering is SNI-based. It uses the server name indicator extension of the TLS handshake.
By default, Network Firewall domain list inspection only includes traffic coming from the VPC where you deploy the firewall. To inspect traffic from IP addresses outside of the deployment VPC, you set the HOME_NET rule variable to include the CIDR range of the deployment VPC plus the other CIDR ranges. For more information, see RuleVariables in this guide and Stateful domain list rule groups in AWS Network Firewall in the Network Firewall Developer Guide
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { mixins as networkfirewall_mixins } from '@aws-cdk/mixins-preview/aws-networkfirewall';
const rulesSourceListProperty: networkfirewall_mixins.CfnRuleGroupPropsMixin.RulesSourceListProperty = {
generatedRulesType: 'generatedRulesType',
targets: ['targets'],
targetTypes: ['targetTypes'],
};
Properties
| Name | Type | Description |
|---|---|---|
| generated | string | Whether you want to apply allow, reject, alert, or drop behavior to the domains in your target list. |
| target | string[] | The types of targets to inspect for. |
| targets? | string[] | The domains that you want to inspect for in your traffic flows. Valid domain specifications are the following:. |
generatedRulesType?
Type:
string
(optional)
Whether you want to apply allow, reject, alert, or drop behavior to the domains in your target list.
When logging is enabled and you choose Alert, traffic that matches the domain specifications generates an alert in the firewall's logs. Then, traffic either passes, is rejected, or drops based on other rules in the firewall policy.
targetTypes?
Type:
string[]
(optional)
The types of targets to inspect for.
Valid values are TLS_SNI and HTTP_HOST .
targets?
Type:
string[]
(optional)
The domains that you want to inspect for in your traffic flows. Valid domain specifications are the following:.
- Explicit names. For example,
abc.example.commatches only the domainabc.example.com. - Names that use a domain wildcard, which you indicate with an initial '
.'. For example,.example.commatchesexample.comand matches all subdomains ofexample.com, such asabc.example.comandwww.example.com.

.NET
Go
Java
Python
TypeScript