Interface S3LoggingConfiguration.Builder

All Superinterfaces:
Buildable, CopyableBuilder<S3LoggingConfiguration.Builder,S3LoggingConfiguration>, SdkBuilder<S3LoggingConfiguration.Builder,S3LoggingConfiguration>, SdkPojo
Enclosing class:
S3LoggingConfiguration
@Mutable @NotThreadSafe public static interface S3LoggingConfiguration.Builder extends SdkPojo, CopyableBuilder<S3LoggingConfiguration.Builder,S3LoggingConfiguration>

  • Method Details

    • logTypeUploadPolicyWithStrings

      S3LoggingConfiguration.Builder logTypeUploadPolicyWithStrings(Map<String,String> logTypeUploadPolicy)

      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.

      Parameters:
      logTypeUploadPolicy - 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.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • logTypeUploadPolicy

      S3LoggingConfiguration.Builder logTypeUploadPolicy(Map<LogType,LogUploadPolicyValue> logTypeUploadPolicy)

      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.

      Parameters:
      logTypeUploadPolicy - 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.

      Returns:
      Returns a reference to this object so that method calls can be chained together.