My application has static front-end content as well as a backend server. I already have an existing mechanism to serve the front-end; I'm running the backend in an AWS EC2 (with Elastic IP). Throughout the course of its operation, my front-end initiates
https requests to my backend (currently to its bare IP). I need a proper CA certificate (not self-signed), or else chrome will block these requests.
what is the standard practice here? it looks like standard certificate providers (e.g., Let's Encrypt) refuse to issue certificates to bare IPs. On the other hand, it seems like overkill to get a custom domain name just for this backend, seeing as users never access it directly (rather, the front-end pings it for them), and they already have a way to get the front-end. in particular, it would be fine if my "domain name" were just a random string of letters.
finally, I need a fully running server in the backend, not just static "hosting".
how should I proceed? many thanks in advance; apologies if this is basic.