-
-
Notifications
You must be signed in to change notification settings - Fork 12
Installing LiveKit on an Amazon Web Services Server for the Foundry LiveKit Module
What you need:
- Amazon Web Services Account
- Domain name you control and can add sub-domains to. Create an Amazon Web Services account (free tier is free for 1 year) and then an instance of an Amazon Linux server (EC2) in your geographic region: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/get-set-up-for-amazon-ec2.html
Use SSH to log into your newly created virtual server (instance): https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html and then install Docker following instructions here: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/docker-basics.html (steps 1-8).
Set-up two sub-domains using your service-provider’s management console, e.g.: livekit.mydomain.org and livekit-turn.mydomain.org, both of these pointing to the IP address of your EC2 instance.
Back in your SSH terminal, log into your EC2 instance. Follow the instructions here to install a LiveKit server in a Docker container: https://docs.livekit.io/deploy/vm/ Use the Startup Script method rather than Cloud Init method, making sure to change the permission of the startup script: sudo chmod 755 init_script.sh to be able to run it. Running the script will output a URL for your Livekit server (e.g. wss://livekit.mydomain.org) API Key and Secret, which you will need for the Foundry LiveKit module.
Instructions on opening the ports on the AWS firewall for LiveKit are here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html
Note: If you stop and start your AWS instance your public IP address will change, and you will need to redirect your domains to the new address. The IP does not change if you restart the instance.
Having installed and enabled the Foundry LiveKit module, use the configuration option to enter your domain name, API key and API secret.