One ALB, one HTTPS listener, one TG - can I have both authorised requests with Cognito and Non-authorised requests?


Hi, can someone please let me know if this is a viable solution and if it's even possible. I have an Application Load Balancer sitting in front of my Target Group which is linked to my ECS Cluster where I have deployed a monolith that contains frontend user routing that doesn't require authentication as well as admin routing that does require authentication. Lets say my load balancer is - can I still use Cognito as an IdP where I have for example a path condition based rules on my listener that check whether the request is (1) or (2) and if its (1) the request doesn't need to be authenticated and gets forwarded to the target group whereas if its (2) the request does need to be authenticated first and then forwarded to the target group.

Once the request reaches the target group then the routing authentication logic will verify the token or whatever for the admin paths.

Is this reasonable/viable , can it work or its not really how things are done?

1 Risposta
Risposta accettata


I think what you want to do is probably possible.
I think it's okay if you create a listener rule that sets Cognito authentication in the case of "/admin/*" and does not set Cognito authentication in other cases.

The article below is in Japanese, but it explains what you want to do.

profile picture
con risposta 4 mesi fa
  • Thanks this is a really helpful answer - and I was able to translate the Japanese article to English with Google Translate so that was also quite helpful to see that someone has actually done this and wrote about it!

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande