Migrate Production Infrastructure from Azure to AWS (Zero/Minimal Downtime) + IaC & Monitoring Setup

We're running a microservice-based production environment on Azure Kubernetes Service (AKS), backed by MongoDB and PostgreSQL. There's no GitOps pipeline and no Infrastructure as Code in place right now - deployments and provisioning are handled manually. We already have an AWS account set up, with CloudFront and a few S3 buckets in use. The goal is to move the entire production stack from Azure to AWS with as little downtime as possible, and come out the other side with an environment that's actually rebuildable - not something held together by tribal knowledge and manual clicks. What we need: - A migration plan and execution for moving AKS workloads to AWS (likely EKS), including MongoDB and PostgreSQL data migration with minimal service interruption - Infrastructure as Code (Terraform preferred) covering the full stack, so the environment can be torn down and rebuilt from code - A GitOps workflow for deployments going forward - we don't have one today - Monitoring and alerting for the new environment: cluster health, service-level metrics, logs, and database performance, with alerts wired up before we consider the migration done - Security best practices baked into the new setup: network segmentation, IAM least-privilege, secrets management, etc. - Integration with our existing AWS resources (CloudFront, S3) rather than standing up parallel infrastructure Ideal candidate: Someone who's done Azure-to-AWS migrations before, not just theoretical Kubernetes/Terraform knowledge. We want practical judgment on cutover strategy (blue-green, phased DNS cutover, whatever fits our setup), database migration with replication instead of a hard cutover that risks data loss, and experience setting up production-grade observability.