In my previous articles, I have covered the first three Amazon Leadership Principles. If you haven’t read them, here are some links:

In this chapter, we will cover the most misunderstood principle:

Are Right, A Lot

Photo by Pablo García Saldaña on Unsplash

Amazon’s definition goes as follows:

Leaders are right a lot. They have strong judgment and good instincts. They seek diverse perspectives and work to disconfirm their beliefs.

Amazon wants everybody to make good decisions, and this is where this principle kicks in.

I knew I have said that Amazon wants you to think everybody is a leader in the project, but this principle mainly applies to the real…

Quick links to the previous articles in this series:

Invent and Simplify

Photo by Terry Vlisidis on Unsplash

Personal note: I’m always a simple person, and I shoot for technical excellence and simplicity. I truly believe in “do one thing and do it right” and “less is more.” That’s why this is my personal favorite. In a world where the entropy is increasing all the time, I do my best to reduce complexity. If O(n) could do it, I wouldn’t stop at O(n log n) only because it’s “good enough.”

Amazon’s definition goes as follows:

Leaders expect and require innovation and invention from their teams and always find ways…

Some cloud, at some Fjord in Norway

In my last article, I talked in depth about Terraform about how it works, some advantages and disadvantages, and best practices. If you haven’t read it yet, here’s the link to it:

Given the benefits and disadvantages of Terraform, it could be a go-to option for many people who want to get started managing their cloud infrastructure as code. However, there are certain cases that you might want to consider other options, and let’s go over them one by one.


CloudFormation is AWS’s answer to Infrastructure as code. It was launched in 2011, way earlier than Terraform, and over the…

In my previous article (and the very first of this series,) I explained the first leadership principle — customer obsession. If you haven’t read it yet, here’s a link to it:

Today, we are going to talk about the second leadership principle:


Photo by Tierra Mallorca on Unsplash

Amazon’s definition goes as follows:

Leaders are owners. They think long term and don’t sacrifice long-term value for short-term results. They act on behalf of the entire company, beyond just their own team. They never say “that’s not my job.”

Like the previous principle — customer obsession, this one is also one of the most important principles, especially…

It’s so famous that probably you already have heard of them: it’s Amazon’s leadership principles.

Photo by Jehyun Sung on Unsplash

In this series, I will explain in-depth every single one of all the 14 leadership principles — what they are, how they are defined, how they are used in everyday work, how you know you are doing it right or wrong. At the end of this series, I will also explain the STAR interview technique and which ones I think are the more important principles.

If you want to land a job in Amazon and you have heard that learning these leadership principles is extremely…


Security is job zero. It’s even more important than any number one priority.

Data security means protecting the data, such as those on a disk or in a database, from destructive forces and the unwanted actions of unauthorized users, such as a cyberattack or a data breach. It’s the practice of protecting digital information throughout its entire lifecycle.

When we talk about unauthorized access, corruption, or theft, there are basically two major possible ways to get the data:

  • The attackers get access to the storage system. For example, they hack into the server or even steal the physical disk.
  • When…

Some art from Kröller-Müller Museum, Netherland.

Disclaimer: I am supposed to talk about deployments following up on the previous chapter. The order of this article in the DevOps series isn’t correct.

A Story

It was not quite long ago, and I was working on a huge B2C financial project which impacts hundreds of millions of users in Europe.

The project had long started before I joined, and when I joined as the infra guy in July, I was told that I only got three months before the release, which would happen in October.

So, yeah, I got three months, that should be more than enough, I told myself…

Marina Bay, Singapore

In the previous chapter, we have discussed Continuous Delivery and Continuous Deployment in length. If you haven’t read it yet, here’s the link to it:

In this chapter, we are going to talk about GitOps.

GitOps — Pushing Continuous Deployment to the Next Level

GitOps is defined as a way of implementing Continuous Deployment for cloud-native applications. It focuses on a developer-centric experience when operating infrastructure by using tools developers are already familiar with, including Git and Continuous Deployment tools.

The definition above doesn’t say much, does it? But, even if you haven’t heard of the concept quite often, chances are, you probably have already been using it:



In earlier chapters, we have covered Continuous Integration (CI), why testing is essential to CI, and how to manage versions with CI.

If you haven’t read those chapters yet, here are some links:

After your code is automatically integrated into your source code management system with high-quality tests in place, the next step you want is to deploy them to an environment, and hopefully in an automated fashion. This is where Continuous Deployment kicks in.

Continuous Delivery V.S. Continuous Deployment

CD can mean both Continuous Delivery and Continuous Deployment.

We read and hear these two terms a lot, and you might get asked quite often…

Flowers for Algernon, Chinese Edition.

Versions, Versions

We all know a thing or two about versioning already.

If you are a Windows user, you probably know Windows 7, 8, and 10.

If you use a mac, you probably are familiar with macOS 10.14, 10.15, or the latest 11 (maybe you know them by the code instead of a number like macOS Mojave, Catalina, and the Big Sur.)

Apparently, people like to put a number to the software. Why is this important?

Versions: Contracts

A version is basically like a contract: it assures you, if you use this version number, if it behaves like this today, it will continue behaving…

Tiexin Guo

Sr. DevOps Consultant | Global Financial Services | Professional Services at AWS

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store