Step 6.2.2
npm install error:
I had to reverse the changes in this pull-request (0b7717e) in order to get npm install to complete. Happened on both 32-bit bullseye and 64-bit Bookworm running on a Raspi 4 4gb.

Step 6.3.3
Not really an issue as it automatically fixes this for you, but "sudo a2enmod cgi" should be "sudo a2enmod cgid".

Thanks,
Noor

Hello. Thanks for providing the tutorial. I didn't see an obvious way to raise questions on AWS so thought I'd ask here. I can't seem to login (Step 7.2, PiBot Provisioning Login) and have worked backwards to try to solve the issue without success. It seems there are some instructions missing at step 6.3 (see image below and 2 arrows). I believe I was able to make the .py scripts executable (chmod +x), but can't confirm and I don't know how to adjust the green grass certificates. Any help would be appreciated.

Thanks,
Noor

Step 13.1
Site access error
When navigating to the cloudfront website, I kept getting access denied error. I double-checked the S3 bucket settings and troubleshooted here with no obvious reason as to why I was getting the error. Input would be appreciated.

Thanks,
Noor

Step 9.3.1
typo
In the tutorial, the "exec_path" line of start-webrtc.py reads: "/homels/pi....". Removed ls -> /home/pi...
This file is imported into Cloud9 in the beginning of the tutorial and does not contain the typo. Consider adjusting the tutorial to only change line 8 with CRED_EP variable instead.

Step 9.4
Component module import error
I was not able to deploy the move and proximity components. In the /greengrass/v2/logs, I keep getting ModuleNotFoundError: No module named 'awsiot' for move and 'boto3' for proximity on line "import awsiot.greengrasscoreipc". I've made sure they (as well as awsiotsdk) are installed as user and that /home/pi/.local/bin was in PATH. I then installed the modules globally and added /home/pi/.local/bin as well as other potentially pertinent paths to PATH for all users and still couldn't deploy successfully. I recreated the component and added a "RequiresPrivilege": true, lifecycle hook, but that didn't deploy either. Input would be appreciated.

The KVS component deployed successfully and I was able to view the stream on AWS Kinesis dashboard on 32-bit Bullseye. In case you run this on 64-bit Bookworm, I had issues with gstreamer and followed the instructions here to get streaming to show up.

Thanks,
Noor

Step 12.1
Typo
Remove ")" after ..role.json
ROLEARN=$(aws iam create-role --role-name "Cloud9-iot-republish-role" --assume-role-policy-document file://iam-assume-role.json) | jq -r '.Role | .Arn').

Step 12.2
: bad substitution
I kept getting : bad substitution error when trying to create the iot-rule.json. I had to manually create the rule via AWS IoT dashboard (message routing -> rules).

Thanks,
Noor

Step 8.7
running "make" fails on both 32-bit bullseye and 64-bit Bookworm:

I kept running into errors with openssl but was able to successfully build after modifying CMakelists.txt. See: https://github.com/dave-malone/aws-kvs-webrtc-demo-for-raspberry-pi/blob/main/build-kvs-webrtc.sh. I entered these lines in the terminal after running "cmake ..".

patch CMakeLists.txt; don't build openssl or mbedtls since those are installed via package manager

sed -i 's+build_dependency(openssl ${BUILD_ARGS})+#build_dependency(openssl ${BUILD_ARGS})+g' amazon-kinesis-video-streams-webrtc-sdk-c/CMakeLists.txt
sed -i 's+set(OPENSSL_ROOT_DIR ${OPEN_SRC_INSTALL_PREFIX})+#set(OPENSSL_ROOT_DIR ${OPEN_SRC_INSTALL_PREFIX})+g' amazon-kinesis-video-streams-webrtc-sdk-c/CMakeLists.txt
sed -i 's+build_dependency(mbedtls ${BUILD_ARGS})+#build_dependency(mbedtls ${BUILD_ARGS})+g' amazon-kinesis-video-streams-webrtc-sdk-c/CMakeLists.txt

Thanks,
Noor