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.
Connecting to databases via SSH Tunneling is something developers and IT professionals often need to do. And HeidiSQL is one of the more popular open-source database tools. While HeidiSQL fully supports SSH tunneling, there doesn’t seem to be any documentation about how to accomplish this. So, after struggling with this for a few hours and figuring it out, I put these instructions together to help others.
These days, cloud solution providers everywhere are marketing “serverless” solutions. While serverless computing is not at all new, it is getting a lot more attention due to the increasing popularity of DevOps and cloud in general. The promise is that serverless will eventually replace how developers currently create software and how this software is managed in production by operations. This article provides an introductory look at serverless. What exactly is it? And what additional advantages does it offer to the DevOps process?
Part 4 of my series on setting up a SharePoint 2016 development farm in Azure. In this article, we will perform the actual SharePoint 2016 installation. This will be a virtual machine (spVM) in the virtual network we created in Part 2 of this series. We will make spVM a member of the Windows Server AD domain, and then create a new SharePoint farm.