I haven’t been able to find the Rocky 10 AMI. Does one exist? If not, is one planned?
Hiya 
The Rocky 10 AMIs are public under our publishing account the same as the rocky 8 and 9 ones.
Marketplace images have been delayed, but I’ve pushed up a couple of offers now to get the process started:
What is the account ID? I can’t find them when I search public AMIs.
I’m having the same issue, I cannot find a Rocky 10 AMI anywhere.
When I go to the Downloads page and under Cloud Providers I click “AWS AMI” the popup shows no version higher than 9.6.
If I look for AMIs shared by the Rocky AWS account ID (792107900819) I also get no images newer than 9.6:
Something doesn’t seem quite right
Just following up on this issue as I’m still not seeing Rocky Linux 10 AMIs available, either via the Download - Rocky Linux page or searching within the AWS console for the AMIs.
I can see all 8.x and 9.x versions but nothing related to 10.x.
Either I’m missing something obvious, or there is a problem. If it’s the latter, I’m surprised it’s only myself and @virginiap enquiring about it.
Any help or advice would be greatly appreciated!
Hello Daedalus,
I am also looking for the Rocky 10 AMI, but it appears that it is still not available. I attempted to search for it in the Community AMIs using Owner ID: 792107900819, but so far have been unable to locate it.
1 Like
If I am interpreting this correctly, I should be able to bypass the silly Marketplace nonsense and search for public AMIs owned by account ID 792107900819. When I do this in us-east-2, I see 8.9, 8.10, 9.3, 9.4, 9.5, and 9.6, but no 10.0. Am I missing something or are there really no AMI’s available yet?
Since AMIs aren’t published at the same time as other release artifacts, what is the best way to track progress toward publication and find out about circumstances such as third-party blockers?
1 Like
Thanks for the ping here. Let me track down why these versions didn’t get published.. I smell a quota issue lurking.
I’ve requested a quota increase. My nose was right (partially). It was also a partial failure of the script to run in the first place, but there was also a quota issue
3 Likes