Hi Steve,

About your first question, if my memory serves well, I did it exactly that way a few months back. 

I ended up automating probes registration with curl and a trivial shell script. Let me know if you need assistance.

Happy new year,
Pierre.

On Sat 2 Jan 2021 at 08:26 Steve Gibbard <scg@gibbard.org> wrote:
I’m working on creating some Raspberry Pi-based software probes, to put in some networks that currently lack Atlas probes.

I’d like to have a standard image that can come up and work wherever an individual probe lands, instead of needing to configure each one separately.

As far as I can tell from the documentation, it looks like the probes are identified by the encryption keys in /var/atlas-probe/etc/probe-key* .  If creating new probes from an image, is it sufficient to make each probe generate its own encryption keys, or are there other files that need to change?

For registering the probes, I see a web form that requires being logged into a RIPE account, and don’t see any equivalent in the API documentation.  Is there a way to register new software probes via the API?

Thanks,
Steve