The t1.micro instance comes with only 602MB of memory. Especially under high load, it is quite easy to deplete the available memory – and since no swap space is enabled by default, this can quickly lead to a server becoming … Continue reading
My EC2 instances are setup to have only the operating system and program files on the root volume, with all other data (logs, mail, etc.) on a second EBS volume. This leads to a very stable root volume, which sees … Continue reading
Following the significant disruption of EBS volumes in April, the importance of backups was once again brought to the forefront. Amazon’s method of generating EBS backups is the ‘snapshot’ – a differential backup stored in S3. While Amazon provides tools … Continue reading
Update: the complementary article to this one, on Rotating EBS snapshots has now been posted. After the recent failure of EBS volumes on Amazon’s cloud, backup is quite likely something to be considering. If, during the aforementioned incident, recent snapshots … Continue reading
While instances backed with EBS-root volumes do cost a bit more than the equivalent instance-store images (there is a cost for I/O), they have certain advantages – persistence and ease of replacement being notable. This article will focus on the … Continue reading
One of the great uses of EBS volumes is there persistence, however, there often comes a time when the data outgrows the original size of the volume. It is a fairly easy matter to remedy this, however, there does tend … Continue reading