Skip to content

Latest commit

 

History

History
 
 

tez-ui

README.md

Tez UI

You can use this Docker image to start the Tez UI and Application Timeline Server and view the Tez UI locally.

Pre-requisite

  • Install Docker

Build Docker image

  1. Clone this repository and change into the utilities/tez-ui directory.
git clone https://github.com/aws-samples/emr-serverless-samples.git
cd emr-serverless-samples/utilities/tez-ui/
  1. Build the image
docker build -t emr/tez-ui .

Start the Tez UI

You can use a pair of AWS access key and secret key, or temporary AWS credentials. These credentials should have access to the S3 log bucket. If encryption is enabled for the logs stored in the S3 bucket, these credentials should have access to the necessary KMS key as well.

  1. Set a few environment variables relevant to your job.
export APPLICATION_ID=001122334455
export JOB_RUN_ID=667788990011
CONTAINER_LOG_BASE_PATH=hive-logs
export S3_LOG_URI=s3://$S3_BUCKET/$CONTAINER_LOG_BASE_PATH
export AWS_CONSOLE_BASE_PATH_URL="https://s3.console.aws.amazon.com/s3/buckets/${S3_BUCKET}?prefix=${CONTAINER_LOG_BASE_PATH}/applications/${APPLICATION_ID}/jobs/${JOB_RUN_ID}"
  1. Set your AWS access key and secret key, and optionally session token.
export AWS_ACCESS_KEY_ID="ASIAxxxxxxxxxxxx"
export AWS_SECRET_ACCESS_KEY="yyyyyyyyyyyyyyy"
export AWS_SESSION_TOKEN="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
  1. Run the Docker image
docker run --rm -it \
    -p 8088:8088 -p 8188:8188 -p 9999:9999 \
    -e AWS_REGION=us-east-1 -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN \
    -e S3_LOG_URI -e JOB_RUN_ID -e APPLICATION_ID -e AWS_CONSOLE_BASE_PATH_URL \
    emr/tez-ui
  1. Access the Tez UI via http://localhost:9999/tez-ui/

Troubleshooting

You may get following exception during TEZ UI startup.

  1. Issue/Exception: com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.services.s3.model.AmazonS3Exception: The ciphertext refers to a customer master key that does not exist, does not exist in this region, or you are not allowed to access. (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied)

    Reason: Given user credentials may not have the access to KMS key which is used to encrypt the logs in the S3 bucket. Add KMS policy with decrypt permission and verify.

  2. Issue/Exception: com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied)

    Reason: Given user credentials may not have the access the S3 bucket. Add S3 policy with read permission and verify.