Cloud architecture, DevOps & apps / by Abdul Aziz

Blogdoang: Cloud,
simply

Cloud platforms and the apps on them, built step by step.

Platforms on Google Cloud, AWS and Azure, and the web and mobile apps that run on them: built with Infrastructure as Code, zero trust and automated delivery, and documented so your team can run them.

Fig. 1 · Eight steady steps, then the last piece clicks into place.

Practice

From the network up to the apps your users touch. Each step stands on the one before it.

What Blogdoang covers.

  • 01

    Cloud architecture & migration

    Multi-cloud and hybrid designs on Google Cloud, AWS and Azure, and migrations between them without downtime.

  • 02

    DevOps & Infrastructure as Code

    Terraform and Ansible for every environment, and CI/CD on Jenkins, GitHub Actions and Cloud Build.

  • 03

    Security & compliance

    Zero trust access, Cloud Armor, WAF, SCC and SIEM, and getting platforms ready for audits such as PCI DSS.

  • 04

    AI & data pipelines

    Data lakes, document extraction and OCR with Gemini, OpenAI, Vertex AI and Amazon Bedrock.

  • 05

    Observability & operations

    Prometheus, Grafana, New Relic and Cloud Operations, with an eye on availability and cost.

  • 06

    Web & mobile apps

    Web apps on FastAPI, Laravel and PostgreSQL, and native Android apps for phone, car and TV.


Selected work

Clients and employers stay anonymous.

Problems solved, step by step.

  1. 01 / Product company AWS · Google Cloud · Terraform · Ansible

    Google Cloud to AWS, zero downtime

    1. Challenge

      Every production and staging workload had to move from Google Cloud to AWS while the product stayed live.

    2. Approach

      Designed the target environment on AWS, codified it in Terraform and Ansible, and cut over one environment at a time.

    3. Result

      All workloads on AWS with zero downtime during the move.

  2. 02 / Product company SonarQube · Wazuh · Vaultwarden · Jenkins · GitHub Actions

    A self-hosted DevSecOps platform

    1. Challenge

      Code quality, threat detection and credentials were handled differently by every team.

    2. Approach

      Rolled out SonarQube, Wazuh SIEM and Vaultwarden, wired into CI/CD on Jenkins and GitHub Actions.

    3. Result

      One shared stack for code quality, threat detection and secrets, and repeatable deployments.


Apps

Web and mobile apps, built and shipped.

Also built

  • Web backend · AI Agentic AI Marketing Pipeline
  • Geospatial Land Suitability Analysis Engine
  • Geospatial Geospatial Biodiversity Engine
  • Web app OKR Management System
All projects →

Method

The same four steps behind every project and every note.

Name it, draw it, run it, prove it.

  1. Step 01

    Name it

    Start from the real situation: what runs today, where it hurts, and what “done” looks like.

  2. Step 02

    Draw it

    Sketch the path a request, a packet or a deploy takes, before touching a console.

  3. Step 03

    Run it

    Change one thing at a time, in code (Terraform, Ansible, CI), so every step can be repeated.

  4. Step 04

    Prove it

    Finish with a check that shows it works, then write it down as a runbook.




Behind Blogdoang

Let’s build something that clicks into place.

I’m Abdul Aziz, a cloud architect, DevOps engineer and app developer with 10+ years in cloud and infrastructure. Blogdoang is my practice, and these notes keep the work honest: every fix written down so it can be repeated.

  1. 01 You write in A few lines on what runs today and what should change.
  2. 02 We map it One call to trace where it hurts and what “done” looks like.
  3. 03 You get a plan Written steps, in order, that your team can run with or without me.
Fig. 2 · From a first message to a plan.