DevOps & Cloud

I build cloud systems that work.

I'm Sammy, a DevOps and Cloud Engineer in London. I build, automate and troubleshoot AWS infrastructure using Terraform, Docker and GitHub Actions.

See my work ↓GitHub ↗LinkedIn ↗

AWS infrastructure

Terraform IaC

GitHub Actions CI/CD

CORE TECH STACK

AWSCloud infrastructure

TerraformInfrastructure as code

DockerContainers

GitHub ActionsCI/CD automation

LinuxSystems and Bash

GitVersion control

FEATURED PROJECT

SammyPulse

A real AWS deployment showing how I build, secure, automate and troubleshoot a service from end to end.

AWS ECS FARGATE

Request path

User→Route 53→HTTPS→ALB→ECS

GitHub Actions→ECR→Fargate

Uptime monitoring on AWS

Containerised Gatus and deployed it on ECS Fargate. Terraform manages the infrastructure and separate GitHub Actions workflows handle application delivery and infrastructure changes.

AWSTerraformDockerECSOIDCCloudWatch

HTTPS through ACM, Route 53 and an ALB
Restricted task traffic to the ALB on port 8080
Commit SHA image tags and automated health checks
SSM secrets, CloudWatch logs and failure alerts

View repository ↗Read case study

NOW BUILDING

What’s Your Anime?

Pick a character and preview your match.

Select a character to reveal a recommendation

ECS V2 · IN PROGRESS

Anime recommendations built as a multi-service platform

I love anime but struggled to understand my own taste and find recommendations that genuinely matched it. This app turns a user’s favourites into a genre profile, five matches and a reason behind each one.

Behind the experience, I’m building three containerised services on ECS Fargate and focusing on traffic routing, asynchronous work, caching, security and reliable deployments.

AWS ECS FargateApplication Load BalancerAWS WAFElastiCache RedisAmazon SQSDynamoDBTerraformGitHub Actions + OIDC

Three separate ECS services keep the user interface, recommendation logic and background event processing independent.

Redis caches common results for faster responses. SQS moves click events out of the request path so the worker can process them reliably.

WAF protects the public entry point, OIDC removes stored AWS keys, and Terraform makes infrastructure changes repeatable and reviewable.

Architecture is in progress and will be refined as I test each tradeoff.

HOW I WORK

Build. Automate. Troubleshoot.

I care about understanding the request path, securing each hop and proving that a deployment works.

Cloud infrastructure

VPCs, subnets, security groups, load balancers, IAM and ECS workloads on AWS.

Infrastructure as code

Modular Terraform, remote state and reviewed plans before infrastructure changes.

CI/CD

GitHub Actions pipelines using OIDC, immutable image tags and post-deployment checks.

Containers

Multi-stage Docker builds, Amazon ECR and container workloads running on Fargate.

Observability

CloudWatch logs, health endpoints, alerts and deliberate failure testing.

Troubleshooting

Tracing failures across DNS, HTTPS, load balancing, networking and applications.

AWSTerraformDockerGitHub ActionsLinuxBashGitNetworking

ABOUT ME

Operations experience. DevOps focus.

Security operations taught me to stay calm under pressure, investigate properly and communicate clearly. I now bring that same mindset to cloud infrastructure.

I learn by building real systems, testing what happens when they fail and understanding each decision well enough to explain it.

2026 — PRESENT

DevOps Engineering · CoderCo

Building production-style AWS projects across cloud, containers, infrastructure as code and CI/CD.

2023 — PRESENT

Security Operations · LSS

Incident handling, access control and site operations in a security-focused environment.

LET'S CONNECT

Let’s talk DevOps and Cloud.

Based in London and ready to build, automate and troubleshoot.

Email Sammy ↗Connect on LinkedIn