Pin the image a connection launches
By default, each cloud node a connection launches boots the newest Ubuntu LTS image of the day. Pin an image when every new node must boot exactly the same one, for example while you check a new release before taking it. A pinned image ages: it misses the updates published after it, so Jaah reminds you to re-pin it once it is more than 30 days old.
Who can do this: org admins with permission to view system settings, on a plan with cloud nodes.
Before you start: have the id of the image you want, from your cloud account. On AWS it is an AMI id
that starts with ami-.
Pin an image
- In the sidebar, select Directory, then the Networks tab, then Connections if the page shows tabs.
- Read the image column. Newest and an image name means nothing is pinned; an image id with an age,
such as
ami-0abc… · 12d, is a pin. - Select the connection's row, then the Advanced tab.
- Enter the image's id in Image (AMI id) on AWS, or Image on another cloud. Left blank, the field reads Newest … at each launch.
- Select Save. Jaah checks that the image exists in the connection's account and region; if it doesn't, the field says why and nothing is saved.
- Check the field's hint: it now reads Pinned 0 days ago.
Pinning changes only new launches. Nodes already running keep the image they booted. Windows nodes always boot the newest Windows Server image.
Re-pin when it falls due
A pin older than 30 days shows in amber with ⚠ on the Connections list, and its hint reads — re-pin due.
- Open the connection's Advanced tab.
- Replace the id in Image with a newer image's id. Saving the same id again keeps its old age.
- Select Save. The amber mark is gone and the age starts again from 0 days.
To stop pinning, clear Image and select Save: new nodes boot the newest image again.
Related
- Connect a cloud account — add the connection in the first place.
- Add a node — launch a cloud node through the connection.
- Networks — every field of a connection, per provider.