AWS Cost Protection Strategy
How a billing audit led to a layered AWS cost protection strategy using budget alerts, monthly reviews, region restrictions and IAM guardrails to reduce the risk of unexpected charges.
Read note →Technical observations from building, operating and troubleshooting real cloud systems.
How a billing audit led to a layered AWS cost protection strategy using budget alerts, monthly reviews, region restrictions and IAM guardrails to reduce the risk of unexpected charges.
Read note →A security alert prompted a wider review of my WordPress infrastructure, leading to improvements across server configuration, domain management, DNS architecture and operational security.
Read note →How I consolidated Cliffable domains into a dedicated AWS account and built HTTPS redirects for secondary domains using Route 53, CloudFront, ACM and S3.
Read note →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 →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 →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 →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 →How Live Server and automatic code formatting improved the speed, structure and efficiency of building Cliffable locally.
Read note →Moving from manual S3 uploads to a GitHub Actions deployment pipeline using OIDC, IAM roles and CloudFront invalidation.
Read note →