I have an elastic public IP for my EC2 instance. I have an Nginx server running on it (and nodejs as a backend server). I'd like to enable HTTPS access to my server.
My questions:
Can I create an SSL certificate (not self-signed) using just my elastic public IP?
If not, my department has a domain. let's say, https://www.example.com. How can I enter the record (and where?) so that https://www.example.com/base-route points to my elastic public IP without affecting any existing routes? If this is possible, do I create ssl certificate for https://www.example.com or https://www.example.com/base-route
If I create a new SSL certificate for https://www.example.com/base-route, will it have any impact on the existing certificate for https://www.example.com/?
Will new routes, say /route-2 on linked domain name point to correct route. For example, https://www.example.com/base-route/route-2 point to http://ip-address/route-2