I have recently used AWS elastic beanstalk to migrate my parse application server. Everything is working well with just plain HTTP, but I need more security so I've tried diving into the AWS documentation for setting up HTTPS with my server.
My goal is to have a scaleable server using a load balancer which protects all parameters in my API calls.
What I've done:
Purchased a domain name from Namecheap.
Created a certificate using AWS Certificate manager for this purchased domain name
Now I'm not sure how to use or test this. Before I had a load balancer I would just input the DNS name of my beanstalk instance when calling the Parse Server with
curl -X GET -H "X-Parse-Application-Id: XXX-XXX-XXX-XXX" -H "Content-Type: application/json" https://my-name.us-east-1.elasticbeanstalk.com/parse/classes/GameScore
But anytime I run this I get a: curl: (51) SSL: no alternative certificate subject name matches target host name error.
So I figured I might now need to start point my requests at the domain name I purchased? Or possibly the load balancer?
Do you see anything wrong with this setup?
I saw a very similar question here Setting up Elastic Beanstalk application with HTTPS
and like this person, my domain is just timing out right now. The given answer didn't make much sense to me.