PutLoggingConfiguration (smaws-clients.Smaws_Client

val request : 
  Smaws_Lib.Context.t ->
  put_logging_configuration_request ->
  (put_logging_configuration_response,
    [> Smaws_Lib.Protocols.AwsJson.error
    | `WAFInternalErrorException of waf_internal_error_exception
    | `WAFNonexistentItemException of waf_nonexistent_item_exception
    | `WAFServiceLinkedRoleErrorException of
      waf_service_linked_role_error_exception
    | `WAFStaleDataException of waf_stale_data_exception ])
    Stdlib.result

This is AWS WAF Classic documentation. For more information, see AWS WAF Classic in the developer guide.

For the latest version of AWS WAF, use the AWS WAFV2 API and see the AWS WAF Developer Guide. With the latest version, AWS WAF has a single set of endpoints for regional and global use.

Associates a LoggingConfiguration with a specified web ACL.

You can access information about all traffic that AWS WAF inspects using the following steps:

Create an Amazon Kinesis Data Firehose.
Create the data firehose with a PUT source and in the region that you are operating. However, if you are capturing logs for Amazon CloudFront, always create the firehose in US East (N. Virginia).
Do not create the data firehose using a Kinesis stream as your source.
Associate that firehose to your web ACL using a PutLoggingConfiguration request.

When you successfully enable logging using a PutLoggingConfiguration request, AWS WAF will create a service linked role with the necessary permissions to write logs to the Amazon Kinesis Data Firehose. For more information, see Logging Web ACL Traffic Information in the AWS WAF Developer Guide.