Test Utility and ARM preferences for Kinesis sample - CloudFormation link & template: instance Create fails in region: ca-central-1

[tonepilot]

The CF template itself does include an ami for ca-central-1.

I should first ask if this Panorama product & repo is still active?

Running the template fails in the Create Instance ... so forget preferred env for the moment ... tried using simple JupyterLabs:

• I don't have time to become a CloudFormation expert

• Despite not being able to have the preferred Test Utility environment, I can run & deploy most of the samples in a CPU-only JupyterLab notebook instance. They have all been x86_64 instances, and they all are able to deploy the samples, and connect to my RTSP camera, as expected.

As far as I can tell, Sagemaker images in ca-central-1 do not support ARM in any case! Is this a Canada availability issue? Which should I select when I create my notebook, if ARM is to be preferred? Your github note strongly suggests: It is highly recommended to use ARM64 based EC2 instance for the Test Utility.

• I am now in need of getting the Kinesis multi camera sample to deploy. The notebook steps all succeed for build, package, etc. It fails to deploy, despite all cameras validated from other sample tests (connection strings & usernames/passwords):
  • samples/kinesis_video_streams:
  • I am building & packaging on x86_64:
    • Could this be the failure issue? There are no debug hints in the AWS console, such as "ARM machine cannot load binaries from x86_64 build" (... as sub-parts are gstreamer & KVS SDK libs).
    • Any suggestions for deploying this kinesis sample? What is simple way to set up a preferred ARM environment for JupyterLabs, if that is the likely cause?
    • Any suggestions for debugging the workflow?

Thanks for your time.