Questions[internet-of-things](server)

I'm wondering if I can use an EKS managed node to be the control plane for a K3s cluster deployed on an edge/IoT device, such as the Intel NUC. My goal is to have a lightweight kubernetes distro to manage containerized applications running on the NUC or theoretically any edge/IoT device, but be able to manage it from the cloud whenever there is internet connectivity.

Could I set up a k3s cluster on the NUC (or an edge/IoT device) and then have that communicate with an AWS EKS control plane via the Kubernetes API server?

I have a simple IoT temp sensor (from China) and I can change the destination it routes traffic to. I want it to continue sending to their system AND to mine (redundancy, resilience etc). The sensor does not support sending to 2 destinations.

I use cloudflare for my webserver - so I have an A rule that routes traffic for a subdomain on to my IoT server. Can I use this to duplicate the traffic so it goes to BOTH the Chinese server AND my own server?

Or would I have to try setting up something that will receive data on my server and then re-send it to China (less preferable as clearly less resilient).

So I have this GCP setup with IoT devices, but I want to SSH into devices that are geographically very far. Of course they are not on the same local network. My current idea is that I host a VPN and connect them through it while I am myself a client of this VPN. It works when I use a single device, however the autologin file (openvn.conf, user-locked) seems to only allow one connection and disconnect any other devices. Maybe I am misunderstanding how a VPN works, but how would one go about creating a new user automatically ? Is there anyway to have an autologin file that handles multiple devices ?

I am using OpenVPN Access Server v2.7.5 with a Debian Linux distribution on the devices.

Thanks in advance.

I am working on an embedded device that runs FreeBSD and SSH.

As you know, sshd likes to randomly generate a set of server keys when it first boots up. The problem is that we will be shipping the product with a read-only sd-card filesystem (non-negotiable).

My two options as I see them are:

• Ship the same sshd server keys on all devices
• Mount a memory file system and generate the server keys on each boot (slow...)

Is it a major security problem to ship the same server keys on all devices? These items will not be directly on the internet. There will occasionally be multiple devices owned by the same person and on the same network.

Most of the time the device will not be connected to the internet.

Logging in with SSH is not part of normal operation. It is mostly for the convenience of the programmers and technicians. Customers will not be logging in to the device with SSH.

What are the ramifications of using the same server keys on multiple hardware devices?

PS could someone please create an internet-of-things tag?

EDIT: I am talking about installing the same host private keys on all servers (devices). As far as user public/private keys, there are currently no plans to use key based login - it would be password login. Again, same password on all servers (devices).

I know that this is probably a bad idea. I'd like to know why precisely it is a bad idea though so I can understand the tradeoffs.