CodeCommit stops working after adding HTTPS listener to Elastic Beanstalk environment

Hello Forum, I added an HTTPS listener to my Elastic Beanstalk environment on AWS to enhance security. However, I've encountered an unexpected issue where my CodeCommit repository seems to have stopped working properly. Prior to adding the HTTPS listener, everything was functioning as expected.

I have configured a certificate for my custom domain and added CNAME record in the DNS Route 53, it verified my certificate. Then I switched Environment type from "Single Instance" to "Load Balanced", after this I added listener to HTTPS with certificate created, I defined port to 443. Everything worked, website indeed got an https connection, but when I tried to deploy changes I made on my local machine to Elastic Beanstalk, it was loading over 10 minutes then in my VS terminal I got error that stated that time limit was exceeded since it was over 10 minutes, and inside my AWS EB I got this message: "Environment health has transitioned from No Data to Info. Application update in progress on 1 instance. 0 out of 1 instance completed (running for 20 seconds). None of the instances are sending data.". I made many tests and determined that every time I push my CodeCommit and then deploy it to EB it works (while http is set up or either Single Instance), but if I make a HTTPS it stops to work without any apparent reason.

My suspicion is that HTTPS listener or switch between instances somehow blocks change from CodeCommit to be send to Elastic Beanstalk. Also it is important to note that my custom domain has DNS record to rout all traffic to EB. "random" domain in order to retrieve information. Let me also know if you know better approaches for deploying a web application on AWS, this approach I used from documentation.

I appreciate your time.