We have just upgraded some of out Datomic Cloud systems, but upon the 1st SSH into the new instances, we are greeted with the following update instructions:
A newer release of "Amazon Linux" is available.
Version 2023.2.20231018:
Version 2023.2.20231026:
Version 2023.2.20231030:
...
Version 2023.6.20250303:
Version 2023.6.20250317:
Version 2023.7.20250331:
Version 2023.7.20250414:
Run "/usr/bin/dnf check-release-update" for full release and version update info
, #_
~\_ ####_ Amazon Linux 2023
~~ \_#####\
~~ \###|
~~ \#/ ___ https://aws.amazon.com/linux/amazon-linux-2023
~~ V~' '->
~~~ /
~~._. _/
_/ _/
_/m/'
Last login: Wed Apr 23 07:05:19 2025
[ec2-user@ip-10-213-45-200 ~]$
which raised a few questions.
how are we supposed to keep these machines up to date, since they can be recycled any time by the autoscaling group, starting out by using the AMI specified in the cloudformation templates, which are just going to fall behind sercurity-wise as time passes?
i assumed compute group instances keep themselves up to date, by periodically applying security-patched packages.
Queries and Transactions made via the client api (e.g. not Ions). The improvements not in improving a single operations performance, but around increasing the number of concurrent operations per node by instance size. So this will affect any operation (transactions and queries) or cross node request (such as request forwarding) in query groups and primary compute groups.
This process is not done automatically, we upgrade the deps and AMIs. We are evaluating an amazon managed approach to automating this between releases. The next release for Cloud will have updated deps and AMIs.