A public AMI image is used by default for the EWAOL instance.
Release: soafee-ewaol-scarthgap-aws-ec2-arm64.rootfs-20250221030541-ewaol-scarthgap-v2.0.0-20250221030541-arm64
AMIs:
- us-east-1: ami-03f61a1fc83b7f58e
- ap-northeast-1: ami-0ee857245cfbd4a09
Source code and license agreements are built into the filesystem of this image at the following locations:
/usr/share/common-licenses//usr/share/licenses//usr/src/yocto-sources
We offer a supplementary distribution of the filesystem images, sources and license agreements in the following locations:
- s3://soafee-avp-demo/soafee-ewaol-scarthgap-aws-ec2-arm64.rootfs-20250221030541
- https://soafee-avp-demo.s3.us-east-1.amazonaws.com/soafee-ewaol-scarthgap-aws-ec2-arm64.rootfs-20250221030541
You can build your own custom EWAOL image using this repository.
AWS requires an IAM role named vmimport that is used globally across your account. The default setting in the Terraform configuration is to use an existing vmimport role.
A Terraform varaible may be set to create and manage this role for you, otherwise the role must already be available in your account to build and upload an AMI. See https://docs.aws.amazon.com/vm-import/latest/userguide/required-permissions.html for more details.
You can enable automatic management of the vmimport role in Terraform by creating the variables file terraform/variables.auto.tfvars and adding the line manage_global_vmimport_role = true.
Run blueprint ami-ewaol-build to build an EWAOL image. The image is built from the template ansible/roles/ewaol_image_builder/templates/ewaol-graviton2-ami.yaml.j2 which may be customized to your needs.
Once the image is built, set the appropriate variable in terraform to use the new EWAOL AMI and re-run terraform and subsequent steps to re-configure. You can override the default EWAOL AMI by creating the variables file terraform/variables.auto.tfvars and adding the line ewaol_ami = ami-000000000 (substituting the ARN of your AMI).
[!TIP] AWS does not provide a service-level agreement (SLA) for AMI generation: Creation of an AMI can take hours. The process is subject to failure or timeout. If this occurs, use the AWS console to monitor any pending AMIs, and then comment out the appropriate AMI names from the Ansible configuration scripts to avoid errors in duplicate AMIs. There is no known workaround for this issue.