Parity between Azure and AWS

It is worthwhile to maintain knowledge parity between Azure and AWS. 

If you use a cool thing in Azure, chances are the same functionality exists in AWS (e.g. managed kubernetes service - known as AKS or EKS in respective clouds) and so you should know how to do same cool thing in AWS.

Cloud economics may dictate future decisions.

Azure Kubernetes Service - Rationale for Using AKS for .NET Applications

Why use the Azure Kubernetes Service (AKS) for your .NET applications (rather than just deploy them to virtual machines)?

First, there are scalability benefits - these are ideal for microservices.

Kubernetes has "canned processes" for scaling.

Kubernetes has what's called Horizontal Pod autoscaling - which means when load increases, the system deploys more pods.  It doesn't change the dynamics of the pods themselves i.e. doesn't allocate more memory or CPU to them, it just makes more pods.