Node AMIs
Every node in a storage cluster — control plane and data plane — boots the same
prebaked image, and its ID is the nodes_ami input to the Terraform modules.
Everything the cluster runs is already compiled and installed in it, so
provisioning only configures a node; nothing is downloaded or built at apply
time.
What is in the image
| Base OS | Ubuntu 22.04 LTS, from Canonical's official image |
| Architecture | arm64, x86_64 |
| Root volume | 30 GiB gp3 |
| Image name | mgx-storage-ubuntu<os-version>-<arch>-<build-timestamp> |
| Node scripts | /opt/mgx/scripts — setup-node.sh and its helpers |
Published images
| Region | Arch | AMI ID | |
|---|---|---|---|
us-east-1 | N. Virginia | arm64 | ami-05c3b3ac5425f273c |
us-east-2 | Ohio | arm64 | ami-05bd43d05d93a8c58 |
us-west-2 | Oregon | arm64 | ami-05967535176c9dd49 |
eu-west-1 | Ireland | arm64 | ami-04d10f2e0465499d9 |
eu-central-1 | Frankfurt | arm64 | ami-079b4b9a7262dfe23 |
ap-southeast-1 | Singapore | arm64 | ami-0fa7b05a1d44f2eaf |
ap-northeast-1 | Tokyo | arm64 | ami-0a9f5a666b1a2034e |
An AMI ID is per-region: take the row for the region you are deploying into and
set it as nodes_ami. Check that your nodes_instance_type matches the image's
architecture — an arm64 image will not boot on an Intel instance type.
Support
For a region that is not in the table, or another question, ask support@backedblock.io.