It works, they used to have issues with DHCP services, but that would have been linux too. It seems to be resolved now.
Have to know where to find the AMIs though. [1] Amazon doesn't make this as easy as they might.
[0] https://www.patreon.com/cperciva
[1] https://lists.freebsd.org/pipermail/freebsd-cloud/2019-Febru...
What would you like to see changed?
While we're here: As I implied, I recently got FreeBSD up and running from one of your AMIs. (I was just playing around, not doing anything serious, and I don't know FreeBSD well at all, my experience is with Linux.) Thanks for your work here. I encountered two issues though:
1. It took a long time for the instance to boot up and for port 22 to open. Roughly 14 minutes. This is with a t3a.small instance.
2. I was unable to confirm the SSH public key of the instance. The EC2 custom is for it to be written to the system log, which is viewable from within the EC2 web dashboard, but FreeBSD didn't appear to do this. (This can take a few minutes on Ubuntu and Amazon Linux 2, for whatever reason, but it works eventually.)
Also, and perhaps it's just me that trips over this, but I'd find it helpful if it were made more explicit that the correct username is 'ec2-user'.
I haven't tried out the ARM64 AMIs but it's great you're providing AMIs for both architectures. Amazon seem pretty serious about their ARM instance-types.