You are totally right, and sorry, because I misread the previous post.
Could you check the following?
- Go to the Target Groups in your aws console.
- Check the Port and Protocol you are using in your target group.
If it is port
HTTP (if you followed our guide it should be), you don't need to download the certificates because the connection between the Load Balancer and the instance is not using HTTPS.
To avoid the warning message that you are having, you can either disable HTTPS in Apache or create a new auto-signed certificate for the instance only. We would recommend the second option. Note that you will continue having the AWS certificate in the Load Balancer and your web application will continue working with the AWS certificate.
To do so, please execute the following commands. The first command will prompt for some information. When asked for
Common Name FQDN, specify
sudo openssl req -new -key /opt/bitnami/apache2/conf/server.key -out /opt/bitnami/apache2/conf/cert.csr
sudo openssl x509 -in /opt/bitnami/apache2/conf/cert.csr -out /opt/bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apache2/conf/server.key -days 365
sudo /opt/bitnami/ctlscript.sh restart apache
After restarting apache, you can check again the Apache logs and the warning messages should not appear. Your web site will continue working with the certificate issued by AWS.
Let us know if it works.