Help me to solve the SSL certificate and DNS record issue for wordpress bitnami multisite instance on AWS Cloudfront

I have configuration issues with the new website I deployed, which uses cloudfront, EC2 load balancer and bitnami wordpress multisite. Right now I can access to website since I added the ec2 instace's IP record to /etc/hosts file but obvilusly that's a temporary solution, plus, it doesn't help for HTTPS at all. What I want from you: 1-) Help me to find the configuration issue(s) both for accessing to my domain with SSL (with or without www CNAME), obviously through Cloudfront, without /etc/host records 2-) Move all the records back to Godaddy (While trying to fix the problem I moved everything to Route53 but I would like to remove that) 3-) Show me a provable guidance so that in the short future whenever I will add another SSL website (another domain) to the same wordpress multsite instance it will also work as expected with Cloudfront Please note that I am NOT asking you to fix it, I will fix it, I am asking you to GUIDE ME. I will do the work. ALSO IMPORTANT: This a BITNAMI MULTISITE wordpress instance, NOT a regular Wordpress instance, therefore you must have experience for this specific one, please mention in your first bid if you have such an experience! Please also state your level of experience with Cloudfront! If you will need any server logs, you will tell me and I will provide you, If you will need any info from Godaddy account i will provide you (screenshot etc.) for acces to AWS console, I will give you the credentials for user with the following rights, if you will need more visibility, I can provide it from my account: AWSCertificateManagerReadOnly AmazonEC2ReadOnlyAccess AmazonRoute53AutoNamingReadOnlyAccess CloudFrontReadOnlyAccess Domain [login to view URL] Cloudfront Distribution domain name: [login to view URL] Here are more technical details for the setup: here are the details of the set up: On the bitnami instance, I have set up the main domain with: sudo ./bnconfig --machine_hostname [login to view URL] sudo mv bnconfig [login to view URL] target group's listener listen's to port 80 and the instance is added as the target (it seemed like unhealthy, stating that "health check failed with this code [302]", that's why modified it added the code 302 as healthy but didn't help) Load balancer, which directs to that target group, has 2 listeners, for port 80 and port 443. the action for the port 443 is "forward to". For 443, I am using the certificate I issued via the certificate manager on AWS, it includes 2 domains with its sub domains (i.e. [login to view URL], *.[login to view URL], [login to view URL], *.[login to view URL]), later on, I am planning to add this another domain to this wordpress multisite, that's why added in the same certificate. I can also see the request counts under the "monitor" tab. Cloudfront distribution has the loadbalancer added, it has "HTTPS only" and "Redirect HTTP to HTTPS" set, "Forwarded query strings" on and already added all the domains I mentioned before as CNAMEs.