Upgrading

From time to time new versions of the On Premises AMI will be released. The upgrade operation requires far less steps than the initial installation. Basically there are 3 things we need to do:

• Launch the new AMI reusing the same Security Group as in the old instance (which is already correctly configured)

• Assign the same IAM role we used on the previous instance so that the new one can access the parameter store.

• Update the Target Group used by the Load Balancer so that we remove the old instance and add the new one.

Launch the new AMI

Since all state required by the service is stored in postgres and in AWS Param Store, we just need to launch the new AMI, but choosing manually the same Security group as we used on the previous version.

Assign the IAM Role

Chose the newly created instance and click on the Modify IAM Role option:

Choose the same IAM Role we used for the old instance:

You will need to Reboot your instance so that the new IAM role gains effect.

Update Target Groups

Next, when the instance is up and running we must also update the Target group used by our load balancer so that it points to the new instance.

Register the new target and wait until it gets "healthy".

You can now deregister the old target so that only the new one will get traffic. You should be able to navigate to the domain that points to the load balancer and test the new instance.

Finally pause or terminate the old instance since it is not used anymore.