Updating the Gitpod Dedicated Infrastructure

Occasionally, it is necessary to update your Gitpod Dedicated infrastructure components to improve performance, reliability, and security. This guide explains how to apply these updates using CloudFormation templates. Most application updates can be applied directly and do not require infrastructure changes. See Deployment and Updates for more information about those.

Gitpod Dedicated Infrastructure Update Process

1. The existing Gitpod CloudFormation stacks are updated via automatically generated changesets. Your Gitpod Account Manager will share these in the form of deeplinks to these changesets that then need to be executed (i.e. accepted) by the user. Note that you may receive either one or two deeplinks depending on the updates required.

2. If you receive two deeplinks for two separate CloudFormation updates, apply them in this order:

   • First, update the stack for the infrastructure creation role (gitpod-role). Follow the instructions from step 3 below.
   • Then, update the stack for the Gitpod Infrastructure (gitpod-instance). Follow the instructions from step 3 below.

3. Executing the changeset by doing the following:

   • Open the deeplink provided (note the order of execution highlighted above). If desired, validate the changes to be made.

   • Press Execute changeset in the top left corner of the UI:

   • Confirm the execution as follows:

   • Wait for the execution to finish. Depending on the update, this can take a while. See the Infrastructure Update Changelog for guidance.

Consult the Infrastructure Update Changelog or your Gitpod Account Manager to determine which stacks need updates and the impact of the update in terms of downtime.

If you require the raw CloudFormation template to update your instance, please consult your Gitpod Account Manager. Ensure you always apply the CloudFormation updates in the right order (role first!).