- Newest
- Most votes
- Most comments
The "Load Balancer Type" section being greyed out in the 'Instance traffic and scaling' configuration is an expected behaviour, it's because the Load Balancer Type cannot be changed once the environment is created.[1]
Now moving forward, with your query of configuring a HTTPS listener on the Classic Load Balanced environment, you can refer the detailed steps below :
1.) Goto "Listeners" section present under the 'Load Balancer Type' section of the 'Instance traffic and scaling' configuration.
2.) Then, click on the 'Add listener' button, and enter the below values in the 'Add listener' dialog box appeared on the screen :
- For Listener port, type the incoming traffic port, typically 443.
- For Listener protocol, choose HTTPS.
- For Instance port, type 80.
- For Instance protocol, choose HTTP.
- For SSL certificate, choose your certificate.
3.) Click on 'Save' button on the dialog box, and then click on Apply button at the bottom, which will trigger an environment configuration update.
I have also shared the screenshots of the aforementioned steps for your reference.
++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++
Note :
- I have created a Sample Beanstalk environment (using Classic Load Balancer) on the platform 'Node.js 18 running on 64bit Amazon Linux 2/5.8.2' in 'us-east-1' region using EBCLI. Also, for AWS Support to have better visibility into the concerned resources, you can open a support case with us to have personalized guidance.
Reference :
[1] Load balancer for your Elastic Beanstalk environment - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.elb.html
Relevant content
- asked a year ago
- asked 2 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 18 days ago
- AWS OFFICIALUpdated 9 months ago