@aws-sdk/client-network-firewall 3.616.0 → 3.620.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist-cjs/index.js CHANGED
@@ -573,7 +573,8 @@ var LogDestinationType = {
573
573
  };
574
574
  var LogType = {
575
575
  ALERT: "ALERT",
576
- FLOW: "FLOW"
576
+ FLOW: "FLOW",
577
+ TLS: "TLS"
577
578
  };
578
579
  var ResourceManagedType = {
579
580
  AWS_MANAGED_DOMAIN_LISTS: "AWS_MANAGED_DOMAIN_LISTS",
@@ -248,6 +248,7 @@ export const LogDestinationType = {
248
248
  export const LogType = {
249
249
  ALERT: "ALERT",
250
250
  FLOW: "FLOW",
251
+ TLS: "TLS",
251
252
  };
252
253
  export const ResourceManagedType = {
253
254
  AWS_MANAGED_DOMAIN_LISTS: "AWS_MANAGED_DOMAIN_LISTS",
@@ -27,8 +27,7 @@ declare const CreateTLSInspectionConfigurationCommand_base: {
27
27
  getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
28
28
  };
29
29
  /**
30
- * <p>Creates an Network Firewall TLS inspection configuration. A TLS inspection configuration contains Certificate Manager certificate associations between and the scope configurations that Network Firewall uses to decrypt and re-encrypt traffic traveling through your firewall.</p>
31
- * <p>After you create a TLS inspection configuration, you can associate it with a new firewall policy.</p>
30
+ * <p>Creates an Network Firewall TLS inspection configuration. Network Firewall uses TLS inspection configurations to decrypt your firewall's inbound and outbound SSL/TLS traffic. After decryption, Network Firewall inspects the traffic according to your firewall policy's stateful rules, and then re-encrypts it before sending it to its destination. You can enable inspection of your firewall's inbound traffic, outbound traffic, or both. To use TLS inspection with your firewall, you must first import or provision certificates using ACM, create a TLS inspection configuration, add that configuration to a new firewall policy, and then associate that policy with your firewall.</p>
32
31
  * <p>To update the settings for a TLS inspection configuration, use <a>UpdateTLSInspectionConfiguration</a>.</p>
33
32
  * <p>To manage a TLS inspection configuration's tags, use the standard Amazon Web Services resource tagging operations, <a>ListTagsForResource</a>, <a>TagResource</a>, and <a>UntagResource</a>.</p>
34
33
  * <p>To retrieve information about TLS inspection configurations, use <a>ListTLSInspectionConfigurations</a> and <a>DescribeTLSInspectionConfiguration</a>.</p>
@@ -45,7 +45,7 @@ declare const DescribeLoggingConfigurationCommand_base: {
45
45
  * // LoggingConfiguration: { // LoggingConfiguration
46
46
  * // LogDestinationConfigs: [ // LogDestinationConfigs // required
47
47
  * // { // LogDestinationConfig
48
- * // LogType: "ALERT" || "FLOW", // required
48
+ * // LogType: "ALERT" || "FLOW" || "TLS", // required
49
49
  * // LogDestinationType: "S3" || "CloudWatchLogs" || "KinesisDataFirehose", // required
50
50
  * // LogDestination: { // LogDestinationMap // required
51
51
  * // "<keys>": "STRING_VALUE",
@@ -65,7 +65,7 @@ declare const UpdateLoggingConfigurationCommand_base: {
65
65
  * LoggingConfiguration: { // LoggingConfiguration
66
66
  * LogDestinationConfigs: [ // LogDestinationConfigs // required
67
67
  * { // LogDestinationConfig
68
- * LogType: "ALERT" || "FLOW", // required
68
+ * LogType: "ALERT" || "FLOW" || "TLS", // required
69
69
  * LogDestinationType: "S3" || "CloudWatchLogs" || "KinesisDataFirehose", // required
70
70
  * LogDestination: { // LogDestinationMap // required
71
71
  * "<keys>": "STRING_VALUE",
@@ -82,7 +82,7 @@ declare const UpdateLoggingConfigurationCommand_base: {
82
82
  * // LoggingConfiguration: { // LoggingConfiguration
83
83
  * // LogDestinationConfigs: [ // LogDestinationConfigs // required
84
84
  * // { // LogDestinationConfig
85
- * // LogType: "ALERT" || "FLOW", // required
85
+ * // LogType: "ALERT" || "FLOW" || "TLS", // required
86
86
  * // LogDestinationType: "S3" || "CloudWatchLogs" || "KinesisDataFirehose", // required
87
87
  * // LogDestination: { // LogDestinationMap // required
88
88
  * // "<keys>": "STRING_VALUE",
@@ -1397,7 +1397,8 @@ export type TargetType = (typeof TargetType)[keyof typeof TargetType];
1397
1397
  /**
1398
1398
  * <p>Stateful inspection criteria for a domain list rule group. </p>
1399
1399
  * <p>For HTTPS traffic, domain filtering is SNI-based. It uses the server name indicator extension of the TLS handshake.</p>
1400
- * <p>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 <code>HOME_NET</code> rule variable to include the CIDR range of the deployment VPC plus the other CIDR ranges. For more information, see <a>RuleVariables</a> in this guide and <a href="https://docs.aws.amazon.com/network-firewall/latest/developerguide/stateful-rule-groups-domain-names.html">Stateful domain list rule groups in Network Firewall</a> in the <i>Network Firewall Developer Guide</i>.</p>
1400
+ * <p>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 <code>HOME_NET</code> rule variable to include the CIDR range of the deployment VPC plus the other CIDR ranges. For more information, see <a>RuleVariables</a> in this guide and
1401
+ * <a href="https://docs.aws.amazon.com/network-firewall/latest/developerguide/stateful-rule-groups-domain-names.html">Stateful domain list rule groups in Network Firewall</a> in the <i>Network Firewall Developer Guide</i>.</p>
1401
1402
  * @public
1402
1403
  */
1403
1404
  export interface RulesSourceList {
@@ -1614,6 +1615,10 @@ export interface StatefulRule {
1614
1615
  * can enable the rule with <code>ALERT</code> action, verify in the logs that the rule
1615
1616
  * is filtering as you want, then change the action to <code>DROP</code>.</p>
1616
1617
  * </li>
1618
+ * <li>
1619
+ * <p>
1620
+ * <b>REJECT</b> - Drops traffic that matches the conditions of the stateful rule, and sends a TCP reset packet back to sender of the packet. A TCP reset packet is a packet with no payload and an RST bit contained in the TCP header flags. REJECT is available only for TCP traffic. This option doesn't support FTP or IMAP protocols.</p>
1621
+ * </li>
1617
1622
  * </ul>
1618
1623
  * @public
1619
1624
  */
@@ -2063,8 +2068,7 @@ export interface CreateRuleGroupRequest {
2063
2068
  * <p>
2064
2069
  * <b>Capacity for a stateful rule group</b>
2065
2070
  * </p>
2066
- * <p>For
2067
- * a stateful rule group, the minimum capacity required is the number of individual rules that
2071
+ * <p>For a stateful rule group, the minimum capacity required is the number of individual rules that
2068
2072
  * you expect to have in the rule group. </p>
2069
2073
  * @public
2070
2074
  */
@@ -2702,6 +2706,7 @@ export type LogDestinationType = (typeof LogDestinationType)[keyof typeof LogDes
2702
2706
  export declare const LogType: {
2703
2707
  readonly ALERT: "ALERT";
2704
2708
  readonly FLOW: "FLOW";
2709
+ readonly TLS: "TLS";
2705
2710
  };
2706
2711
  /**
2707
2712
  * @public
@@ -2709,23 +2714,36 @@ export declare const LogType: {
2709
2714
  export type LogType = (typeof LogType)[keyof typeof LogType];
2710
2715
  /**
2711
2716
  * <p>Defines where Network Firewall sends logs for the firewall for one log type. This is used
2712
- * in <a>LoggingConfiguration</a>. You can send each type of log to an Amazon S3 bucket, a CloudWatch log group, or a Kinesis Data Firehose delivery stream.</p>
2713
- * <p>Network Firewall generates logs for stateful rule groups. You can save alert and flow log
2714
- * types. The stateful rules engine records flow logs for all network traffic that it receives.
2715
- * It records alert logs for traffic that matches stateful rules that have the rule
2716
- * action set to <code>DROP</code> or <code>ALERT</code>. </p>
2717
+ * in <a>LoggingConfiguration</a>. You can send each type of log to an Amazon S3 bucket, a CloudWatch log group, or a Firehose delivery stream.</p>
2718
+ * <p>Network Firewall generates logs for stateful rule groups. You can save alert, flow, and TLS log
2719
+ * types. </p>
2717
2720
  * @public
2718
2721
  */
2719
2722
  export interface LogDestinationConfig {
2720
2723
  /**
2721
- * <p>The type of log to send. Alert logs report traffic that matches a <a>StatefulRule</a> with an action setting that sends an alert log message. Flow logs are
2722
- * standard network traffic flow logs. </p>
2724
+ * <p>The type of log to record. You can record the following types of logs from your Network Firewall stateful engine.</p>
2725
+ * <ul>
2726
+ * <li>
2727
+ * <p>
2728
+ * <code>ALERT</code> - Logs for traffic that matches your stateful rules and that have an action that sends an alert. A stateful rule sends alerts for the rule actions DROP, ALERT, and REJECT. For more information, see <a>StatefulRule</a>.</p>
2729
+ * </li>
2730
+ * <li>
2731
+ * <p>
2732
+ * <code>FLOW</code> - Standard network traffic flow logs. The stateful rules engine records flow logs for all network traffic that it receives. Each flow log record captures the network flow for a specific standard stateless rule group.</p>
2733
+ * </li>
2734
+ * <li>
2735
+ * <p>
2736
+ * <code>TLS</code> - Logs for events that are related to TLS inspection. For more information, see
2737
+ * <a href="https://docs.aws.amazon.com/network-firewall/latest/developerguide/tls-inspection-configurations.html">Inspecting SSL/TLS traffic with TLS inspection configurations</a>
2738
+ * in the <i>Network Firewall Developer Guide</i>.</p>
2739
+ * </li>
2740
+ * </ul>
2723
2741
  * @public
2724
2742
  */
2725
2743
  LogType: LogType | undefined;
2726
2744
  /**
2727
2745
  * <p>The type of storage destination to send these logs to. You can send logs to an Amazon S3 bucket,
2728
- * a CloudWatch log group, or a Kinesis Data Firehose delivery stream.</p>
2746
+ * a CloudWatch log group, or a Firehose delivery stream.</p>
2729
2747
  * @public
2730
2748
  */
2731
2749
  LogDestinationType: LogDestinationType | undefined;
@@ -2735,9 +2753,8 @@ export interface LogDestinationConfig {
2735
2753
  * <ul>
2736
2754
  * <li>
2737
2755
  * <p>For an Amazon S3 bucket, provide the name of the bucket, with key <code>bucketName</code>,
2738
- * and optionally provide a prefix, with key <code>prefix</code>. The following example
2739
- * specifies an Amazon S3 bucket named
2740
- * <code>DOC-EXAMPLE-BUCKET</code> and the prefix <code>alerts</code>: </p>
2756
+ * and optionally provide a prefix, with key <code>prefix</code>. </p>
2757
+ * <p>The following example specifies an Amazon S3 bucket named <code>DOC-EXAMPLE-BUCKET</code> and the prefix <code>alerts</code>: </p>
2741
2758
  * <p>
2742
2759
  * <code>"LogDestination": \{ "bucketName": "DOC-EXAMPLE-BUCKET", "prefix": "alerts"
2743
2760
  * \}</code>
@@ -2752,7 +2769,7 @@ export interface LogDestinationConfig {
2752
2769
  * </p>
2753
2770
  * </li>
2754
2771
  * <li>
2755
- * <p>For a Kinesis Data Firehose delivery stream, provide the name of the delivery stream, with key
2772
+ * <p>For a Firehose delivery stream, provide the name of the delivery stream, with key
2756
2773
  * <code>deliveryStream</code>. The following example specifies a delivery stream
2757
2774
  * named <code>alert-delivery-stream</code>: </p>
2758
2775
  * <p>
@@ -639,6 +639,7 @@ export type LogDestinationType =
639
639
  export declare const LogType: {
640
640
  readonly ALERT: "ALERT";
641
641
  readonly FLOW: "FLOW";
642
+ readonly TLS: "TLS";
642
643
  };
643
644
  export type LogType = (typeof LogType)[keyof typeof LogType];
644
645
  export interface LogDestinationConfig {
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-network-firewall",
3
3
  "description": "AWS SDK for JavaScript Network Firewall Client for Node.js, Browser and React Native",
4
- "version": "3.616.0",
4
+ "version": "3.620.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "node ../../scripts/compilation/inline client-network-firewall",
@@ -20,40 +20,40 @@
20
20
  "dependencies": {
21
21
  "@aws-crypto/sha256-browser": "5.2.0",
22
22
  "@aws-crypto/sha256-js": "5.2.0",
23
- "@aws-sdk/client-sso-oidc": "3.616.0",
24
- "@aws-sdk/client-sts": "3.616.0",
25
- "@aws-sdk/core": "3.616.0",
26
- "@aws-sdk/credential-provider-node": "3.616.0",
27
- "@aws-sdk/middleware-host-header": "3.616.0",
23
+ "@aws-sdk/client-sso-oidc": "3.620.0",
24
+ "@aws-sdk/client-sts": "3.620.0",
25
+ "@aws-sdk/core": "3.620.0",
26
+ "@aws-sdk/credential-provider-node": "3.620.0",
27
+ "@aws-sdk/middleware-host-header": "3.620.0",
28
28
  "@aws-sdk/middleware-logger": "3.609.0",
29
- "@aws-sdk/middleware-recursion-detection": "3.616.0",
30
- "@aws-sdk/middleware-user-agent": "3.616.0",
29
+ "@aws-sdk/middleware-recursion-detection": "3.620.0",
30
+ "@aws-sdk/middleware-user-agent": "3.620.0",
31
31
  "@aws-sdk/region-config-resolver": "3.614.0",
32
32
  "@aws-sdk/types": "3.609.0",
33
33
  "@aws-sdk/util-endpoints": "3.614.0",
34
34
  "@aws-sdk/util-user-agent-browser": "3.609.0",
35
35
  "@aws-sdk/util-user-agent-node": "3.614.0",
36
36
  "@smithy/config-resolver": "^3.0.5",
37
- "@smithy/core": "^2.2.7",
38
- "@smithy/fetch-http-handler": "^3.2.2",
37
+ "@smithy/core": "^2.3.0",
38
+ "@smithy/fetch-http-handler": "^3.2.3",
39
39
  "@smithy/hash-node": "^3.0.3",
40
40
  "@smithy/invalid-dependency": "^3.0.3",
41
- "@smithy/middleware-content-length": "^3.0.4",
42
- "@smithy/middleware-endpoint": "^3.0.5",
43
- "@smithy/middleware-retry": "^3.0.10",
41
+ "@smithy/middleware-content-length": "^3.0.5",
42
+ "@smithy/middleware-endpoint": "^3.1.0",
43
+ "@smithy/middleware-retry": "^3.0.12",
44
44
  "@smithy/middleware-serde": "^3.0.3",
45
45
  "@smithy/middleware-stack": "^3.0.3",
46
46
  "@smithy/node-config-provider": "^3.1.4",
47
- "@smithy/node-http-handler": "^3.1.3",
48
- "@smithy/protocol-http": "^4.0.4",
49
- "@smithy/smithy-client": "^3.1.8",
47
+ "@smithy/node-http-handler": "^3.1.4",
48
+ "@smithy/protocol-http": "^4.1.0",
49
+ "@smithy/smithy-client": "^3.1.10",
50
50
  "@smithy/types": "^3.3.0",
51
51
  "@smithy/url-parser": "^3.0.3",
52
52
  "@smithy/util-base64": "^3.0.0",
53
53
  "@smithy/util-body-length-browser": "^3.0.0",
54
54
  "@smithy/util-body-length-node": "^3.0.0",
55
- "@smithy/util-defaults-mode-browser": "^3.0.10",
56
- "@smithy/util-defaults-mode-node": "^3.0.10",
55
+ "@smithy/util-defaults-mode-browser": "^3.0.12",
56
+ "@smithy/util-defaults-mode-node": "^3.0.12",
57
57
  "@smithy/util-endpoints": "^2.0.5",
58
58
  "@smithy/util-middleware": "^3.0.3",
59
59
  "@smithy/util-retry": "^3.0.3",