Compliance requirements state that all communications between company on-premises hosts and EC2 instances be encrypted in transit. Hosts use custom proprietary protocols for their communication, and…

Question

Options

• AOffload SSL termination onto an SSL listener on a Classic Load Balancer, and use a TCP
• BRoute all traffic through a TCP listener on a Classic Load Balancer, and terminate the TLS
• CCreate an HTTPS listener using an Application Load Balancer, and route all of the communication
• DOffload SSL termination onto an SSL listener using an Application Load Balancer, and re-spawn

• A
  4% (1)
• B
  76% (19)
• C
  4% (1)
• D
  16% (4)

Explanation

If you use HTTPS or SSL for your front-end connections, you must deploy an X.509 certificate (SSL server certificate) on your load balancer. The load balancer decrypts requests from clients before sending them to the back-end instances (known as SSL termination). For more information, see SSL/TLS Certificates for Classic Load Balancers. If you don't want the load balancer to handle the SSL termination (known as SSL offloading), you can use TCP for both the front-end and back-end connections, and deploy certificates on the registered instances handling requests. https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-listener-config.html

No community discussion yet for this question.