"Hamburg": Find the AWS EC2 volume still a md5 mismatch

[JesseRhoads]

The current version of this scenario has two volumes that match the specs given, and neither pass the md5 check.
I brute force checked, and actually NO volumes in the data set match when md5sum checked to the sums in the check.... So something is odd here.
Did the dataset change?
Also 31/09/2025 is not a valid date. September is only 30 days....

[mark-wagner]

There is a typo in the description. It is looking for the instance id, which the example object is a volume.

I don't want to provide any spoilers so I will not say anything about the other parts of your comments.

[tillschander]

Yes, the description for this one needs some improvements. Currently it is a bit misleading asking for the ID of a volume and even giving an example of a volume ID when the actual solution is an instance ID.

One of the volumes contains important data and we need to identify which volume (its ID)

e.g.: echo "vol-00000000000000000" > ~/mysolution