Skip to main content

AWS view instance store volume - ephemeral storage

Instance store volume in AWS is not like the EBS Volume (ebs - elastic block storage).
The main difference between EBS and instance store volume, is EBS data or its contents will persist after reboot or shutdown.
And for EBS volume you can take snapshot, create image do a backup or simply attached the EBS volume to another instance.
Where as for instance store volume, which is physically attached to the host. It can't be search or can't be found on the "Volume" navigation pane. Thus, snapshot or taking backup is not possible.
Instance store volume is some sort of a RAMDisk, in which it is indeed process data quite fast.
However, if the instance is rebooted or shutdown all data is gone.
Ideal only for dynamic data processing, that once data is process on the fly; data can be discarded or not needed anymore.


How to view or check whether the instance you have got instance store volume?
In a Linux instance, type the command below on a Terminal window:
lsblk -o +SERIAL

Type the command as it is including the capital letters.
After successfully typing the command it will show an output similar below.
Serial labelled as vol-xxx is an EBS volume which can be found on the Volume Navigation Pane of the AWS interface.
Whereas, the disk with the label AWSxxx is an instance store volume, which is technically part of the instance subscription and is used as a RAMDisk or an ephemeral storage.
Sample output:

Do not put crucial or important data to an ephemeral storage such as an instance store volume, unless there is some sort of a backup or a real-time synchronization to a storage that will persist after reboot or shutdown.





Let your faith be stronger than your fears.
Hold on to Jesus for He is always at your side.
Pray and cast all your worries upon Him.
God never fails, He give us graces according to His abundance.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more