Published 30 May 2026
When a 1GB Instance Wasn't Enough
A production outage revealed how little headroom remained on a 1 GB Lightsail instance, leading to a deeper look at capacity planning, memory pressure and the decision to upgrade.
Read note →Technical observations from building, operating and troubleshooting real cloud systems.
Published 30 May 2026
A production outage revealed how little headroom remained on a 1 GB Lightsail instance, leading to a deeper look at capacity planning, memory pressure and the decision to upgrade.
Read note →Published 29 May 2026
How monitoring and alerting detected a real production outage and helped trace the root cause to memory exhaustion, migration PHP settings and a stale plugin reference.
Read note →Published 26 May 2026
How intermittent WordPress outages after a Lightsail migration led to swap configuration, Route 53 health checks, CloudWatch alarms and SNS email notifications for automated failure detection.
Read note →Published 25 May 2026
How a failed WordPress restore test exposed weaknesses in my backup strategy and led to a simpler, recovery-first approach using AWS Lightsail snapshots, Lambda automation and monitoring.
Read note →Published 23 May 2026
How Live Server and automatic code formatting improved the speed, structure and efficiency of building Cliffable locally.
Read note →Published 23 May 2026
Moving from manual S3 uploads to a GitHub Actions deployment pipeline using OIDC, IAM roles and CloudFront invalidation.
Read note →