AWS – Upgrade Elastic Beanstalk Load Balancer from Classic to Application

I think you need to specify what Elastic Beanstalk environment that you use (see: Supported Platforms), because different environment has different configuration.

Basically, you need to customize:

• Elastic Load Balancer:
  • Listen on port 80 and proxy it to EC2 instance port 80.
  • Listen on port 443 and proxy it to EC2 instance port 443.
• EC2 Web Server/Proxy:
  • Listen on port 80 and response with redirect to HTTPS.
  • Listen on port 443 and serve the request.

To customized it, you can use CLI or .ebextensions.

You can check on Enable HTTPS and HTTP-Redirect on AWS Elastic Beanstalk. It tells you how to configure Elastic Beanstalk Single Docker Container serve HTTPS and HTTP (redirect to HTTPS). You can adjust the config as your need.

You don't do this by disabling http access.

You do this in your instance's web server. When a request comes in without the X-Forwarded-Proto: https header that ELB adds when the incoming request came in over https, your web servers need to send a HTTP/1.1 301 Moved Permanently redirect to the browser, specifying Location: https://... in the response.

There is no way for a new visitor's browser to automagically know it should retry with https unless your application tells it to.

There are alternative, more advanced ways to accomplish this but they still do not involve ELB (elastic load balancer) or EB (elastic beanstalk) or security group configuration.