2017-12-25 02:06:54 +00:00
|
|
|
# Alpine Linux EC2 AMI Build
|
|
|
|
|
|
|
|
|
|
**NOTE: This is not an official Amazon or AWS provided image. This is community
|
|
|
|
|
built and supported.**
|
|
|
|
|
|
|
|
|
|
This repository contains a packer file and a script to create an EC2 AMI
|
|
|
|
|
containing Alpine Linux. The AMI is designed to work with most EC2 features
|
2017-12-25 05:03:53 +00:00
|
|
|
such as Elastic Network Adapters and NVME EBS volumes by default. If anything
|
|
|
|
|
is missing please report a bug.
|
2017-12-25 02:06:54 +00:00
|
|
|
|
2018-08-28 05:26:28 +00:00
|
|
|
This image can be launched on any modern instance type, including T3, M5, C5,
|
|
|
|
|
I3, R5, P3, X1, X1e, D2, Z1d. Other instances may also work but have not been
|
2017-12-25 02:06:54 +00:00
|
|
|
tested. If you find an issue with instance support for any current generation
|
|
|
|
|
instance please file a bug against this project.
|
|
|
|
|
|
|
|
|
|
To get started use one of the AMIs below. The default user is `alpine` and will
|
|
|
|
|
be configured to use whatever SSH keys you chose when you launched the image.
|
|
|
|
|
If user data is specified it must be a shell script that begins with `#!`. If a
|
|
|
|
|
script is provided it will be executed as root after the network is configured.
|
|
|
|
|
|
2017-12-25 05:03:53 +00:00
|
|
|
**Note:** This image will be updated as Alpine Linux changes over time and as
|
|
|
|
|
AWS adds regions. This file and
|
2018-08-19 14:31:44 +00:00
|
|
|
[release.yaml](https://github.com/mcrute/alpine-ec2-ami/blob/master/release.yaml)
|
2017-12-25 02:06:54 +00:00
|
|
|
will be updated as new regions are made available.
|
|
|
|
|
|
2017-12-25 05:03:53 +00:00
|
|
|
| Alpine Version | Region Code | AMI ID |
|
|
|
|
|
| -------------- | ----------- | ------ |
|
2017-12-26 16:58:28 +00:00
|
|
|
| 3.7 | ap-southeast-2 | [ami-7628d814](https://ap-southeast-2.console.aws.amazon.com/ec2/home#launchAmi=ami-7628d814) |
|
|
|
|
|
| 3.7 | sa-east-1 | [ami-ae5414c2](https://sa-east-1.console.aws.amazon.com/ec2/home#launchAmi=ami-ae5414c2) |
|
|
|
|
|
| 3.7 | us-west-2 | [ami-e474db9c](https://us-west-2.console.aws.amazon.com/ec2/home#launchAmi=ami-e474db9c) |
|
|
|
|
|
| 3.7 | eu-central-1 | [ami-a96ff8c6](https://eu-central-1.console.aws.amazon.com/ec2/home#launchAmi=ami-a96ff8c6) |
|
|
|
|
|
| 3.7 | eu-west-2 | [ami-9ea2bbfa](https://eu-west-2.console.aws.amazon.com/ec2/home#launchAmi=ami-9ea2bbfa) |
|
|
|
|
|
| 3.7 | ap-south-1 | [ami-29c28846](https://ap-south-1.console.aws.amazon.com/ec2/home#launchAmi=ami-29c28846) |
|
|
|
|
|
| 3.7 | eu-west-1 | [ami-66de501f](https://eu-west-1.console.aws.amazon.com/ec2/home#launchAmi=ami-66de501f) |
|
|
|
|
|
| 3.7 | us-east-1 | [ami-976020ed](https://us-east-1.console.aws.amazon.com/ec2/home#launchAmi=ami-976020ed) |
|
|
|
|
|
| 3.7 | us-west-1 | [ami-1c393f7c](https://us-west-1.console.aws.amazon.com/ec2/home#launchAmi=ami-1c393f7c) |
|
|
|
|
|
| 3.7 | ap-northeast-2 | [ami-b96ccdd7](https://ap-northeast-2.console.aws.amazon.com/ec2/home#launchAmi=ami-b96ccdd7) |
|
|
|
|
|
| 3.7 | ap-northeast-1 | [ami-361c8850](https://ap-northeast-1.console.aws.amazon.com/ec2/home#launchAmi=ami-361c8850) |
|
|
|
|
|
| 3.7 | us-east-2 | [ami-c487afa1](https://us-east-2.console.aws.amazon.com/ec2/home#launchAmi=ami-c487afa1) |
|
|
|
|
|
| 3.7 | ap-southeast-1 | [ami-25a8c059](https://ap-southeast-1.console.aws.amazon.com/ec2/home#launchAmi=ami-25a8c059) |
|
|
|
|
|
| 3.7 | ca-central-1 | [ami-293d874d](https://ca-central-1.console.aws.amazon.com/ec2/home#launchAmi=ami-293d874d) |
|
2017-12-25 02:06:54 +00:00
|
|
|
|
|
|
|
|
## Caveats
|
|
|
|
|
|
|
|
|
|
This image is being used in production but it's still somewhat early stage in
|
|
|
|
|
its development and thus there are some sharp edges.
|
|
|
|
|
|
|
|
|
|
- Only EBS-backed HVM instances are supported. While paravirtualized instances
|
|
|
|
|
are still available from AWS they are not supported on any of the newer
|
|
|
|
|
hardware so it seems unlikely that they will be supported going forward. Thus
|
|
|
|
|
this project does not support them.
|
|
|
|
|
|
2018-08-28 05:26:28 +00:00
|
|
|
- The linux-vanilla kernel all the linux-firmware packages it installs is much
|
|
|
|
|
larger than is necessary for an AMI designed to run on EC2. Unfortunately,
|
|
|
|
|
the linux-virt kernel is currently missing NVMe support, which is required for
|
|
|
|
|
the newest generation of instance families.
|
|
|
|
|
|
2018-08-01 00:55:39 +00:00
|
|
|
- The aws-ena-driver-vanilla package is still in edge/testing, and requires the
|
|
|
|
|
matching linux-vanilla package from edge/main. When ENA is available in an
|
2018-08-28 05:26:28 +00:00
|
|
|
alpine version release (ideally with a 'virt' kernel flavor), edge/testing
|
|
|
|
|
and edge/main should no longer be necessary.
|
2017-12-25 02:06:54 +00:00
|
|
|
|
|
|
|
|
- [cloud-init](https://cloudinit.readthedocs.io/en/latest/) is not currently
|
|
|
|
|
supported on Alpine Linux. Instead this image uses
|
|
|
|
|
[tiny-ec2-bootstrap](https://github.com/mcrute/tiny-ec2-bootstrap). Hostname
|
|
|
|
|
setting will work as will setting the ssh keys for the Alpine user based on
|
|
|
|
|
what was configured during instance launch. User data is supported as long
|
|
|
|
|
as it's a shell script (starts with #!). See the tiny-ec2-bootstrap README
|
|
|
|
|
for more details. You can still install cloud-init using aports but the
|
|
|
|
|
version in the tree is somewhat old and may not work correctly for Alpine.
|
|
|
|
|
If full cloud-init support is important to you please file a bug against this
|
|
|
|
|
project.
|
|
|
|
|
|
|
|
|
|
- CloudFormation support is still forthcoming. This requires patches and
|
|
|
|
|
packaging for the upstream cfn tools that have not yet been accepted.
|
|
|
|
|
Eventually full CloudFormation support will be available.
|
