Portfolio index

Technical build record / 05

June–August 2026

Secure GCP + Blockkeeper Operations Platform

A Terraform-managed Google Cloud server and local operations platform built around constrained administration, infrastructure hardening, backups, recovery, and operator control.

State
Built and tested
Spotlight

A concise record of what was built, tested, and retained.

Verified evidence

Résumé validation snapshot
34 / 34 application testsThe snapshot covers the operations console and Java bridge; it does not assess any later live configuration.

Technologies and themes

  • GCP
  • Terraform
  • IAM/IAP
  • Ubuntu
  • ARM64
  • Shielded VM
  • React
  • .NET
  • Java
  • systemd

Operational recovery case

Infrastructure hardening becomes credible when administration is constrained, operator control stays local, and recovery is designed into the platform instead of promised after failure.

Conceptual recovery cradleIllustrative · not live infrastructure, configuration, or telemetry

  1. 01 / Reproducible boundary

    Define the operating boundary before the server runs

    Terraform made the Google Cloud environment reproducible around a custom VPC, Shielded VM controls, private backups, and deletion protection. IAP-only administration and least-privilege IAM constrained operation instead of treating hardening as a later patch.

  2. 02 / Local control

    Keep operator control on the local side

    Blockkeeper paired the cloud server with a localhost-only React and .NET operations console connected through a Java bridge. Routine control stayed inside a deliberately narrow administrative surface rather than adding another public interface.

  3. 03 / Recovery evidence

    Treat maintenance and recovery as normal operation

    Automated patching, systemd recovery, checksum-verified backups, and player-based stability and recovery checks made rollback and restart part of the engineered system. The résumé records 34/34 application tests across the operations console and Java bridge.