Let's Encrypt certificate with AWS deploy: What do I need to do with the ElasticIP, my DNS, and my domain?

OpenVidu v2 Issues with deployment
1

Hi there, I’m trying to get up and running with OpenVidu. So far, I deployed a test OpenVidu server to Amazon following the instructions located here: https://openvidu.io/docs/deployment/deploying-aws/

My first test server used the self-signed SSL certificate setting. For testing this works but for a production app clearly this won’t work. So I setup a new test server and this time I selected the Let’s Encrypt option for the SSL certificate setting.

However, here’s where I am running into issues. I see this message on the tutorial page:

If you are using LET’S ENCRYPT CERTIFICATE , of course you will need to register your ElasticIP in your DNS hosting service and associate it with the fully qualified domain name. Until your domain name is not accessible through the public IP you chose, this deployment won’t work

Can someone elaborate on what exactly this means? I’ve created the Elastic IP in AWS and added that IP address to the OpenVidu configuration when I setup the server.

But what exactly am I supposed to do with this Elastic IP address now? Am I understanding this correctly that I should be able to use the Elastic IP address to reach my site?

Thanks in advance for any help!

2

Managed to figure it out myself finally. I’m not a server/networking/AWS expert by any means so it took awhile.

I’ll post what I did in case anyone else runs into this question in the future. Essentially in my DNS settings for my domain, I setup a new DNS A record. I made a subdomain which pointed to the Elastic IP I setup on AWS.

That allowed me to successfully deploy the OpenVidu server on AWS. Once the AWS server was deployed, I could then use that subdomain to access my OpenVidu server. The SSL certificates appear to be working correctly, I’m not getting any warning messages about certificates anymore.

Hopefully someone else will find this helpful.

3

Yes, you did it perfectly right :wink: Users must setup a new DNS A record for their domain, pairing their (sub)domain with the IP of the cloud provider server where OpenVidu is gonna be deployed (an ElasticIP of AWS in this specific case).

Regards.

1 Like