3 ms·

I'm missing something here. We have lists of AMIs in every release announcement, and FreeBSD is also in the AWS Marketplace. (Also, for the automation nerds,

I'm missing something here. We have lists of AMIs in every release announcement, and FreeBSD is also in the AWS Marketplace. (Also, for the automation nerds, there's an SNS notification which goes out every time we publish new AMIs.) What would you like to see changed?

MaxBarraclough 6y ago
I wasn't very clear: the way the AWS Marketplace wants me to 'buy' the AMI for $0 is an annoying extra step. You're doing the right thing on your side, publishing the AMI IDs plainly, the way Ubuntu do. [0] The AMI IDs work fine in EC2 even without 'buying', if you already know them, so it makes little sense for Amazon to artificially introduce this $0 payment step, in the name of it being a 'marketplace'. 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. [0] https://cloud-images.ubuntu.com/locator/ec2/ https://cloud-images.ubuntu.com/locator/ec2/

MaxBarraclough 6y ago

I wasn't very clear: the way the AWS Marketplace wants me to 'buy' the AMI for $0 is an annoying extra step. You're doing the right thing on your side, publishing the AMI IDs plainly, the way Ubuntu do. [0] The AMI IDs work fine in EC2 even without 'buying', if you already know them, so it makes little sense for Amazon to artificially introduce this $0 payment step, in the name of it being a 'marketplace'. 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. [0] https://cloud-images.ubuntu.com/locator/ec2/ https://cloud-images.ubuntu.com/locator/ec2/