NOTE: This is not an official AWS or Alpine project. This is community built and supported.
To get started with one of our pre-built minimalist AMIs, please refer to the README in the releases subdirectory.
Alternately, with the right filters, you can query the EC2 API to programmatically
find our most recent AMIs. For example, using the aws command line tool...
aws ec2 describe-images \
--output text \
--filters \
Name=owner-id,Values=538276064493 \
Name=name,Values='alpine-ami-*' \
Name=state,Values=available \
Name=tag:profile_build,Values=v3_10-x86_64 \
--query 'max_by(Images[], &CreationDate).ImageId'
...will list the latest AMI id from our collection of 'v3_10-x86_64' builds. Refer to the AWS CLI Command Reference for describe-images for more details.
Using the scripts and configuration in this project, you can build your own custom Alpine Linux AMIs. If you experience any problems building custom AMIs, please open an issue and include as much detailed information as possible.
- Packer >= 1.4.1
- Python 3.x (3.7 is known to work)
make(GNU Make is known to work)- an AWS account with an existing subnet in an AWS Virtual Private Cloud
Target profile config files reside in the profiles subdirectory, where you will also find the config we use for our pre-built AMIs. Refer to the README in that subdirectory for more details and information about how AMI profile configs work.
These scripts use the boto3 library to interact with AWS, enabling you to
provide your AWS account credentials in a number of different ways. see the
offical boto3 documentation's section on
configuring credentials
for more details. Please note that these scripts do not implement the first
two methods on the list.
To build all build targets in a target profile, simply...
make PROFILE=<profile>
You can also build specfic build targets within a profile:
make PROFILE=<profile> BUILDS="<build1> <build2>"
If the packer binary is not in your PATH, or you would like to specify a
different one, use...
make PACKER=<packer-path> PROFILE=<profile>
Before each build, new Alpine Linux releases are detected and the version's core profile is updated.
If there's already an AMI with the same name as the profile build's, that build will be skipped and the process moves on to build the other profile's build targets (if any).
After each successful build, releases/<profile>.yaml is updated with the
build's details, including (most importantly) the ids of the AMI artifacts that
were built.
Additional information about using your custom AMIs can be found in the README in the releases subdirectory.
Every now and then, you may want to clean up old AMIs from your EC2 account and
your profile's releases/<profile>.yaml. There are three different levels of
pruning:
revision- keep only the latest revision for each releaserelease- keep only the latest release for each versionversion- remove any end-of-life versions
To prune a profile (or optionally one build target of a profile)...
make prune LEVEL=<level> PROFILE=<profile> [BUILD=<build>]
Any AMIs in the account which are "unknown" (to the profile/build target, at least) will be called out as such, but will not be pruned.
This make target updates the releases README, primarily for updating the list of our pre-built AMIs. This may-or-may-not be useful for other target profiles.
make release-readme PROFILE=<profile>
make clean will remove the temporary build subdirectory, which contains the
resolved profile and Packer configs, the Python virtual environment, and other
temporary build-related artifacts.
-
New Alpine Linux versions are currently not auto-detected and added as a core version profile; this process is, at the moment, still a manual task.
-
Although it's possible to build "aarch64" (arm64) AMIs, they don't quite work yet.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent