This project demonstrates how to port Amazon Kinesis Video Streams Producer to Embedded devices(FreeRTOS/Embedded Linux). In case of using the following platforms the reference examples can securely stream video to Kinesis Video Streams.
- KVS producer on Linux - To evaluate KVS Producer without using MCU-based hardware, you can use the Linux machine. Please refer to the following section to setup the example.
- KVS producer with WebRTC on Linux
- Ingenic T31
- Espressif ESP-WROVER-KIT
- Realtek AmebaPro
- Raspberry Pi/V4L2
To download, run the following command:
git clone --recursive https://github.com/aws-samples/amazon-kinesis-video-streams-producer-embedded-c.git
If you miss running git clone command with --recursive , run git submodule update --init --recursive within the repository.
Camera devices can use X.509 certificates to connect to AWS IoT and retrieve credentials from the AWS IoT credentials provider to authenticate with the Kinesis Video Streams service. Follow the instructions in this document "how-iot" to setup the X.509 certificate.
In the examples, we upload video from H264 frames which are stored as files. These files are put under "samples/h264SampleFrames/" with filename "frame-[index].h264". For example, "frame-001.h264", "frame-002.h264", etc.
You can also use sample frames of amazon-kinesis-video-streams-producer-c.
This section describes how to run the example on Linux. The reference OS is Ubuntu 18.04LTS.
Before running the example, you need to edit the file "samples/kvsapp/sample_config.h" and replace these settings:
#define KVS_STREAM_NAME "kvs_example_camera_stream"
#define AWS_KVS_REGION "us-east-1"
#define AWS_KVS_SERVICE "kinesisvideo"
#define AWS_KVS_HOST AWS_KVS_SERVICE "." AWS_KVS_REGION ".amazonaws.com"
#define H264_FILE_FORMAT "/path/to/samples/h264SampleFrames/frame-%03d.h264"
#define CREDENTIALS_HOST "xxxxxxxxxxxxxx.credentials.iot.us-east-1.amazonaws.com"
#define ROLE_ALIAS "KvsCameraIoTRoleAlias"
#define THING_NAME KVS_STREAM_NAME
#define ROOT_CA \
"-----BEGIN CERTIFICATE-----\n" \
"......" \
"-----END CERTIFICATE-----\n"
#define CERTIFICATE \
"-----BEGIN CERTIFICATE-----\n" \
"......" \
"-----END CERTIFICATE-----\n"
#define PRIVATE_KEY \
"-----BEGIN RSA PRIVATE KEY-----\n" \
"......" \
"-----END RSA PRIVATE KEY-----\n"
#endif
The values of these settings come from the procedure of setting up the credentials provider by following instructions in this document "how-iot".
- KVS_STREAM_NAME: It's the stream name.
- CREDENTIALS_HOST: It's the IoT credentials host we setup earier.
- ROLE_ALIAS: It's the role alias we setup earier.
- ROOT_CA, CERTIFICATE, PRIVATE_KEY: These are X509 certificates. Please filled in your X509 certificates.
- H264_FILE_FORMAT: It's H264 file location.
Run the following command to configure the CMake project:
mkdir build
cd build
cmake ..
Run the following command to build the project.
cmake --build .
To run the example, run the following command.
./bin/kvsappcli
If everything works fine, you should see the following logs.
PUT MEDIA endpoint: s-xxxxxxxx.kinesisvideo.us-east-1.amazonaws.com
Try to put media
Info: 100-continue
Info: Fragment buffering, timecode:1620367399995
Info: Fragment received, timecode:1620367399995
Info: Fragment buffering, timecode:1620367401795
Info: Fragment persisted, timecode:1620367399995
Info: Fragment received, timecode:1620367401795
Info: Fragment buffering, timecode:1620367403595
.....
You can also check the streaming video in the console of Kinesis Video.
Please refer to port for how to port solution to your destination platform. There are already platform Linux and ESP32 for reference.
In the KVS application, we use these platform-dependent components:
- time: We need to get the current time for RESTful API and add timestamps to data frames.
- random number: It's used to generate the UUID of the MKV segment header. You could ignore it if you didn't use the MKV part of this library.
- sleep: It's for avoiding race conditions when making RESTful requests.