Please add OM to AWS

Other
1

Hello
Currently, Amazon Web Services support this OS: Ubuntu, Amazon Linux, Red Hat Enterprise Linux, CentOS, Debian, SUSE, FreeBSD, Fedora, macOS, Mint, Gentoo, and OpenSolaris.

Can you please work with AWS and add OM to the list?
Thanks,
Dmitriy

2

Do you have any contact at AWS we could talk to? We don’t have one, and info@… addresses for big companies are typically very good at ignoring things.

3

An AMI is a template that contains the software configuration (operating system, application server, and applications) required to launch your instance. You can select an AMI provided by AWS, our user community, or the AWS Marketplace.

There are 6427 AWS Marketplace AMIs (AWS and trusted third-party AMIs) and 500 Community AMIs (Published by anyone).

Community AMIs contain all AMIs that are public, therefore anyone can publish an AMI and it will show in this catalog. This catalog can also contain paid products. When using community AMIs it is best practice to ensure you know and trust the publisher before launching an AMI.

I guess you should have an AWS account (AWS have a Free Tier account) and use EC2 Image Builder to create custom AMI

4

Will take a look. Assuming an AMI is essentially a qcow2 image or something, it shouldn’t be a big problem. But we like automating things, so ideally it should come right out of os-image-builder without having to use their tools to get it on.

5

Amazon’s cloud computing uses Xen and KVM hypervisors. You can probably create an image without AWS tools, but I am not sure about it.

6

I’ve tried, but the sad truth is their interface is so messy that I couldn’t figure it out if my life dependend on it.
After all the hoops it bombs out saying

  • Image recipe: InvalidParameter: The service role EC2InstanceProfileForImageBuilder provided does not exist or does not have sufficient permissions.
  • Import: InvalidParameter: The service role EC2InstanceProfileForImageBuilder provided does not exist or does not have sufficient permissions.

Even though the image is set up to be public.

7

Did you open a ticket with AWS support? You can escalate the issue to the engineering team, but you have to spend some boring time with the first support layer person first.
Sorry, I can’t open this ticket from my corporate account.

8

No tickets with the free plan

9

Maybe you should create those service roles first?

10

This is the answer from AI: It sounds like there’s an issue with the IAM role used by AWS Image Builder. Here are a few steps you can take to troubleshoot and resolve this error:

  1. Verify the Role Exists: Ensure that the EC2InstanceProfileForImageBuilder role exists in your AWS account.
  2. Check Role Permissions: Make sure the role has the necessary permissions. You can attach the EC2InstanceProfileForImageBuilder managed policy to the role.
  3. Trust Policy: Ensure that the role’s trust policy allows the vmie.amazonaws.com service to assume the role. Here’s an example trust policy:
    {
    “Version”: “2012-10-17”,
    “Statement”: [
    {
    “Effect”: “Allow”,
    “Principal”: {
    “Service”: “vmie.amazonaws.com”
    },
    “Action”: “sts:AssumeRole”,
    “Condition”: {
    “StringEquals”: {
    “sts:Externalid”: “vmimport”
    }
    }
    }
    ]
    }

Review Logs: Check the CloudWatch logs for more detailed error messages. The logs can provide more insight into what might be going wrong