I am trying to get an EMR Studio running on an existing EKS cluster by following the instructions here: https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-studio-create-eks-cluster.html
Most of those steps went smoothly, but the issue occurred when I tried to create a managed endpoint with the following command:
aws emr-containers create-managed-endpoint --name [ENDPOINT_NAME] --virtual-cluster-id [VIRTUAL_CLUSTER_ID] --type JUPYTER_ENTERPRISE_GATEWAY --release-label emr-6.2.0-latest --execution-role-arn [EXECUTION_ROLE_ARN] --certificate-arn [CERTIFICATE_ARN]
The endpoint has been created, it stayed in CREATING status for a few minutes, then it terminated, without giving any clues what might be the problem.
The result of listing the endpoints is the following:
{
"id": "2w5v7j307hut1",
"name": "ENDPOINT_NAME",
"arn": "ENDPOINT_ARN",
"virtualClusterId": "VIRTUAL_CLUSTER_ID",
"type": "JUPYTER_ENTERPRISE_GATEWAY",
"state": "TERMINATED_WITH_ERRORS",
"releaseLabel": "emr-6.2.0-latest",
"executionRoleArn": "EXECUTION_ROLE_ARN",
"certificateArn": "CERTIFICATE_ARN",
"createdAt": "2022-05-09T19:58:21+00:00",
"stateDetails": "Unknown",
"failureReason": "INTERNAL_ERROR",
"tags": {}
},
Could anyone give some suggestions how to troubleshoot this? Is there a way to access logs to figure out what could be wrong?
Thanks a lot!
Simon
Simon did you ever figure this out? Hitting same issue....
Curious if you figured out what the issue was.
Hi, hitting same issue. did you manage to get any hint about the issue?
In my case it was that this doesn't support EKS v1.22. Supports suggestion was to rebuild the cluster as v1.21