0

I have an EMR cluster configured with the following SecurityConfiguration:


"AuthenticationConfiguration": {
  "IdentityCenterConfiguration": {
    "EnableIdentityCenter": true
  }
},
"AuthorizationConfiguration": {
  "LakeFormationConfiguration": {
    "EnableLakeFormation": true
  }
}

After enabling above configuration, I can no longer access Livy (port 8998) from web ui or even from the master node of emr cluster reaching the standard REST API (/sessions endpoint) by curl.

I'm trying to query existing Livy sessions (e.g., via GET /sessions) either anonymously or by using GetClusterSessionCredentials, but everything fails.

How I can deal with livy in this case, because livy after such changes have secretagent-authentication type of authintication and it's not clear how I can now connect to it.


livy.server.auth.type = secretagent-authentication
livy.server.auth.secretagent-authentication.class = org.apache.hadoop.security.authentication.server.AuthenticationFilter
livy.server.auth.secretagent-authentication.param.type = com.amazonaws.emr.secretagent.connector.livy.LivySecretAgentAuthenticationHandlerImpl
livy.server.access-control.enabled = true

I I will disable IdentityCenterConfiguration it works fine, but I'm not allowed to do it because it's needed for other components.

1
  • Did you created authentication header, as, after SSO enabled on EMR needs different approach for Auth.. Commented Jun 4 at 16:41

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.