Arch Linux AMIs for Amazon Web Services - ArchWiki

Jump to content

# Arch Linux AMIs for Amazon Web Services

4 languages

- Español
- 日本語
- Português
- 中文（简体）

From ArchWiki

## Public community Arch AMIs

Note: Arch Linux currently does not offer official Amazon Machine Images. The ones listed here are created by the community.

### AMIs

Arch Linux AMIs are listed here: http://arch-ami-list.drzee.net/

AMIs are build twice a month (the 1st and the 15th - 2:00am UTC) and are available for all regions that to do not explicitly require 'Opt-in' - see Region List. If an AMI is needed in a region where its currently not available, an AMI can be copied to that region.

The AMIs are EBS HVM AMIs and are available with two different kernels:

- std - using the Standard Arch Linux Kernel from the default Arch repositories configured with the necessary modules for EC2 usage. The scheduler and I/O is not optimized for Cloud. A complete list of packages in the AMI: [1].
- ec2 - using an EC2 optimized kernel of the Standard Arch Linux Kernel created by UplinkLabs and hosted in a dedicated repository - click here for more details. List of packages in the AMI: [2].

Both kernels have been tested on many different EC2 instance types (t2, t3, t3a, m/r/c5, m/r/c6 and advanced hardware with GPUs) and are booting fine.

Note: As of 2023-06-12, there is confirmation that EC2 optimized kernel from UplinkLabs hangs upon boot when running on an instance family using the XEN hypervisor (e.g. `t2-micro`). The XEN kernel modules are not included in the latest kernel which is why the boot fails. Please use only instance families using the new Nitro Hypervisor - see: Instances build on Nitro. These will still work with the EC2 optimized kernel.
Note: ec2 repository ships other packages alongside linux-ec2 kernel. By default, ec2 is set as the top most repository in `pacman.conf`. As a result, packages from ec2 may have a higher priority than those from the Official repositories. This can lead to some inconsistent behaviors depending on actual versions of packages.

AMIs with LTS kernels are not built.

### REST API to List AMIs

An REST API is available to get a JSON of available AMIs:

Note: The API endpoint now uses a custom domain name which should remain static.

- Get all AMIs: `https://arch-ami-api.drzee.net/`
- Get list of latest AMI in each region: `https://arch-ami-api.drzee.net/latest` (this produces the same list as http://arch-ami-list.drzee.net/ but in JSON)
- Get all AMIs in region: `https://arch-ami-api.drzee.net/region` - replace `region` with the desired region: `eu-north-1`, `eu-west-1`, `us-east-1` etc.
- Get all AMIs in region for CPU architecture: `https://arch-ami-api.drzee.net/region/arch` - replace `arch` with `x86_64`
- Get all AMIs in region for CPU architecture and kernel-type: `https://arch-ami-api.drzee.net/region/arch/type` - replace `type` with `std` or `ec2`
- Get Latest AMI in region for in region for CPU architecture and kernel-type: `https://arch-ami-api.drzee.net/region/arch/type/latest` - replace `region`, `arch` and `type`

### First Run

Note: The mirror list baked into the AMI was generated at time of image build and is using servers in Germany.

After booting the AMI it is recommended/required to execute the following steps to initialize pacman and select fast local repositories:

    # pacman-key --init
    # pacman-key --populate
    # reflector --country "ISO 3166-1 Alpha-2 Country Code" --protocol https,http --score 20 --sort rate --save /etc/pacman.d/mirrorlist
    # pacman -Syu

The Reflector package is preinstalled in the AMIs.

It is recommended to set a proper configuration for reflector in `/etc/xdg/reflector/reflector.conf` and enable the timer services to regularly refresh the mirror list. For details see the Reflector package documentation.

For convenience, a script is included: `/etc/pacman.d/pacman_init.sh`.

Executing the script with `sudo` will automatically run the above `pacman-key` commands and setup Reflector by writing `/etc/xdg/reflector/reflector.conf`. Finally it will run Reflector to generate a mirrorlist.

Country selection for Reflector is done based on the AWS region where the instance is running. The following shows mapping between region and country codes (only regions where the AMIs are distributed to are supported):

    # region_to_country['eu-west-1']='IE,UK,DE'
    # region_to_country['eu-west-2']='UK,IE,DE'
    # region_to_country['eu-west-3']='FR,DE,UK'
    # region_to_country['eu-central-1']='DE,FR,UK'
    # region_to_country['eu-north-1']='SE,FI,NO,DE'
    # region_to_country['us-east-1']='US,CA'
    # region_to_country['us-east-2']='US,CA'
    # region_to_country['us-west-1']='US,CA'
    # region_to_country['us-west-2']='US,CA'
    # region_to_country['ap-south-1']='IN,SG,US'
    # region_to_country['ap-northeast-1']='JP,KR,TW,US'
    # region_to_country['ap-northeast-2']='KR,JP,TW,US'
    # region_to_country['ap-northeast-3']='JP,KR,TW,US'
    # region_to_country['ap-southeast-1']='SG,ID,TH,US'
    # region_to_country['ap-southeast-2']='AU,NZ,US'
    # region_to_country['ca-central-1']='CA,US'
    # region_to_country['sa-east-1']='BR,CL,US'

For EMEA Regions, "DE" (Germany), and for US/APAC/South America Regions, "US" (United States), is always included as a last resort should in country or "neighbor" country repositories be unavailable.

Alternative provide your own mirrorlist and do not use the Reflector package.

### Build process

Note: This section provides a short description on how the AMIs are build.

The entire build process runs on AWS and is fully automated.

Overall the automated build procedure is managed by a AWS Step Function that is executed at regular intervals using a Amazon EventBridge timed event.

The step function will initiate the build process and uses a combination of native calls and AWS Lambda functions for more complex elements.

A new set of AMIs is build, by booting an EC2 instance with the previous AMI and using it as the work or build machine. The build machine is bootstrapped with a special build script that essentially uses pacstrap and some additional steps to build the image, the basics are outlined in section (2) below.

Following the build of the AMI the new AMI is test booted on an EC2 instance to verify that it starts up correctly. If successful the AMI is distributed to the regions and registered in a DynamoDB database. The database can be queried using the API REST endpoint. Old AMIs are deleted from the regions and the DynamoDB database.

### Credits

Thanks to Steven from UplinkLabs for helping to understand the build process and test the initial quality of the images. Also thanks to Mathcom for an excellent shells script to help me get started (unfortunately the link to that has been removed), which accelerate putting the basic build process together.

You may send comments and suggestions (without any promise that they will be looked at) to: arch-ami 'at' drzee.net

### Wishlist

- Create official EC2/Cloud optimized kernels in the Standard Arch Linux repositories.
- Add the AWS CLI v2 to the Standard Arch Linux repositories (v1 is available, but may be discontinued in the future)
  - Unfortunately AWS CLI v2 was removed from the Extra Repo due to issues with Python 3.12 - images are again build with aws-cli v1

## Building Arch AMIs

You can also build your own Arch Linux AMI. See [3] for details.

Category:

- Installation process