# Rocky 9.4 AWS ami not booting after kernel update **URL:** \ **Category:** Rocky Linux Help & Support\ **Tags:** rocky-linux-9\ **Created:** [May 15, 2024, 4:32pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091 "2024-05-15T16:32:32Z")\ **Posts on this page:** 13\ **Page:** 2
**Author:** ![MikeDach](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@MikeDach](https://forums.rockylinux.org/u/MikeDach)\ **Post date:** [June 18, 2024, 4:55pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/21 "2024-06-18T16:55:47Z")
Hello, to bump the topic, I just checked and `792107900819` does not have new images listed for `Rocky-9-EC2-Base-9.4*` ---
**Author:** ![sanjanrahman](https://avatars.discourse-cdn.com/v4/letter/s/aeb1de/32.png) [@sanjanrahman](https://forums.rockylinux.org/u/sanjanrahman)\ **Post date:** [June 26, 2024, 8:11pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/22 "2024-06-26T20:11:31Z")
Note: I do see 792107900819/Rocky-9-EC2-Base-9.4-20240523.0.x86\_64 was created first on 2024/05/09 for AWS Public AMI then most probably have the fix on x86\_64 with new create date 2024/06/03, However arm64 Image is still having problems per this issue rocky-9-4-aws-ami-not-booting-after-kernel-update Any ETA on this fix and receive new public base image AMI in AWS 792107900819/Rocky-9-EC2-Base-9.4-20240509.0.aarch64 create date after 2024/05/09? ---
**Author:** ![sanjanrahman](https://avatars.discourse-cdn.com/v4/letter/s/aeb1de/32.png) [@sanjanrahman](https://forums.rockylinux.org/u/sanjanrahman)\ **Post date:** [July 3, 2024, 2:34pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/23 "2024-07-03T14:34:33Z")
Hi, Any update on this? Thanks ---
**Author:** ![sanjanrahman](https://avatars.discourse-cdn.com/v4/letter/s/aeb1de/32.png) [@sanjanrahman](https://forums.rockylinux.org/u/sanjanrahman)\ **Post date:** [July 10, 2024, 3:54pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/24 "2024-07-10T15:54:13Z")
Good Morning! is there any update on image AMI in AWS 792107900819/Rocky-9-EC2-Base-9.4-20240509.0.aarch64 create date after 2024/05/09? ---
**Author:** ![jaybrink4312](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@jaybrink4312](https://forums.rockylinux.org/u/jaybrink4312)\ **Post date:** [August 20, 2024, 4:06pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/25 "2024-08-20T16:06:03Z")
I’m using my own AMI Rocky 9.4 AMI and seeing same dnf update issues. This did not work for me… ```auto dnf -y update grub2-mkconfig -o /boot/grub2/grub.cfg shutdown --no-wall --reboot 1 ``` Rocky 9.4 dnf update results in non-functional EC2. This is the worst sort of bug and will likely result in return to using RHEL instance (which I am loath to do). Original “uname -a” 5.14.0-427.26.1.el9\_4.x86\_64 #1 SMP PREEMPT\_DYNAMIC Tue Jul 23 16:00:21 UTC 2024 x86\_64 x86\_64 x86\_64 GNU/Linux dnf update to kernel x86\_64 5.14.0-427.31.1.el9\_4 ---
**Author:** ![mbaker\_undo](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mbaker\_undo](https://forums.rockylinux.org/u/mbaker_undo)\ **Post date:** [October 4, 2024, 3:43pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/26 "2024-10-04T15:43:33Z")
Hello, adding to the list of people seeing this issue with AWS ARM image Rocky-9-EC2-Base-9.4-20240509.0.aarch64. Doesn’t appear to be a newer one. ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [October 4, 2024, 5:58pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/27 "2024-10-04T17:58:49Z")
> [@mbaker\_undo](#): > > Hello, adding to the list of people seeing this issue with AWS ARM image Rocky-9-EC2-Base-9.4-20240509.0.aarch64. > > Doesn’t appear to be a newer one. When trying to do a deploy of an EC2 instance, I see the latest version. ![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/e/e7f309e4874fe792af9e1b4bffd2cc19e639078a.png) What is the process you are using to deploy the instance? > [@jaybrink4312](#): > > Rocky 9.4 dnf update results in non-functional EC2. This is the worst sort of bug and will likely result in return to using RHEL instance (which I am loath to do). Can you please describe what the console shows after performing an update? We have not received any reports of aarch64 systems having kernel update issues at our bug tracker. ---
**Author:** ![mbaker\_undo](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mbaker\_undo](https://forums.rockylinux.org/u/mbaker_undo)\ **Post date:** [October 6, 2024, 11:08am UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/28 "2024-10-06T11:08:10Z")
I was matching on the name ```auto 12:02 $ aws ec2 describe-images --filter 'Name=name,Values=Rocky-9-EC2-Base-9.4-*.aarch64' --query 'Images[].Description' [ "Rocky-9-EC2-Base-9.4-20240509.0.aarch64" ] ``` but didn’t realise there can be a uuid on the end ```auto 12:04 $ aws ec2 describe-images --filter 'Name=description,Values=Rocky-9-EC2-Base-9.4-*.aarch64' --query 'Images[].Name' [ "Rocky-9-EC2-Base-9.4-20240509.0.aarch64", "Rocky-9-EC2-Base-9.4-20240523.0.aarch64-0d51926d-1cd1-4223-bda9-346993accc16" ] ``` I’ll update the pattern in the selection process. ---
**Author:** ![mbaker\_undo](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mbaker\_undo](https://forums.rockylinux.org/u/mbaker_undo)\ **Post date:** [October 6, 2024, 11:22am UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/29 "2024-10-06T11:22:28Z")
No that’s not why it didn’t get picked up. It’s because it’s on a different owner ID ```auto 12:15 $ aws ec2 describe-images --filter 'Name=name,Values=Rocky-9-EC2-Base-9.4-*.aarch64*' --query 'sort_by(Images, &CreationDate)[*].[ImageId,OwnerId,CreationDate,Name]' [ [ "ami-08dc5c2a8ee46cbcb", "792107900819", "2024-05-09T21:47:02.000Z", "Rocky-9-EC2-Base-9.4-20240509.0.aarch64" ], [ "ami-09e7c72f178c8efc1", "679593333241", "2024-06-03T21:35:14.000Z", "Rocky-9-EC2-Base-9.4-20240523.0.aarch64-0d51926d-1cd1-4223-bda9-346993accc16" ] ] ``` We search for the owner ID of 792107900819 ---
**Author:** ![michelmzs](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/michelmzs/32/4866_2.png) [@michelmzs](https://forums.rockylinux.org/u/michelmzs)\ **Post date:** [October 21, 2024, 5:11pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/30 "2024-10-21T17:11:29Z")
Hi team, I couldn’t find an AWS AMI with the fix under the owner ID 792107900819 (Rocky Linux Project). Is this expected? We tested the AMI from AWS Marketplace, and it works fine. However, to use it, we need an additional Marketplace subscription for each account, I’d like to confirm before changing our internal AMI usage process. ---
**Author:** ![jaredc](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@jaredc](https://forums.rockylinux.org/u/jaredc)\ **Post date:** [October 22, 2024, 9:36am UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/31 "2024-10-22T09:36:20Z")
For which architecture? I can see x86\_64 ami in eu-west-2 Rocky-9-EC2-Base-9.4-20240523.0.x86\_64 ami-0a7b5dd86d37ab5a4 aarch64 only seems to be available from the marketplace ---
**Author:** ![michelmzs](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/michelmzs/32/4866_2.png) [@michelmzs](https://forums.rockylinux.org/u/michelmzs)\ **Post date:** [October 22, 2024, 2:12pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/32 "2024-10-22T14:12:04Z")
@jaredc for aarch64, there is no build `20240523` available in any region. For now, we’ve decided to switch to AWS-owned AMIs and handle the subscription through the AWS License Manager service. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [December 21, 2024, 2:12pm UTC](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091/33 "2024-12-21T14:12:14Z")
Closed on December 21, 2024, 2:12pm UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed. [Previous page](https://forums.rockylinux.org/t/rocky-9-4-aws-ami-not-booting-after-kernel-update/14091.md?page=1)