Hamza A.

I keep production Kubernetes on GCP and AWS fast, stable and secure, and I get cloud environments through security reviews without stalling the engineering team. Top Rated Plus, 100% Job Success, $50K+ earned here. WHERE I USUALLY COME IN - A SOC 2, ISO or customer security review is coming, and IAM, secrets, logging and network access are loose - A GKE or EKS cluster is unstable, over-provisioned, or nobody on the team wants to touch it - Pages at 3am, and nobody knows which alert actually matters - Every new environment is a ticket and a week of copy-pasted Terraform - Deploys need someone watching them, and rollbacks are manual - The cloud bill is growing faster than traffic - You are moving between clouds, or off hand-built servers, and cannot afford downtime WHAT I HAVE DELIVERED - Took a US AI/SaaS platform from failed Drata scans to passing SOC 2 checks. Tightened IAM and password controls, enabled CloudTrail, VPC Flow Logs, CloudWatch alarms and SNS alerting, enforced EBS and S3 encryption, and set up DynamoDB point-in-time recovery and AWS Backup. - Migrated a SaaS platform from Amazon ECS to EKS with zero customer-facing downtime. Terraform for EKS, VPC, IAM and Karpenter, ECS task definitions rebuilt as Helm charts, delivered through Argo CD, with production traffic shifted gradually at the load balancer. - Rebuilt a financial trading platform on AWS to 99.95% availability with zero critical downtime, cutting deployment time by 80% and manual changes by 90%. - Secured a GCP environment hosting AI models and APIs, and currently hold a senior security engineering contract covering both cloud and bare-metal infrastructure. WHAT I DO Cloud security and compliance readiness. Least-privilege IAM, secrets handling with Vault and Secret Manager, audit logging, encryption at rest and in transit, public exposure and network review, backup and disaster recovery, and control remediation for SOC 2 through Drata or Vanta. Production Kubernetes. GKE and EKS with Helm and Argo CD, autoscaling, network policies, pod disruption budgets, resource right-sizing, and the cluster troubleshooting that tends to happen at bad hours. Infrastructure as Code. Terraform modules, remote state, multi-environment and multi-project layouts, drift control, and refactoring inherited Terraform that nobody on the team understands anymore. CI/CD. GitHub Actions, GitLab CI, Cloud Build and CodePipeline. Canary and blue-green rollouts, and rollbacks that hold under pressure. Observability and reliability. Prometheus, Grafana, Loki, OpenTelemetry, Datadog and Cloud Monitoring. SLOs and error budgets, alerts your team acts on instead of muting, incident response and postmortems. Cloud and cost. GCP across GKE, Cloud Run, Cloud SQL, VPC and IAM. AWS across EKS, ECS, RDS, VPC and IAM. Right-sizing, autoscaling, committed-use discounts and Savings Plans. HOW I WORK Everything lands in code, is reviewed in pull requests, is documented, and is handed over so your team can run it without me. I work as part of Cloudico, so when a project needs a second engineer or coverage outside my hours, that is available rather than a reason to stall. I will tell you when something is a bad idea before you pay me to build it. START HERE Send me what is failing: the audit you have to pass, the cluster nobody trusts, the bill, or the 3am page. I will tell you what I would check first and whether I am the right person for it. If I am not, I will say so.