Updating on Bottlerocket

Guidelines for Updating In-Place

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

There are some guidelines and considerations to keep in mind when updating your Bottlerocket nodes in-place. Some movements between versions are updates, some are not updates, and there are some caveats you may need to consider based on the history of the project.

Update Paths

Certain movements between releases of Bottlerocket are accessible through an in-place update path.

Between Minor or Patch Versions of the Same Variant

With the exception of moving between major versions and a caveat discussed below, it is possible to update in-place from one released version of a variant to another released version of the same variant. In particular, the following update paths work:

Locking to a Specific Release

Mon, 01 Jan 0001 00:00:00 +0000

Locking your Bottlerocket nodes to a specific release is possible using the Bottlerocket Settings API.

A quick explanation of the apiclient command used below:

Two settings are set: updates.version-lock and updates.ignore-waves.

updates.version-lock: which version of Bottlerocket to lock to when apiclient checks for updates.
updates.ignore-waves: ignore the update waves behavior and update the Bottlerocket node immediately.

To create an SSM Command Document, follow the steps in the AWS Systems Manager User Guide: “Create an SSM document (console)”. Remember to select “YAML” in the “Content” box, since the SSM Command Document below is formatted in YAML.