EZLive is a minimal self-hosted livestream solution built on top of S3-compatible object storage.
It runs a local RTMP server, receive live video, turns it into HLS segments (.m3u8 + .ts) and serves them as static files through any S3-compatible object storage. No dedicated streaming server is required — everything runs serverlessly. Then you can easily setup a HTML5 HLS player to watch the stream.
Install dependencies:
- FFMpeg (libavformat, libavutil, libavcodec)
- AWS C++ SDK (libaws-cpp-sdk-core, libaws-cpp-sdk-s3)
Build:
make
Setup a S3-compatible object storage bucket, for example, Cloudflare R2, AWS S3, Minio, DigitalOcean, etc.
Then create a config file config:
listening_addr=127.0.0.1
listening_port=1935
bucket=YOUR_BUCKET_NAME
endpoint=https://your-s3.com
s3_path=ezlive/
access_key=YOUR_S3_ACCESS_KEY
secret_key=YOUR_S3_SECRET_KEY
region=auto
key=your_live_key
In the dashboard of your object storage provider, enable public read, and add the domain name of your web HLS player to CORS setting. If you don't know how to setup a web HLS player, just add https://mistivia.github.io.
For AWS S3, Edit bucket setting, set "Permissions" -> "Bucket Policy" to:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicReadOnly",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::nebulive/*"
}
]
}
Then set "Permissions" -> "Cross-origin resource sharing (CORS)" to:
[
{
"AllowedHeaders": [
"*"
],
"AllowedMethods": [
"GET"
],
"AllowedOrigins": [
"https://your.hls.player.com"
],
"ExposeHeaders": []
}
]
Start EZLive:
./ezlive
Open OBS, streaming to rtmp://127.0.0.1/live, no streaming key needed. The streaming format must be H.264 + AAC.
Then use a HLS player to load https://YOUR_BUCKET_NAME.your-s3.com/ezlive/stream.m3u8 to watch the stream.
If you don't know how to setup a HLS player, then make sure you have added https://mistivia.github.io in your object storage's CORS setting, then open https://mistivia.github.io/ezlive#https://YOUR_BUCKET_NAME.your-s3.com/ezlive/stream.m3u8.
The Docker and Windows binary builds were done on my laptop. While I promise I have no malicious intent, this does not guarantee that my build environment is secure, so is the build target. If you truly care about your privacy and security, please make sure to build from source yourself.
Download the docker image tarball in release.
Load the docker image:
cat ezlive-docker-image.tar.gz | gzip -d | sudo docker load
Create a directory conf:
mkdir conf
Create a config file conf/config, the config file is nearly the same as the config above. But for docker, the listening_addr should be 0.0.0.0:
listening_addr=0.0.0.0
listening_port=1935
bucket=YOUR_BUCKET_NAME
endpoint=https://your-s3.com
s3_path=ezlive/
access_key=YOUR_S3_ACCESS_KEY
secret_key=YOUR_S3_SECRET_KEY
region=auto
key=your_live_key
Start docker container:
sudo docker run -it --rm \
-v ./conf:/etc/ezlive/ \
-p 127.0.0.1:1935:1935 \
localhost/ezlive
For windows users, there is a windows build using MSYS2. See release.
To start using, unzip the windows tarball, create a config file in the same directory as ezlive.exe, and run ezlive.exe.
The built-in RTMP server is modified from pine.
Thank @uonr for making nix flake.