3

We have one app deployed on an EC2 instance that can communicate inbound/outbound using HTTP, TCP, and UDP protocols.

One option could be to have an ALB for HTTP traffic and an NLB for TCP, UDP traffic.

The challenge is that the application allows the configuration of a single target FQDN so we can't target both the NLB and ALB based on the protocol.

As we don't want to go to classic ELB I'm wondering how others implemented a solution for similar challenges. Would AWS Global Accelerator help in such a case?

Lucian Revnic
  • 31
  • 3
  • Why won't an NLB work for your HTTP traffic? Are there specific features of the ALB you need for the HTTP traffic? – Mark B Mar 31 '21 at 14:56
  • It does look like AWS Global Accelerator would solve this problem. – Mark B Mar 31 '21 at 15:04
  • Thank you @MarkB, indeed behind the ALB there are other instances receiving/sending HTTP traffic and are already attached to the ALB. – Lucian Revnic Mar 31 '21 at 18:50

0 Answers0