A reusable validation script developed for Platform Foundation that consolidates critical post-deployment health checks into a single command.

Linux Root Filesystem Cleanup & Disk Usage Investigation

Purpose

This runbook provides a structured process for identifying and reclaiming disk space on Linux systems when the root filesystem becomes full.

Typical symptoms include:

• No space left on device
• Docker image pulls fail
• Package upgrades fail
• Log files stop writing
• Applications crash due to inability to write temporary files

1. Verify Disk Usage

Check filesystem utilization.

df -h

Example:

Filesystem       Size  Used Avail Use%
/dev/root        8.7G  8.6G   84M 100%

If the root filesystem (/) is above 90%, continue with this runbook.

Understand OIDC, OAuth 2.0, and GitHub Actions workload identity federation with AWS. This article explains how GitHub workflows authenticate to AWS without long-lived access keys and how IAM trust policies and scoped roles control what those workflows can do.

UI-imported dashboards live only in Grafana's SQLite database and disappear if it resets. File-based provisioning fixes this permanently.

You don't need to memorize every format — you need to recognize what KIND of file you're looking at and know the 2-3 rules that actually matter for each one. This is that map.

Homepage worked, every sub-path returned 403. Root cause: default_root_object only covers the bucket root — fixed with a CloudFront Function that rewrites directory paths to index.html.

sed patterns used throughout platform builds — with real examples from prometheus.yml, HAProxy, and GitHub Actions.

AWS Backup / EFS Restore Runbook

Overview

Reusable procedure for restoring an Amazon EFS filesystem from AWS Backup into a new, isolated filesystem for investigation, recovery, file extraction, or validation without modifying the source filesystem.

This procedure also documents common AWS Backup and EFS restore gotchas.

Prerequisites

• AWS CLI installed if CLI access is required
• IAM permissions confirmed for AWS Backup, EFS, and the required S3/AWS resources
• Correct AWS Region identified
• Recovery point identified
• Scratch EC2 instance available for mounting the restored filesystem
• Destination volume has adequate free space for any files being copied locally
• Confirm the restore will not modify the original filesystem

Known Gotchas

1. AWS Backup item path validation can be misleading

For item-level restores, the AWS Backup UI may display a message indicating that the item path must be relative.

Container Resource Patching Runbook

Overview

Procedure for temporarily replacing a resource file inside a running container without rebuilding or redeploying the container image.

This method is intended for controlled, temporary remediation when a permanent image-based fix is not immediately available.

A resource-level patch should be treated as a temporary operational change, not a replacement for updating the underlying image.

Prerequisites

• Correct target host identified
• Correct target container identified
• Current container/image version verified
• Patched file validated before deployment
• Original file backed up before replacement
• Patched file staged in a known location
• Rollback procedure understood
• Change documented for later removal or incorporation into the image

Procedure

1. Connect to the Host

ssh <instance-host>

Obtain the required privileges: