Leaves Heritage Hub
Microservice platform for AI-generated stories, AI portraits, a media vault and a family hub that enables interactive engagement.
Role: Team Lead · DevOps · Developer
Beyond writing code, I own how it runs: automated pipelines, infrastructure as code with Terraform, containerised microservices, hardened networks and systems that scale with the business — hands-on with 39 AWS services, and at home on Azure, GCP, Cloudways and Hostinger.
What I handle
The infrastructure side of a product — set up properly, automated, and ready for growth.
Cloud infrastructure defined in Terraform — declarative, version-controlled and reproducible across environments.
Automated build, test and deploy pipelines so releases are fast, repeatable and low-risk.
Containerised apps that run the same everywhere — from a laptop to production.
Set up, harden and monitor infrastructure on the platform that fits the product and budget.
Production-ready Nginx and Apache configuration in front of your applications.
Keep response times low as traffic grows — without outages.
Clean, well-indexed schemas and the right data store for each job.
The right structure for where the product is today — and where it's going.
Comfortable on the command line, managing and maintaining Ubuntu servers.
How I work
No big-bang rewrites — steady improvements you can see at every step.
Review the current setup, bottlenecks and risks
Agree on architecture, platform and priorities
Pipelines, containers and repeatable deployments
Caching, load balancing and performance tuning
Monitoring, updates and a healthy system
Microservices on AWS
The layers I built and ran on Leaves Heritage Hub — from the edge where users arrive, down to the network, security and operations underneath.
Provisioned as code with Terraform
Every layer below is defined in Terraform: declarative, version-controlled configuration. Changes are previewed with a plan, reviewed and applied, and tracked state keeps environments consistent and reproducible.
Users reach a global CDN over HTTPS, filtered by a web firewall and DDoS protection.
Load balancers and an API gateway route each request to the right service.
Each microservice runs as a container on ECS with Fargate; Lambda handles event-driven tasks.
Services talk asynchronously through queues, topics and an event bus; emails go out via SES.
Relational and NoSQL data, pooled connections, Redis caching and object storage for media.
Everything sits in a VPC: public and private subnets, controlled egress and private service endpoints.
Least-privilege access, managed secrets, encryption keys and continuous threat detection.
Metrics, logs and alarms, a full audit trail, compliance checks, backups and cost tracking.
AWS · Azure · GCP
Experience gained building and running microservices on AWS. The same building blocks exist on Azure and GCP under different names — so the architecture carries across clouds.
Resizable virtual servers in the cloud, with full control over the OS, instance size and scaling.
Managed container orchestration that runs, scales and deploys Docker containers — the backbone for microservices.
Private, secure registry for Docker images, integrated with ECS, with image scanning and lifecycle rules.
Serverless compute for containers — run ECS tasks without managing servers, paying only for what runs.
Event-driven serverless functions that run code on demand and scale automatically, even to zero.
Global CDN that caches and delivers content and APIs from edge locations close to users, over HTTPS.
Issues and auto-renews free SSL/TLS certificates for load balancers, CloudFront and API Gateway.
Layer-7 load balancer that routes HTTP/HTTPS traffic by path or host — ideal for routing to microservices.
Layer-4 load balancer for TCP/UDP traffic with ultra-low latency, static IPs and very high throughput.
Managed front door for APIs — routing, authentication, throttling and versioning for backend services.
An isolated private network in the cloud, with full control over IP ranges, routing and connectivity.
Segments of a VPC — public subnets for load balancers, private subnets to keep apps and databases hidden.
Connects a VPC's public subnets to the internet for inbound and outbound traffic.
Lets services in private subnets reach the internet (updates, external APIs) without being reachable from it.
Stateful firewalls around each resource that allow only the ports and sources a service actually needs.
Stateless, subnet-level allow/deny rules that add a second layer of network defence.
Private connections from the VPC to services like S3 or ECR — traffic never crosses the public internet.
Highly durable object storage for files, media, backups and static assets, with fine-grained access control.
Managed relational databases (PostgreSQL, MySQL) with automated backups, patching, Multi-AZ and replicas.
Pools and shares database connections so many services or functions don't overwhelm the database.
Managed Redis for in-memory caching, sessions and fast lookups — cuts database load and response times.
Serverless NoSQL key-value database with single-digit-millisecond performance at any scale.
Controls who and what can access each resource, using roles and least-privilege policies.
Stores and rotates database passwords, API keys and secrets, delivered securely to services at runtime.
Creates and manages encryption keys used to encrypt data at rest across storage and databases.
Web application firewall that blocks attacks like SQL injection, XSS and bad bots before they reach the app.
Managed DDoS protection that keeps applications available during large-scale attacks.
Continuous threat detection that watches account and network activity for suspicious behaviour.
Managed message queues that decouple microservices and absorb traffic spikes with reliable background jobs.
Pub/sub messaging that fans one event out to many subscribers — queues, functions, email or SMS.
Serverless event bus that routes events between services with rules, plus scheduled jobs.
Scalable email sending for transactional mail like sign-ups, password resets and notifications.
Central monitoring with metrics and dashboards across cloud resources and applications.
Collects, stores and searches application and service logs in one place for fast debugging.
Alerts on thresholds like CPU, errors or latency — and can trigger notifications or auto-scaling.
Records every API call and account action for auditing, security analysis and compliance.
Tracks resource configuration changes over time and checks them against compliance rules.
Visualises and analyses cloud spend to find savings and keep the monthly bill under control.
Centralised, policy-based backups across databases, storage and compute, with retention rules.
Toolkit
What I use day to day to build, ship and run production systems.
In practice
Microservice platform for AI-generated stories, AI portraits, a media vault and a family hub that enables interactive engagement.
Role: Team Lead · DevOps · Developer
Across every product I lead
At ICODERZ I own DevOps end-to-end — CI/CD pipelines, cloud deployments and performance optimisation — alongside architecture and delivery.
Tell me where it hurts — I'll help you fix it and set it up to scale.
Get in touch