1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Instance storage is ephemeral - as you've discovered the data (most likely) won't survive a stop/start cycle and is not guaranteed to survive a reboot as the instance may be moved to different hardware if we detect that there is an issue with the original host.
There are many different operating systems and filesystem types - we can't predict what you will use the drive for; so it's very important that during operating system boot you check to see if the storage is initialised in the way that you need to to be. This must be done every time the operating system starts.
If you want persistent storage then EBS is the way to go.
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thank you. Are the EBS Volumes that I attach to an i4i instance different from regular EBS volumes, in that, are they somehow faster (nitro), or is it only the ephemeral storage that has the nitro architecture?
EBS is EBS no matter what the instance type. There are different classes of EBS (performance-wise) but it is all persistent stored.. However, EBS is network-attached storage so there is slightly more latency using that than instance-attached storage.