I ran into problems with my AWS Lightsail instance: it exceeded the CPU burst quota for too long and was suspended, and I couldn't figure out how to un-suspend it.
\nI had a snapshot of the hard drive and I wanted to recover the data from it. This ended up taking far longer than I expected - I imagine there's a better way of doing this but here's how I solved it.
\nShort version: I migrated the snapshot to EC2, then launched an EC2 instance and mounted that snapshot as an EBS volume.
\nLong version (because I had to figure out a lot of steps along the way):
\nsnap-02a530e12a34\n/dev/sdb with the snapshot identifier I found in the previous step. I started this instance with a keypair so I could SSH into it.scp (with the keypair) to copy off the dataI hadn't worked with EBS before so this took some figuring out. My instance was configured with /dev/sdb as an EBS volume. I confirmed that the data was accessible like so:
[ec2-user@ip-172-31-26-179 dev]$ sudo file -s /dev/xvdb\n/dev/xvdb: x86 boot sector; partition 1: ID=0x83, active, starthead 32, startsector 2048, 167770079 sectors, code offset 0x63\nThen I created a /data directory and mounted the volume:
[ec2-user@ip-172-31-26-179 dev]$ sudo mkdir /data\n[ec2-user@ip-172-31-26-179 dev]$ sudo mount /dev/xvdb1 /data\nI actually tried sudo mount /dev/xvdb /data first and got a mount: /data: wrong fs type error - this StackOverflow answer helped me solve that.