AWS Application Load Balancer (ALB) in absence of Web Adaptor

[Ranga_Tolapi]

Q1: How to achieve the below behavior using ALB (without Web Adaptor)?

1. Portal:
   • End point URL: https://lb.domain.com/portal/*
   • Internal URL: https://portalmachine.domain.com:7443/arcgis/*
2. Federated Server:
   • End point URL: https://lb.domain.com/arcgis/*
   • Internal URL: https://federatedservermachine.domain.com:6443/arcgis/*
3. Hosted Server:
   • End point URL: https://lb.domain.com/server/*
   • Internal URL: https://hostedservermachine.domain.com:6443/arcgis/*

Q2: How to set X-Forwarded-Host header in ALB?

Q3: How to detect redirects (HTTP codes 301 or 302) and update its Location header to ensure that the fully qualified domain name (FQDN) and context of the response match the server's WebContextURL value?

Appreciate your advises please.

[ReeseFacendini · Accepted solution]

1) When using ALBs instead of ArcGIS Web Adaptors, the web context becomes "arcgis" and you would end up with the URLs below:

• https://portalLB.domain.com/arcgis/*
• https://federatedLB.domain.com/arcgis/* 
• https://hostingLB.domain.com/arcgis/*

There is not a way to leverage ALBs but have the context be /portal, /hosting, etc. In order to choose the web context, you would need to leverage ArcGIS Web Adaptors.

2) ALBs don't support X-Forwarded-Host (or custom headers in the first place), which is why the URLs above have to have to context of /arcgis, instead of /portal, /server, etc. (corrected answer)

[Ranga_Tolapi]

Thank you so much @ReeseFacendini, highly appreciated.