[
https://issues.apache.org/jira/browse/NIFI-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250279#comment-17250279
]
Ruben Laguna commented on NIFI-3882:
------------------------------------
I guess, that it was really terminating the HTTPS for the NiFI UI, which is
possible already today.
What is not possible (IMHO) is to do it reliably due to the lack of a /health
endpoint that allows the load balancer to check if the node is ready to accept
UI requests.
I've reported this in https://issues.apache.org/jira/browse/NIFI-8100. The
gist is that for AWS Load Balancer we need an endpoint that does NOT require
authentication and that gives a 4xx-5xx http status code if the node is
disconnected (not part of the cluster).
> Unable to run NiFi behind AWS Load Balancer
> -------------------------------------------
>
> Key: NIFI-3882
> URL: https://issues.apache.org/jira/browse/NIFI-3882
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Richard St. John
> Priority: Major
>
> Running Apache NiFi behind an AWS Elastic Load Balancer fails.
> Upon closer inspection, AWS Elastic Load Balancers only support the following
> headers:
> X-Forwarded-For
> X-Forwarded-Proto
> X-Forwarded-Port
> In our case, we would like our ELB to be HTTPS enabled, but our NiFi cluster
> is running in a trusted environment on port 8080.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
