Saw this issue in Jira. It seems pretty important and the fix would be relatively easy. I believe.
https://issues.apache.org/jira/browse/NIFI-3882 Wouldn't the fix be to check for both the AWS provided http header and the existing ones to provide compatibility? That would fix the scheme and the port. Not sure how to handle the hostname. Maybe add a new configuration that allows the user to set the hostname if its not available via the header? -- Cheers, Edgardo
