Posts in Category: Networking & Firewalls

From a Single EC2 Instance to a 14-Node Multi-Cloud K3s Cluster: Networking, Firewalls, Self-Healing, and DevOps

Back when I first started this blog, everything ran on one tuned EC2 t1.micro instance sharing memory between Apache, PHP, and MySQL. Over the years that single VM grew into a 14-node multi-cloud Kubernetes (K3s) cluster running across Oracle Cloud Infrastructure and Google Cloud Platform Always Free tiers. Instead of relying on expensive managed services, every layer of networking, firewall filtering, ingress TLS, media storage, observability, and disaster recovery is built declaratively and maintained by closed-loop self-healing automation.

Isometric illustration of a resilient multi-cloud Kubernetes cluster connected over encrypted WireGuard tunnels and firewall perimeters
Multi-cloud K3s topology connected through an encrypted WireGuard mesh and zero-trust firewall policies.
Continue reading

Proxy using an SSH tunnel

Browse the web through your SSH server by turning it into a proxy server.
Proxy using an SSH tunnel
Continue reading

Simplify your life with an SSH config file and ClusterSSH

Simplify your life with an SSH config file and ClusterSSH

If you’re anything like me, you probably log in and out of a half dozen remote servers on a daily basis. And if you’re even more like me, you have trouble remembering all of the various usernames, remote addresses and command line options for things like specifying a non-standard connection port or forwarding local ports to the remote machine. And if you sometimes have to do the same thing across many servers, this post is for you.

Continue reading

Apache: restrict access based on IP address to selected directories

apacheThe Apache web server lets you control access based on various conditions. For example, suppose you want to restrict access to http://subdomain.domain.com/ (mapped to the /var/www/subdomain directory) from the 192.168.1.0/24 network (within an intranet).

Apache provides access control based on client hostname, IP address, or other characteristics of the client request using mod_authz_core in Apache 2.4 (or mod_authz_host / mod_access in legacy Apache 2.2).

Continue reading