Set up picam

[sgbaird]

Mostly set up, except we need to get the new lambda URL set up for VCL. Currently in my office in the corner. We also have parts for an additional one.

https://ac-training-lab.readthedocs.io/en/latest/devices/picam.html

[sgbaird]

https://github.com/vertical-cloud-lab/MonArk/issues/9

https://github.com/vertical-cloud-lab/MonArk/issues/6

https://github.com/vertical-cloud-lab/MonArk/issues/2

https://github.com/vertical-cloud-lab/MonArk/issues/7

[sgbaird]

We have BYU AWS accounts now.

From Ian Hagen:

Your accounts are now created. To access them you can go to aws.byu.edu. Access is controlled through some gro groups. The groups are aws-byu-dept-vcl-prd and aws-byu-dept-vcl-dev. You can add other users to the accounts by adding them as a member in those groups. If you have any questions let me know.

[seth-leavitt]

Update/Status:

PiCam is all imaged and ready to go as soon as the secret file is updated with the AWS url.

What left is needed:

• AWS URL for Lambda Script

[seth-leavitt]

I've been looking at rpi-Imager Which should in theory allow us to deploy the pi cam with a copy of Raspbian on it with all of the files and also customized secrets. Which in theory should make it so that the problem is just as simple as 1) Changing the config file 2) Imaging it.

I'm not completely sure how to use the RPI-imager yet, but given that pretty much all of the picam setup has just been git cloning and text file changing, it seems like it would be pretty simple. Especially since with Raspberry Pi Connect, we can have remote shell and screen sharing built into the image as well.

[seth-leavitt]

While trying to put together the Amazon AWS Lambda Function, I get blocked by a permission error:

User: arn:aws:iam::526563839438:user/seth-leavitt is not authorized to perform: iam:CreateRole on resource: arn:aws:iam::526563839438:role/service-role/LambdaCameraVCL-role-0vl3unlt because no identity-based policy allows the iam:CreateRole action

[sgbaird]

Turns out I get the same error.

My own troubleshooting: https://chatgpt.com/share/e/698cc15e-13d4-8001-b228-a3e8d3c69de4 (private), which wasn't too fruitful.

I did some of my own trial-and-error, and figured out that using one of the following existing roles works ok (ones with check marks, didn't bother trying the top 3). I was able to invoke a test using the ReadOnly role, so I'm not really sure what the implications of choosing one of these roles is in this specific case. I'll defer to BYU AWS on what to use.

@seth-leavitt could you try again, but using one of the existing roles above?

[seth-leavitt]

I don't have any existing roles populating, so I tried using our account ID: byu-dept-vcl-prd, along with manually typing each of PowerBuilder, lambda_role_multipart_upload, and ReadOnly as the role name. It seems like I don't have access to any of the ones in your screen shot.

It looks like I'm either being blocked by Azure because I don't yet have permissions to access the BYU AWS portal through Azure, OR I don't have access to any other roles besides the seth-leavitt role. Is there someone that I should just reach out to get this sorted out so that I don't keep bothering you?

Sorry for the late reply on this one.

[sgbaird]

It's a role you select when creating the lambda function itself, not switching your account login

[sgbaird]

All good, it's a steep learning curve

[seth-leavitt]

Okay,

So I've been going back and forth with Copilot for a while on this one.

It seems like I'm not trusted by any other AWS roles and so I'm unable to access or assume any of them. Is there something else that I'm missing?