Comment 10 for bug 2066999

The following packages have been tested on amd64 to ensure no regressions:

* 1.0.0-0ubuntu16.24.04.1
* 1.0.0-0ubuntu16.23.10.1
* 1.0.0-0ubuntu11.22.04.5
* 1.0.0-0ubuntu9.6

The process is the same for each release, but shown below is the example for noble.

1) Launch instance
Example of how to start it via awscli:
$ aws ec2 run-instances --region eu-north-1 --image-id ami-0b15dce563b217be3 --count 1 --instance-type t3.micro --key-name mitchell --security-group-ids sg-0e03e00997fa53926 --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=mitchdz-hibernate-test-noble}]' --metadata-options HttpTokens=required --block-device-mappings '[{"DeviceName":"/dev/sda1","Ebs":{"Encrypted":true,"DeleteOnTermination":true,"VolumeSize":24,"VolumeType":"gp3"}}]' --hibernation-options Configured=true

2) ssh into the ec2 instance

3) Update package
# cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
# apt update && apt upgrade -y
# apt install -y ec2-hibinit-agent -t noble-proposed

4) log time
# uptime | tee -a /tmp/uptime.old

5) Hibernate the instance

6) Wait for instance to be available to start, then start the instance

7) ssh into the instance

8) check /tmp/uptime.old existence and contents to be correct, meaning the time is as expected when ran the command before hibernation