# Build AWS BalenaOS Image for ARM

**URL:** <https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746>\
**Category:** Product support\
**Created:** [April 2, 2026, 2:53pm UTC](https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746 "2026-04-02T14:53:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobertBakker](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@RobertBakker](https://forums.balena.io/u/RobertBakker)\
**Post date:** [April 2, 2026, 2:54pm UTC](https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746/1 "2026-04-02T14:54:00Z")

</div>

Hi,

In the past I’ve used the pre-published balena images to launch devices on AWS. Since these are not available anymore I followed this post to create an Generic x86\_64 image

Some of our devices run aarch64 - how can I build an arm image? I guess a need a specific link for bh.cr/balena\_os/…. to do that?

thx,

Robert

> **[BalenaOS AWS Amazon Machine Images Now Available](https://blog.balena.io/balenaos-aws-ami-available/)**
>
> This guide will show you how to create and provision a balenaOS Generic x86\_64 (GPT) Amazon Machine Image (AMI).

---

<div class="post-metadata">

**Author:** ![ycardaillac](https://avatars.discourse-cdn.com/v4/letter/y/a698b9/32.png) [@ycardaillac](https://forums.balena.io/u/ycardaillac)\
**Post date:** [April 2, 2026, 3:07pm UTC](https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746/2 "2026-04-02T15:07:00Z")

</div>

Hi @RobertBakker ,

You can build a generic aarch64 image with yocto using this [repo](https://github.com/balena-os/balena-generic) and specifically [machine](https://github.com/balena-os/balena-generic/blob/master/layers/meta-balena-generic/conf/machine/generic-aarch64.conf).

However I suppose you want to download a pre-built image.

You can do so in the way explained in the article you mentioned:

`balena os download generic-aarch64 -o balena.img --version v6.12.3+rev2`

Please keep us posted on how that goes for you.

Regards,

Yann

---

<div class="post-metadata">

**Author:** ![RobertBakker](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@RobertBakker](https://forums.balena.io/u/RobertBakker)\
**Post date:** [April 2, 2026, 4:53pm UTC](https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746/3 "2026-04-02T16:53:25Z")

</div>

Hi @ycardaillac ,

Thanks for th quick response,. The page refers to

`docker pull bh.cr/balena_os/cloud-config-amd64/461031537d2655560b9bc29ea2e1405c`

I guess that should be something else for an arm build?

regards,

Robert

---

<div class="post-metadata">

**Author:** ![RobertBakker](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@RobertBakker](https://forums.balena.io/u/RobertBakker)\
**Post date:** [April 2, 2026, 6:25pm UTC](https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746/4 "2026-04-02T18:25:07Z")

</div>

hm… I did create the amd image, but I just found out that it just doesn’t boot…. there’s nothing to see on of the ways AWS exposed information (systemlogs/screenshot/serial console..)

Since I spend enough time on this for now I’ll use the workaround to boot the old images I still had and upgrade the balenaOS via de belana web interface …

let’s hope that will keep working in the future…

---

<div class="post-metadata">

**Author:** ![ycardaillac](https://avatars.discourse-cdn.com/v4/letter/y/a698b9/32.png) [@ycardaillac](https://forums.balena.io/u/ycardaillac)\
**Post date:** [April 3, 2026, 7:13am UTC](https://forums.balena.io/t/build-aws-balenaos-image-for-arm/375746/5 "2026-04-03T07:13:19Z")

</div>

Hi @RobertBakker,

Oh yes sorry, I thought you referred to the OS image, well I think this container image:

`docker pull bh.cr/balena_os/cloud-config-amd64/461031537d2655560b9bc29ea2e1405c`

is only a pre-built version of [GitHub - balena-os/cloud-config: balenaCloud application used to configure balenaOS from supported metadata services · GitHub](https://github.com/balena-os/cloud-config) so you can clone the repo and `balena push` it to your fleet. Instead of using the pre-built image with `FROM` in a Dockerfile.

Your workaround should keep working as well, but it would be better if you’d be able to provision directly with a up to date OS image.

Regards,

Yann
