Skip to content

S3LoggingConfiguration

Source code in docs_src/capo_emr/types/s3_logging_configuration.py 
11
12
13
class S3LoggingConfiguration(TypedDict, closed=True):
    log_type_upload_policy: NotRequired["capo_emr.types.log_type_map.LogTypeMap"]
    """<p>A map that specifies the upload policy for each log type. The key is the log type, and the value is the upload policy.</p> <p>Valid log types:</p> <ul> <li> <p> <code>system-logs</code>: EMR Daemon logs.</p> </li> <li> <p> <code>application-logs</code>: Framework logs from Hadoop, Spark, Hive and other applications running on the cluster.</p> </li> <li> <p> <code>persistent-ui-logs</code>: Logs required for persistent application UIs such as Spark History Server and Tez UI.</p> </li> </ul> <p>Valid upload policies:</p> <ul> <li> <p> <code>emr-managed</code>: Standard behavior. Logs are uploaded to S3 bucket as configured in your LogUri, with certain logs retained by the service for operational support and troubleshooting purposes.</p> </li> <li> <p> <code>on-customer-s3only</code>: Logs are uploaded only to the customer-specified S3 bucket. This requires you to specify a LogUri when creating the cluster. Persistent-ui-logs cannot have on-customer-s3only policy. Allowed policies for persistent-ui-logs are emr-managed and disabled.</p> </li> <li> <p> <code>disabled</code>: No S3 upload for this log type.</p> </li> </ul>"""

log_type_upload_policy instance-attribute 

log_type_upload_policy: NotRequired[LogTypeMap]

A map that specifies the upload policy for each log type. The key is the log type, and the value is the upload policy.

Valid log types:

  • system-logs: EMR Daemon logs.

  • application-logs: Framework logs from Hadoop, Spark, Hive and other applications running on the cluster.

  • persistent-ui-logs: Logs required for persistent application UIs such as Spark History Server and Tez UI.

Valid upload policies:

  • emr-managed: Standard behavior. Logs are uploaded to S3 bucket as configured in your LogUri, with certain logs retained by the service for operational support and troubleshooting purposes.

  • on-customer-s3only: Logs are uploaded only to the customer-specified S3 bucket. This requires you to specify a LogUri when creating the cluster. Persistent-ui-logs cannot have on-customer-s3only policy. Allowed policies for persistent-ui-logs are emr-managed and disabled.

  • disabled: No S3 upload for this log type.