i4i Instance type. NVMe ssd drive has to be initialized with each restart apparently

0

Hello, I stopped the instance, knowing that the data on the NVMe drive was going to disappear. However, I did not expect that the drive would need to be reinitialized again. I want to keep my tempdb from SQL on there and if the node crashes and restarts, I would ideally like that drive to be accessible again without me having to do anything. 2nd question. is it only NVMe instance store drive that is a Nitro drive? Or, when I specify the other EBS volumes that I want to attach, are those automatically Nitro SSD's or something else? Thanks

asked a year ago578 views
1 Answer
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.

profile pictureAWS
EXPERT
answered a year ago
  • 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.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions