| | | 🔗 Stories, Tutorials & Articles | | | | | | | I Left Port 22 Open on the Internet for 54 Days. Here's Who Showed Up. ✅ | | | | | | A 54-day SSH honeypot on port 22 logged 268,000+ login attempts from 7,556 IPs, with 99.6% of attackers running a single automated fingerprinting command and only 28 ever opening an interactive shell. The data shows hardcoded IoT credentials and Solana validator hunting dominating the password lists, a single Belgian residential IP firing 156,000 attempts on its own, and a small professional tier using /dev/tcp/ socket tricks with rotating C2 infrastructure to drop UPX-packed ELF binaries. |
| | | | | | | | | | | Incidents *Will* Happen. Are You (Actually) Prepared? | | | | | | Joe Mckevitt, CTO of Uptime Labs, argues that incident prevention and incident preparation are not substitutes, and that organizations relying on the heroic engineer who knows the infrastructure at 2am have a habit, not a strategy. The piece pushes for a deliberate playbook (practiced communication, pre-understood failure behavior, repeatable response) over runbooks decaying in Confluence, and notes that AI in the execution path will reshape failure modes rather than reduce the need for human-led preparation. |
| | | | | | | | | | Migrating from DigitalOcean to Hetzner: From $1,432 to $233/month With Zero Downtime ✅ | | | | | A walkthrough of migrating 248 GB of MySQL across 30 databases, 34 Nginx sites, GitLab EE, and Neo4j from a $1,432/month DigitalOcean droplet to a $233/month Hetzner AX162-R dedicated box with no downtime.
The path: mydumper/myloader with 32 threads for the bulk MySQL 5.7 to 8.0 import, master-to-replica sync from a recorded binlog position with slave_exec_mode = IDEMPOTENT to bypass 1062 errors, scripted DNS TTL reduction to 300s on A/AAAA records only, converting the old Nginx configs into reverse proxies during propagation, and a final flip of all A records via the DigitalOcean API. |
| | | | | | | | | | | Why Queues Don’t Fix Scaling Problems | | | | | | Queues do not create capacity, they delay the moment insufficient capacity becomes visible, and sustained overload turns a queue from a smoothing buffer into a cascading failure that takes down databases, connection pools, and consumer instances before it ever hits the queue's own limits. |
| | | | | | | | | | S3 Files and the changing face of S3 | | | | | AWS launched S3 Files, an EFS-backed feature that mounts any S3 bucket or prefix as an NFS filesystem on EC2, containers, or Lambda, with changes batched back to S3 roughly every 60 seconds.
Rather than collapsing file and object semantics into a single model (an early design attempt called "EFS3" that the team abandoned after deciding it produced only the lowest common denominator), Andy Warfield describes a "stage and commit" architecture borrowed from version control: EFS holds the live filesystem view, S3 stays the source of truth on conflict, and key names that can't be represented in both worlds emit events instead of failing. |
| | | | | | 👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
|
|
