get_logging_configuration
¶
get_logging_configuration(
resource_arn: ResourceArn,
*,
config_overrides: Optional[WAFV2ClientConfig] = None,
log_type: Optional[LogType] = None,
log_scope: Optional[LogScope] = None,
) -> GetLoggingConfigurationResponse
Returns the LoggingConfiguration for the specified web ACL.
Parameters:
-
resource_arn(ResourceArn) –The Amazon Resource Name (ARN) of the web ACL for which you want to get the LoggingConfiguration.
-
log_type(Optional[LogType], default:None) –Used to distinguish between various logging options. Currently, there is one option.
Default:
WAF_LOGS -
log_scope(Optional[LogScope], default:None) –The owner of the logging configuration, which must be set to
CUSTOMERfor the configurations that you manage.The log scope
SECURITY_LAKEindicates a configuration that is managed through Amazon Security Lake. You can use Security Lake to collect log and event data from various sources for normalization, analysis, and management. For information, see Collecting data from Amazon Web Services services in the Amazon Security Lake user guide.The log scope
CLOUDWATCH_TELEMETRY_RULE_MANAGEDindicates a configuration that is managed through Amazon CloudWatch Logs for telemetry data collection and analysis. For information, see What is Amazon CloudWatch Logs ? in the Amazon CloudWatch Logs user guide.Default:
CUSTOMER
Raises:
-
WAFInternalErrorException–Your request is valid, but WAF couldn’t perform the operation because of a system problem. Retry your request.
-
WAFInvalidOperationException–The operation isn't valid.
-
WAFInvalidParameterException–The operation failed because WAF didn't recognize a parameter in the request. For example:
-
You specified a parameter name or value that isn't valid.
-
Your nested statement isn't valid. You might have tried to nest a statement that can’t be nested.
-
You tried to update a
WebACLwith aDefaultActionthat isn't among the types available at DefaultAction. -
Your request references an ARN that is malformed, or corresponds to a resource with which a web ACL can't be associated.
-
-
WAFNonexistentItemException–WAF couldn’t perform the operation because your resource doesn't exist. If you've just created a resource that you're using in this operation, you might just need to wait a few minutes. It can take from a few seconds to a number of minutes for changes to propagate.
-
UnknownServiceError–The service returned an error code this client does not model.