Click an object in the room, or scroll down to the case files.
Night. Rain on the glass. Somewhere a pipeline is still running.
This is the case room. Every project is a case; every architecture is evidence.
Nothing on these walls claims more than the record supports.
06 cases on file. The investigator is in. Choose an object to begin.
Investigator dossier
Ibnu Adzim
Cloud infrastructure, DevOps automation, backend and data systems, IoT
Handle
@Sann2267
Location
Indonesia
Cases
06 on file
Cloud infrastructure on AWS
DevOps and CI/CD automation
Backend and data pipelines in Python
IoT telemetry and dashboards
I build cloud, DevOps, backend, data, and IoT systems, mostly in Python on AWS.
The case files in this room come from two sources. Three of them are Cloud Computing
modules from LKS Nasional 2026 (Indonesia's national vocational skills competition),
worked through on AWS Academy Learner Lab: a CI/CD platform on self-hosted GitHub Actions
runners, an end-to-end analytics platform, and a multi-tenant Kubernetes SaaS with
cross-region disaster recovery. The others are my own systems: an Instagram job-vacancy
scraping pipeline, the full-stack dashboard that runs on top of it, and an ESP32
environment monitor on AWS IoT Core.
Every case states what was documented, what was built, and what was only planned. Nothing
here claims a metric the source material does not support.
A local Python pipeline that collects publicly visible Instagram job-vacancy posts across Indonesia's 38 provinces, reads the flyer images with OCR, extracts and normalises the vacancy fields, deduplicates within and across runs, and stores structured output as JSON, JSON Lines, CSV, and SQLite.
A FastAPI and React dashboard over the scraped job corpus. The API serves the corpus read-only with a per-user layer for saved jobs, an admin operations page queues scraper runs for a worker process that reports progress back through the database, and an optional AI layer answers questions over the same filtered data.
A CI/CD platform for four containerised Lambda microservices, built inside a private VPC because managed CI/CD services are unavailable in the lab. GitHub Actions run on self-hosted EC2 runners in private subnets, images go to ECR, REST and WebSocket API Gateways expose the functions, and CloudWatch, VPC Flow Logs, Secrets Manager, and Cognito cover observability and security.
A five-layer data platform: CSV batches land in S3 and user events stream through Kinesis; Glue, EMR, Step Functions, and EventBridge transform and orchestrate; Redshift, DynamoDB, and S3 store history, real-time metrics, and the lake; Lambda behind API Gateway serves five endpoints protected by WAF and API keys; a dashboard on Amplify shows GMV, sales, funnel, and ML segments.
A multi-tenant SaaS platform on Amazon EKS across two regions: a dual-VPC design in Virginia separating application and data, namespace-isolated tenants with restricted Pod Security Standards and NetworkPolicy, an event-driven audit pipeline, Grafana on ECS Fargate, blue/green canary releases through CodeDeploy, and an Oregon standby with Aurora Global Database and S3 cross-region replication.
An ESP32 reads temperature and humidity from a DHT22 and publishes JSON over MQTT to AWS IoT Core, authenticated with an X.509 device certificate over TLS. Node-RED subscribes to the topic, applies the data logic, and renders gauges, a 24-hour trend, and threshold alerts on a dashboard that is reachable from anywhere.