Ran into an issue associated with a recent attempt to leverage an on-prem solution, tactically, by duplicating the functionality in AWS (while in the process of migrating DC svcs into the cloud): the on-prem egress Internet access happens via Bluecoats, with authentication, behind F5, and by-pass (where auth is not possible) via X-Forwarded-For headers + whitelisting of IPs belonging to systems not supporting auth, on the Bluecoats.
The AWS solution leveraging ELB fails to provide the necessary functionality for X-Forwared-For headers, when servicing Bluecoats. Any similar experience / ideas on how to resolve this, short of standing up F5 in AWS?
No comments:
Post a Comment