Provisioning Multi-Region AWS Infrastructure with Crossplane

Mon, 22 Jun 2026 09:34:43 +0000

Originally published on Medium on 22 June 2026.

Before we can deploy applications across multiple EKS clusters, we need the infrastructure to exist. That sounds obvious, but it is where many platforms become fragmented.

One team creates a VPC with Terraform.
Another team creates EKS clusters manually.
DNS records are created somewhere else.
IAM roles are patched during incidents.
A few resources are managed by scripts that only one person understands.

This works for a while, but it does not scale well. For a multi-region platform, we need infrastructure that is:

Building a Multi-Region EKS Platform with Crossplane, FluxCD, and GitOps

Thu, 18 Jun 2026 10:19:22 +0000

Originally published on Medium on 18 June 2026.

Multi-region Kubernetes sounds simple until you try to operate it. At first, the problem looks like this: “We need to deploy the same application to multiple EKS clusters.”

But very quickly, the real problem becomes much bigger:

Who creates the AWS infrastructure?
Who owns the EKS clusters?
How are applications onboarded?
How do we avoid configuration drift?
How do we promote changes safely?
How do we know what version is running in each region?
How do we recover when one region fails?

In this series, I want to describe a platform architecture for managing multi-region deployments on AWS EKS using Crossplane, FluxCD, GitOps, and GitHub Deployments.

Gitops on Konstantinos (Kostas) Dichalas

Provisioning Multi-Region AWS Infrastructure with Crossplane

Building a Multi-Region EKS Platform with Crossplane, FluxCD, and GitOps