In my previous post, I installed Google Cloud SDK in a Windows Subsystem for Linux environment. Here I’ll document setting up Cloud Code extension for Visual Studio Code so that we can easily interact with Google Cloud from within the IDE.

In my previous post, I showed how I’ve setup my development environment on Windows with Visual Studio Code and Windows Subsystem for Linux. Here I’ll document how to setup Google Cloud SDK in WSL environment.

More and more developer are relying on open source tools and libraries that are UNIX/Linux native. This is especially true for web and other applications that are deployed on public cloud. While I recommends a dedicated Linux development environment, this may not be possible for a lot of developers working on company issued Windows desktop/laptops. For these developers, Windows Subsystem for Linux (WSL) provides a Linux VM that is tightly integrated with the familiar Windows experience. Using the WSL extension for Visual Studio Code further simplifies the experience.

A step-by-step walk-through of installing OpenShift (on AWS) with Installer-provisioned Infrastructure using manual credentials mode.

I wrote about the AWS resources created by OpenShift installer in my earlier post. In this post, let's take a closer look at IAM credentials used by OpenShift on AWS.

The simplest way to install OpenShift on AWS is to make use of the IPI (Installer Provisioned Infrastructure) method. With IPI, the installation process will provision the necessary VPC and other infrastructure resources, and then install OpenShift onto the provisioned infrastructure. Sounds good, but to the curious (and paranoids), exactly what AWS resources were created by the installer? Let's take a look.