[jira] [Commented] (KNOX-1334) Knox on AWS EMR

["Mert Hocanin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KNOX-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530661#comment-16530661 ] 

Mert Hocanin commented on KNOX-1334:
------------------------------------

I have attached a patch that makes several changes to the rewrite rules for Jobhistory, NodeManagerUI, and YarnUI for an instance of KNOX that works for EMR's configuration. I would love for someone to review and let me know if there is anything I can do to improve it. I tried to apply this patch to the latest master branch and there were no conflicts. Thanks!

> Knox on AWS EMR
> ---------------
>
>                 Key: KNOX-1334
>                 URL: https://issues.apache.org/jira/browse/KNOX-1334
>             Project: Apache Knox
>          Issue Type: Bug
>            Reporter: PRAVEEN K RAVIKUMAR
>            Priority: Major
>         Attachments: KNOX-1343.patch
>
>
> Hi
> I have requirement to send all the request coming to proxy to be forwarded to EMR master node.
> Example:
> https://<any dns-name>:<PORT>/ --> Proxy --> EMR master.
> The DNS name could be anything, because there are many slave nodes. I would like the proxy to "redirect" dynamically "https://<any dns-name>:<PORT>/" to EMR master host. Could you please let me know if a reverse proxy/ Apache Knox can do that. I am trying to mimic option2 "SSH Tunnel to the Master Node Using Dynamic Port Forwarding"
> https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-ssh-tunnel.html
> Sample URLS:
> YARN ResourceManager https://master-public-dns-name:8088/ YARN NodeManager https://slave-public-dns-name:8042/ Spark HistoryServer https://master-public-dns-name:18080/
> [https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-ssh-tunnel.html]
>  
> If so could you please share me the steps to configure Knox on EMR cluster- would be very helpful?
> Praveen.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)