Cost savings in the cloud are extremely important for small-sized technology businesses. In this article, I share some insights on saving costs while working with Amazon Route 53. I also discuss how to prevent DNS issues when recreating hosted zones.
I remember having to terminate an entire Amazon EC2 instance because I somehow lost access to it via SSH. Well, looking back, termination really wasn’t necessary. Using the simple process described here, you can easily regain access to the AWS EC2 instance that you locked yourself out of.
My previous article on the subject of adding a swap file to an Amazon EC2 instance focused on adding the swap file to the instance storage (also known as ephemeral storage) that comes with certain Amazon EC2 instances. This article discusses how you can still leverage the concept of swap files even on “EBS only” Amazon EC2 instances.
Amazon Web Services (AWS) makes it very easy to expand EBS volumes. You just right-click on the volume, select modify, and enter the new, larger volume size. Done. To shrink Amazon EBS volumes, however, is a whole different matter – there is no way to do this directly using the AWS console. In this article, I describe a roundabout technique that I have often used to save some bucks in scenarios where I mistakenly over-allocated Amazon EBS when setting up EC2.
Here I explain the second method to speed up your WordPress site using Amazon’s CDN. To get background information on the process described here, please read my previous post: Speed Up WordPress With Amazon S3 And Cloudfront (Part 1).
With just a bit of extra effort, you could get significant page speed improvements on your WordPress website by using Amazon’s Content Delivery Network (CDN). This is because Amazon has robust servers all over the world that can serve your content much faster than the single shared hosting server that your WordPress site is most likely installed on.