1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
- Stop the broke instance
- Detach the root volume from broke instance
- Spin up an another new instance that you can log in to (it has its own root volume)
- Attach the root volume of the broke instance to the new instance
- Mount the the volume to the operating system of the new instance
- Fix the mistake
- Stop the new instance
- Detach the broke instance root volume from the new instance
- Attach the broke instance root volume to the broke instance
- Boot the broke instance.
- Broke instance now fixed instance
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Thank you, I'll try it right now, I appreciate
Hey, please can you come to resolve the issue for me? i can't attach the volume to the new instance, I saw it needs to be the same zone but I cannot find the availability zone.
Find out what subnet the broken instance is in, you can see this in the details of the ec2 instance. Click on the subnet-id, then you can see what AZ it is in.