1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Take that snapshot from the production instance that you created earlier and create a new volume and attach it to a running troubleshooting instance that you have access to. Mount the volume to the OS and then start looking through the logs to find the root cause.
Once you find the root cause, stop the production instance, detach the volume, attach it to the troubleshooting instance, fix the issue, detach from troubleshooting instance, attach back to prod instance, and start production instance.
Consider using Sessions Manager to connect to the instance in the future.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
Thanks. How do I attach a snapshot to a running troubleshooting lightsail instance?
It seems to be ec2 only.... https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-attaching-volume.html
In Lightsail, I get
There are no disks in Ireland, Zone A that you can attach to this instance.
Despite the fact I have two separate instances running