aws-sdk-wafv2 1.70.0 → 1.72.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 709fa74d545a9bd5a3313ce44f8e5d2598cbcf703eb04f1cc41e28cd60125506
4
- data.tar.gz: bb19fdda06d4593e0cb4423c85f934918d6b6176cf789cfb4a5f7180ce91b279
3
+ metadata.gz: 667eb0c7becd2a1a7a54f79947025353b7e9bce0491d8363a7ececbf87643bda
4
+ data.tar.gz: 40af3093da425f3127efa326e50994b8bcb6e6b02467a4165bc60252a91eb5a9
5
5
  SHA512:
6
- metadata.gz: ba7f965bdadb365aabcf1763dd783dedc8c95d0e76d3674962e28452a598dcf2777c24bed0c862e903f649052b60fb61db8b3f71106c81bd28d16da612af5059
7
- data.tar.gz: b255ec9c6c0c478e56f92d62708273fc2ff0e5988ebb606d2fc4cbb1246b3c40bcd9a9a0d1b4d5a31901171ecaee1d4be0e31a012ffe95393e1306a77ffe19fa
6
+ metadata.gz: 1d1639fd9b0f249643a2f484f02eb0f1724c531a25327d1f84c8c5cb527e07017b89aaebf3b72c5de847c55424f1013c0f6870b9c2ed98eec3c97f88f7d00376
7
+ data.tar.gz: e085a883e262bae5d4e47b9f11b1648cba050194679d68a024d8b4e55e1eac5a46dbeddec169adcc4173177997e77ee1b424250c3bc56c5be6e252a17f3d335e
data/CHANGELOG.md CHANGED
@@ -1,6 +1,16 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.72.0 (2023-10-27)
5
+ ------------------
6
+
7
+ * Feature - Updates the descriptions for the calls that manage web ACL associations, to provide information for customer-managed IAM policies.
8
+
9
+ 1.71.0 (2023-09-28)
10
+ ------------------
11
+
12
+ * Feature - Correct and improve the documentation for the FieldToMatch option JA3 fingerprint.
13
+
4
14
  1.70.0 (2023-09-27)
5
15
  ------------------
6
16
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.70.0
1
+ 1.72.0
@@ -410,23 +410,41 @@ module Aws::WAFV2
410
410
  # Resource Name (ARN) of the web ACL. For information, see
411
411
  # [UpdateDistribution][1] in the *Amazon CloudFront Developer Guide*.
412
412
  #
413
- # When you make changes to web ACLs or web ACL components, like rules
414
- # and rule groups, WAF propagates the changes everywhere that the web
415
- # ACL and its components are stored and used. Your changes are applied
416
- # within seconds, but there might be a brief period of inconsistency
417
- # when the changes have arrived in some places and not in others. So,
418
- # for example, if you change a rule action setting, the action might be
419
- # the old action in one area and the new action in another area. Or if
420
- # you add an IP address to an IP set used in a blocking rule, the new
421
- # address might briefly be blocked in one area while still allowed in
422
- # another. This temporary inconsistency can occur when you first
423
- # associate a web ACL with an Amazon Web Services resource and when you
424
- # change a web ACL that is already associated with a resource.
425
- # Generally, any inconsistencies of this type last only a few seconds.
413
+ # **Required permissions for customer-managed IAM policies**
414
+ #
415
+ # This call requires permissions that are specific to the protected
416
+ # resource type. For details, see [Permissions for AssociateWebACL][2]
417
+ # in the *WAF Developer Guide*.
418
+ #
419
+ # **Temporary inconsistencies during updates**
420
+ #
421
+ # When you create or change a web ACL or other WAF resources, the
422
+ # changes take a small amount of time to propagate to all areas where
423
+ # the resources are stored. The propagation time can be from a few
424
+ # seconds to a number of minutes.
425
+ #
426
+ # The following are examples of the temporary inconsistencies that you
427
+ # might notice during change propagation:
428
+ #
429
+ # * After you create a web ACL, if you try to associate it with a
430
+ # resource, you might get an exception indicating that the web ACL is
431
+ # unavailable.
432
+ #
433
+ # * After you add a rule group to a web ACL, the new rule group rules
434
+ # might be in effect in one area where the web ACL is used and not in
435
+ # another.
436
+ #
437
+ # * After you change a rule action setting, you might see the old action
438
+ # in some places and the new action in others.
439
+ #
440
+ # * After you add an IP address to an IP set that is in use in a
441
+ # blocking rule, the new address might be blocked in one area while
442
+ # still allowed in another.
426
443
  #
427
444
  #
428
445
  #
429
446
  # [1]: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_UpdateDistribution.html
447
+ # [2]: https://docs.aws.amazon.com/waf/latest/developerguide/security_iam_service-with-iam.html#security_iam_action-AssociateWebACL
430
448
  #
431
449
  # @option params [required, String] :web_acl_arn
432
450
  # The Amazon Resource Name (ARN) of the web ACL that you want to
@@ -4138,9 +4156,16 @@ module Aws::WAFV2
4138
4156
  # `UpdateDistribution`. For information, see [UpdateDistribution][1] in
4139
4157
  # the *Amazon CloudFront API Reference*.
4140
4158
  #
4159
+ # **Required permissions for customer-managed IAM policies**
4160
+ #
4161
+ # This call requires permissions that are specific to the protected
4162
+ # resource type. For details, see [Permissions for
4163
+ # DisassociateWebACL][2] in the *WAF Developer Guide*.
4164
+ #
4141
4165
  #
4142
4166
  #
4143
4167
  # [1]: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_UpdateDistribution.html
4168
+ # [2]: https://docs.aws.amazon.com/waf/latest/developerguide/security_iam_service-with-iam.html#security_iam_action-DisassociateWebACL
4144
4169
  #
4145
4170
  # @option params [required, String] :resource_arn
4146
4171
  # The Amazon Resource Name (ARN) of the resource to disassociate from
@@ -5285,6 +5310,27 @@ module Aws::WAFV2
5285
5310
 
5286
5311
  # Retrieves the WebACL for the specified resource.
5287
5312
  #
5313
+ # This call uses `GetWebACL`, to verify that your account has permission
5314
+ # to access the retrieved web ACL. If you get an error that indicates
5315
+ # that your account isn't authorized to perform `wafv2:GetWebACL` on
5316
+ # the resource, that error won't be included in your CloudTrail event
5317
+ # history.
5318
+ #
5319
+ # For Amazon CloudFront, don't use this call. Instead, call the
5320
+ # CloudFront action `GetDistributionConfig`. For information, see
5321
+ # [GetDistributionConfig][1] in the *Amazon CloudFront API Reference*.
5322
+ #
5323
+ # **Required permissions for customer-managed IAM policies**
5324
+ #
5325
+ # This call requires permissions that are specific to the protected
5326
+ # resource type. For details, see [Permissions for
5327
+ # GetWebACLForResource][2] in the *WAF Developer Guide*.
5328
+ #
5329
+ #
5330
+ #
5331
+ # [1]: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_GetDistributionConfig.html
5332
+ # [2]: https://docs.aws.amazon.com/waf/latest/developerguide/security_iam_service-with-iam.html#security_iam_action-GetWebACLForResource
5333
+ #
5288
5334
  # @option params [required, String] :resource_arn
5289
5335
  # The Amazon Resource Name (ARN) of the resource whose web ACL you want
5290
5336
  # to retrieve.
@@ -5894,9 +5940,23 @@ module Aws::WAFV2
5894
5940
  end
5895
5941
 
5896
5942
  # Retrieves an array of the Amazon Resource Names (ARNs) for the
5897
- # regional resources that are associated with the specified web ACL. If
5898
- # you want the list of Amazon CloudFront resources, use the CloudFront
5899
- # call `ListDistributionsByWebACLId`.
5943
+ # regional resources that are associated with the specified web ACL.
5944
+ #
5945
+ # For Amazon CloudFront, don't use this call. Instead, use the
5946
+ # CloudFront call `ListDistributionsByWebACLId`. For information, see
5947
+ # [ListDistributionsByWebACLId][1] in the *Amazon CloudFront API
5948
+ # Reference*.
5949
+ #
5950
+ # **Required permissions for customer-managed IAM policies**
5951
+ #
5952
+ # This call requires permissions that are specific to the protected
5953
+ # resource type. For details, see [Permissions for
5954
+ # ListResourcesForWebACL][2] in the *WAF Developer Guide*.
5955
+ #
5956
+ #
5957
+ #
5958
+ # [1]: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_ListDistributionsByWebACLId.html
5959
+ # [2]: https://docs.aws.amazon.com/waf/latest/developerguide/security_iam_service-with-iam.html#security_iam_action-ListResourcesForWebACL
5900
5960
  #
5901
5961
  # @option params [required, String] :web_acl_arn
5902
5962
  # The Amazon Resource Name (ARN) of the web ACL.
@@ -6570,19 +6630,30 @@ module Aws::WAFV2
6570
6630
  #
6571
6631
  # </note>
6572
6632
  #
6573
- # When you make changes to web ACLs or web ACL components, like rules
6574
- # and rule groups, WAF propagates the changes everywhere that the web
6575
- # ACL and its components are stored and used. Your changes are applied
6576
- # within seconds, but there might be a brief period of inconsistency
6577
- # when the changes have arrived in some places and not in others. So,
6578
- # for example, if you change a rule action setting, the action might be
6579
- # the old action in one area and the new action in another area. Or if
6580
- # you add an IP address to an IP set used in a blocking rule, the new
6581
- # address might briefly be blocked in one area while still allowed in
6582
- # another. This temporary inconsistency can occur when you first
6583
- # associate a web ACL with an Amazon Web Services resource and when you
6584
- # change a web ACL that is already associated with a resource.
6585
- # Generally, any inconsistencies of this type last only a few seconds.
6633
+ # **Temporary inconsistencies during updates**
6634
+ #
6635
+ # When you create or change a web ACL or other WAF resources, the
6636
+ # changes take a small amount of time to propagate to all areas where
6637
+ # the resources are stored. The propagation time can be from a few
6638
+ # seconds to a number of minutes.
6639
+ #
6640
+ # The following are examples of the temporary inconsistencies that you
6641
+ # might notice during change propagation:
6642
+ #
6643
+ # * After you create a web ACL, if you try to associate it with a
6644
+ # resource, you might get an exception indicating that the web ACL is
6645
+ # unavailable.
6646
+ #
6647
+ # * After you add a rule group to a web ACL, the new rule group rules
6648
+ # might be in effect in one area where the web ACL is used and not in
6649
+ # another.
6650
+ #
6651
+ # * After you change a rule action setting, you might see the old action
6652
+ # in some places and the new action in others.
6653
+ #
6654
+ # * After you add an IP address to an IP set that is in use in a
6655
+ # blocking rule, the new address might be blocked in one area while
6656
+ # still allowed in another.
6586
6657
  #
6587
6658
  # @option params [required, String] :name
6588
6659
  # The name of the IP set. You cannot change the name of an `IPSet` after
@@ -6803,19 +6874,30 @@ module Aws::WAFV2
6803
6874
  #
6804
6875
  # </note>
6805
6876
  #
6806
- # When you make changes to web ACLs or web ACL components, like rules
6807
- # and rule groups, WAF propagates the changes everywhere that the web
6808
- # ACL and its components are stored and used. Your changes are applied
6809
- # within seconds, but there might be a brief period of inconsistency
6810
- # when the changes have arrived in some places and not in others. So,
6811
- # for example, if you change a rule action setting, the action might be
6812
- # the old action in one area and the new action in another area. Or if
6813
- # you add an IP address to an IP set used in a blocking rule, the new
6814
- # address might briefly be blocked in one area while still allowed in
6815
- # another. This temporary inconsistency can occur when you first
6816
- # associate a web ACL with an Amazon Web Services resource and when you
6817
- # change a web ACL that is already associated with a resource.
6818
- # Generally, any inconsistencies of this type last only a few seconds.
6877
+ # **Temporary inconsistencies during updates**
6878
+ #
6879
+ # When you create or change a web ACL or other WAF resources, the
6880
+ # changes take a small amount of time to propagate to all areas where
6881
+ # the resources are stored. The propagation time can be from a few
6882
+ # seconds to a number of minutes.
6883
+ #
6884
+ # The following are examples of the temporary inconsistencies that you
6885
+ # might notice during change propagation:
6886
+ #
6887
+ # * After you create a web ACL, if you try to associate it with a
6888
+ # resource, you might get an exception indicating that the web ACL is
6889
+ # unavailable.
6890
+ #
6891
+ # * After you add a rule group to a web ACL, the new rule group rules
6892
+ # might be in effect in one area where the web ACL is used and not in
6893
+ # another.
6894
+ #
6895
+ # * After you change a rule action setting, you might see the old action
6896
+ # in some places and the new action in others.
6897
+ #
6898
+ # * After you add an IP address to an IP set that is in use in a
6899
+ # blocking rule, the new address might be blocked in one area while
6900
+ # still allowed in another.
6819
6901
  #
6820
6902
  # @option params [required, String] :name
6821
6903
  # The name of the set. You cannot change the name after you create the
@@ -6904,26 +6986,37 @@ module Aws::WAFV2
6904
6986
  #
6905
6987
  # </note>
6906
6988
  #
6907
- # When you make changes to web ACLs or web ACL components, like rules
6908
- # and rule groups, WAF propagates the changes everywhere that the web
6909
- # ACL and its components are stored and used. Your changes are applied
6910
- # within seconds, but there might be a brief period of inconsistency
6911
- # when the changes have arrived in some places and not in others. So,
6912
- # for example, if you change a rule action setting, the action might be
6913
- # the old action in one area and the new action in another area. Or if
6914
- # you add an IP address to an IP set used in a blocking rule, the new
6915
- # address might briefly be blocked in one area while still allowed in
6916
- # another. This temporary inconsistency can occur when you first
6917
- # associate a web ACL with an Amazon Web Services resource and when you
6918
- # change a web ACL that is already associated with a resource.
6919
- # Generally, any inconsistencies of this type last only a few seconds.
6920
- #
6921
6989
  # A rule group defines a collection of rules to inspect and control web
6922
6990
  # requests that you can use in a WebACL. When you create a rule group,
6923
6991
  # you define an immutable capacity limit. If you update a rule group,
6924
6992
  # you must stay within the capacity. This allows others to reuse the
6925
6993
  # rule group with confidence in its capacity requirements.
6926
6994
  #
6995
+ # **Temporary inconsistencies during updates**
6996
+ #
6997
+ # When you create or change a web ACL or other WAF resources, the
6998
+ # changes take a small amount of time to propagate to all areas where
6999
+ # the resources are stored. The propagation time can be from a few
7000
+ # seconds to a number of minutes.
7001
+ #
7002
+ # The following are examples of the temporary inconsistencies that you
7003
+ # might notice during change propagation:
7004
+ #
7005
+ # * After you create a web ACL, if you try to associate it with a
7006
+ # resource, you might get an exception indicating that the web ACL is
7007
+ # unavailable.
7008
+ #
7009
+ # * After you add a rule group to a web ACL, the new rule group rules
7010
+ # might be in effect in one area where the web ACL is used and not in
7011
+ # another.
7012
+ #
7013
+ # * After you change a rule action setting, you might see the old action
7014
+ # in some places and the new action in others.
7015
+ #
7016
+ # * After you add an IP address to an IP set that is in use in a
7017
+ # blocking rule, the new address might be blocked in one area while
7018
+ # still allowed in another.
7019
+ #
6927
7020
  # @option params [required, String] :name
6928
7021
  # The name of the rule group. You cannot change the name of a rule group
6929
7022
  # after you create it.
@@ -7867,20 +7960,6 @@ module Aws::WAFV2
7867
7960
  #
7868
7961
  # </note>
7869
7962
  #
7870
- # When you make changes to web ACLs or web ACL components, like rules
7871
- # and rule groups, WAF propagates the changes everywhere that the web
7872
- # ACL and its components are stored and used. Your changes are applied
7873
- # within seconds, but there might be a brief period of inconsistency
7874
- # when the changes have arrived in some places and not in others. So,
7875
- # for example, if you change a rule action setting, the action might be
7876
- # the old action in one area and the new action in another area. Or if
7877
- # you add an IP address to an IP set used in a blocking rule, the new
7878
- # address might briefly be blocked in one area while still allowed in
7879
- # another. This temporary inconsistency can occur when you first
7880
- # associate a web ACL with an Amazon Web Services resource and when you
7881
- # change a web ACL that is already associated with a resource.
7882
- # Generally, any inconsistencies of this type last only a few seconds.
7883
- #
7884
7963
  # A web ACL defines a collection of rules to use to inspect and control
7885
7964
  # web requests. Each rule has a statement that defines what to look for
7886
7965
  # in web requests and an action that WAF applies to requests that match
@@ -7894,6 +7973,31 @@ module Aws::WAFV2
7894
7973
  # Cognito user pool, an App Runner service, or an Amazon Web Services
7895
7974
  # Verified Access instance.
7896
7975
  #
7976
+ # **Temporary inconsistencies during updates**
7977
+ #
7978
+ # When you create or change a web ACL or other WAF resources, the
7979
+ # changes take a small amount of time to propagate to all areas where
7980
+ # the resources are stored. The propagation time can be from a few
7981
+ # seconds to a number of minutes.
7982
+ #
7983
+ # The following are examples of the temporary inconsistencies that you
7984
+ # might notice during change propagation:
7985
+ #
7986
+ # * After you create a web ACL, if you try to associate it with a
7987
+ # resource, you might get an exception indicating that the web ACL is
7988
+ # unavailable.
7989
+ #
7990
+ # * After you add a rule group to a web ACL, the new rule group rules
7991
+ # might be in effect in one area where the web ACL is used and not in
7992
+ # another.
7993
+ #
7994
+ # * After you change a rule action setting, you might see the old action
7995
+ # in some places and the new action in others.
7996
+ #
7997
+ # * After you add an IP address to an IP set that is in use in a
7998
+ # blocking rule, the new address might be blocked in one area while
7999
+ # still allowed in another.
8000
+ #
7897
8001
  # @option params [required, String] :name
7898
8002
  # The name of the web ACL. You cannot change the name of a web ACL after
7899
8003
  # you create it.
@@ -8922,7 +9026,7 @@ module Aws::WAFV2
8922
9026
  params: params,
8923
9027
  config: config)
8924
9028
  context[:gem_name] = 'aws-sdk-wafv2'
8925
- context[:gem_version] = '1.70.0'
9029
+ context[:gem_version] = '1.72.0'
8926
9030
  Seahorse::Client::Request.new(handlers, context)
8927
9031
  end
8928
9032
 
@@ -32,7 +32,7 @@ module Aws::WAFV2
32
32
  raise ArgumentError, "FIPS and DualStack are enabled, but this partition does not support one or both"
33
33
  end
34
34
  if Aws::Endpoints::Matchers.boolean_equals?(use_fips, true)
35
- if Aws::Endpoints::Matchers.boolean_equals?(true, Aws::Endpoints::Matchers.attr(partition_result, "supportsFIPS"))
35
+ if Aws::Endpoints::Matchers.boolean_equals?(Aws::Endpoints::Matchers.attr(partition_result, "supportsFIPS"), true)
36
36
  return Aws::Endpoints::Endpoint.new(url: "https://wafv2-fips.#{region}.#{partition_result['dnsSuffix']}", headers: {}, properties: {})
37
37
  end
38
38
  raise ArgumentError, "FIPS is enabled but this partition does not support FIPS"
@@ -542,14 +542,21 @@ module Aws::WAFV2
542
542
  # * `UriPath`: The value that you want WAF to search for in the URI
543
543
  # path, for example, `/images/daily-ad.jpg`.
544
544
  #
545
- # * `JA3Fingerprint`: The string to match against the web request's
546
- # JA3 fingerprint header. The header contains a hash fingerprint of
547
- # the TLS Client Hello packet for the request.
548
- #
549
- # * `HeaderOrder`: The comma-separated list of header names to match
550
- # for. WAF creates a string that contains the ordered list of header
551
- # names, from the headers in the web request, and then matches
552
- # against that string.
545
+ # * `JA3Fingerprint`: Match against the request's JA3 fingerprint.
546
+ # The JA3 fingerprint is a 32-character hash derived from the TLS
547
+ # Client Hello of an incoming request. This fingerprint serves as a
548
+ # unique identifier for the client's TLS configuration. You can use
549
+ # this choice only with a string match `ByteMatchStatement` with the
550
+ # `PositionalConstraint` set to `EXACTLY`.
551
+ #
552
+ # You can obtain the JA3 fingerprint for client requests from the
553
+ # web ACL logs. If WAF is able to calculate the fingerprint, it
554
+ # includes it in the logs. For information about the logging fields,
555
+ # see [Log fields][1] in the *WAF Developer Guide*.
556
+ #
557
+ # * `HeaderOrder`: The list of header names to match for. WAF creates
558
+ # a string that contains the ordered list of header names, from the
559
+ # headers in the web request, and then matches against that string.
553
560
  #
554
561
  # If `SearchString` includes alphabetic characters A-Z and a-z, note
555
562
  # that the value is case sensitive.
@@ -569,6 +576,10 @@ module Aws::WAFV2
569
576
  #
570
577
  # The value that you want WAF to search for. The SDK automatically
571
578
  # base64 encodes the value.
579
+ #
580
+ #
581
+ #
582
+ # [1]: https://docs.aws.amazon.com/waf/latest/developerguide/logging-fields.html
572
583
  # @return [String]
573
584
  #
574
585
  # @!attribute [rw] field_to_match
@@ -966,7 +977,14 @@ module Aws::WAFV2
966
977
  #
967
978
  # @!attribute [rw] match_scope
968
979
  # The parts of the cookies to inspect with the rule inspection
969
- # criteria. If you specify `All`, WAF inspects both keys and values.
980
+ # criteria. If you specify `ALL`, WAF inspects both keys and values.
981
+ #
982
+ # `All` does not require a match to be found in the keys and a match
983
+ # to be found in the values. It requires a match to be found in the
984
+ # keys or the values or both. To require a match in the keys and in
985
+ # the values, use a logical `AND` statement to combine two match
986
+ # rules, one that inspects the keys and another that inspects the
987
+ # values.
970
988
  # @return [String]
971
989
  #
972
990
  # @!attribute [rw] oversize_handling
@@ -2397,15 +2415,32 @@ module Aws::WAFV2
2397
2415
  # @return [Types::HeaderOrder]
2398
2416
  #
2399
2417
  # @!attribute [rw] ja3_fingerprint
2400
- # Match against the request's JA3 fingerprint header. The header
2401
- # contains a hash fingerprint of the TLS Client Hello packet for the
2402
- # request.
2418
+ # Match against the request's JA3 fingerprint. The JA3 fingerprint is
2419
+ # a 32-character hash derived from the TLS Client Hello of an incoming
2420
+ # request. This fingerprint serves as a unique identifier for the
2421
+ # client's TLS configuration. WAF calculates and logs this
2422
+ # fingerprint for each request that has enough TLS Client Hello
2423
+ # information for the calculation. Almost all web requests include
2424
+ # this information.
2403
2425
  #
2404
2426
  # <note markdown="1"> You can use this choice only with a string match
2405
2427
  # `ByteMatchStatement` with the `PositionalConstraint` set to
2406
2428
  # `EXACTLY`.
2407
2429
  #
2408
2430
  # </note>
2431
+ #
2432
+ # You can obtain the JA3 fingerprint for client requests from the web
2433
+ # ACL logs. If WAF is able to calculate the fingerprint, it includes
2434
+ # it in the logs. For information about the logging fields, see [Log
2435
+ # fields][1] in the *WAF Developer Guide*.
2436
+ #
2437
+ # Provide the JA3 fingerprint string from the logs in your string
2438
+ # match statement specification, to match with any future requests
2439
+ # that have the same TLS configuration.
2440
+ #
2441
+ #
2442
+ #
2443
+ # [1]: https://docs.aws.amazon.com/waf/latest/developerguide/logging-fields.html
2409
2444
  # @return [Types::JA3Fingerprint]
2410
2445
  #
2411
2446
  # @see http://docs.aws.amazon.com/goto/WebAPI/wafv2-2019-07-29/FieldToMatch AWS API Documentation
@@ -3532,7 +3567,14 @@ module Aws::WAFV2
3532
3567
  #
3533
3568
  # @!attribute [rw] match_scope
3534
3569
  # The parts of the headers to match with the rule inspection criteria.
3535
- # If you specify `All`, WAF inspects both keys and values.
3570
+ # If you specify `ALL`, WAF inspects both keys and values.
3571
+ #
3572
+ # `All` does not require a match to be found in the keys and a match
3573
+ # to be found in the values. It requires a match to be found in the
3574
+ # keys or the values or both. To require a match in the keys and in
3575
+ # the values, use a logical `AND` statement to combine two match
3576
+ # rules, one that inspects the keys and another that inspects the
3577
+ # values.
3536
3578
  # @return [String]
3537
3579
  #
3538
3580
  # @!attribute [rw] oversize_handling
@@ -3832,15 +3874,31 @@ module Aws::WAFV2
3832
3874
  include Aws::Structure
3833
3875
  end
3834
3876
 
3835
- # Match against the request's JA3 fingerprint header. The header
3836
- # contains a hash fingerprint of the TLS Client Hello packet for the
3837
- # request.
3877
+ # Match against the request's JA3 fingerprint. The JA3 fingerprint is a
3878
+ # 32-character hash derived from the TLS Client Hello of an incoming
3879
+ # request. This fingerprint serves as a unique identifier for the
3880
+ # client's TLS configuration. WAF calculates and logs this fingerprint
3881
+ # for each request that has enough TLS Client Hello information for the
3882
+ # calculation. Almost all web requests include this information.
3838
3883
  #
3839
3884
  # <note markdown="1"> You can use this choice only with a string match `ByteMatchStatement`
3840
3885
  # with the `PositionalConstraint` set to `EXACTLY`.
3841
3886
  #
3842
3887
  # </note>
3843
3888
  #
3889
+ # You can obtain the JA3 fingerprint for client requests from the web
3890
+ # ACL logs. If WAF is able to calculate the fingerprint, it includes it
3891
+ # in the logs. For information about the logging fields, see [Log
3892
+ # fields][1] in the *WAF Developer Guide*.
3893
+ #
3894
+ # Provide the JA3 fingerprint string from the logs in your string match
3895
+ # statement specification, to match with any future requests that have
3896
+ # the same TLS configuration.
3897
+ #
3898
+ #
3899
+ #
3900
+ # [1]: https://docs.aws.amazon.com/waf/latest/developerguide/logging-fields.html
3901
+ #
3844
3902
  # @!attribute [rw] fallback_behavior
3845
3903
  # The match status to assign to the web request if the request
3846
3904
  # doesn't have a JA3 fingerprint.
@@ -3883,7 +3941,14 @@ module Aws::WAFV2
3883
3941
  #
3884
3942
  # @!attribute [rw] match_scope
3885
3943
  # The parts of the JSON to match against using the `MatchPattern`. If
3886
- # you specify `All`, WAF matches against keys and values.
3944
+ # you specify `ALL`, WAF matches against keys and values.
3945
+ #
3946
+ # `All` does not require a match to be found in the keys and a match
3947
+ # to be found in the values. It requires a match to be found in the
3948
+ # keys or the values or both. To require a match in the keys and in
3949
+ # the values, use a logical `AND` statement to combine two match
3950
+ # rules, one that inspects the keys and another that inspects the
3951
+ # values.
3887
3952
  # @return [String]
3888
3953
  #
3889
3954
  # @!attribute [rw] invalid_fallback_behavior
data/lib/aws-sdk-wafv2.rb CHANGED
@@ -52,6 +52,6 @@ require_relative 'aws-sdk-wafv2/customizations'
52
52
  # @!group service
53
53
  module Aws::WAFV2
54
54
 
55
- GEM_VERSION = '1.70.0'
55
+ GEM_VERSION = '1.72.0'
56
56
 
57
57
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-wafv2
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.70.0
4
+ version: 1.72.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-09-27 00:00:00.000000000 Z
11
+ date: 2023-10-27 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core