TIL on Shawn Sorichetti

AWS S3 Files: S3 Buckets as NFS Filesystems

me@ssoriche.com (Shawn Sorichetti) — Wed, 08 Apr 2026 00:00:00 +0000

I’ve hit this problem twice now. At MetaCPAN, we were looking at using S3 as a sync target for rsync from upstream CPAN — conceptually simple, except rsync wants a filesystem and S3 very much isn’t one. More recently, I wanted to mount an S3 bucket as an image cache for Buildah. Same wall. You end up writing glue code, or reaching for a FUSE driver that may or may not be production-ready, or just redesigning around the limitation.

Logging Into Multiple AWS SSO Sessions at Once

me@ssoriche.com (Shawn Sorichetti) — Sun, 05 Apr 2026 00:00:00 +0000

I use Granted for per-terminal AWS credential assumptions — it’s great for switching between the multiple work accounts I juggle throughout the day. But I have SSO configured across more than one organization, and every morning I was logging into each one manually, one at a time, like a chump.

Turns out aws sso login has a --sso-session flag that targets a named session block from ~/.aws/config. So logging into multiple orgs is just two commands:

GL.iNet's AdGuard Home Hides Upstream DNS Settings in a Non-Obvious Place

me@ssoriche.com (Shawn Sorichetti) — Tue, 03 Mar 2026 00:00:00 +0000

On a recent trip I kept getting connection failures that needed retrying — pages half-loading, API calls timing out, the usual DNS-smells-wrong experience. It was intermittent enough to be annoying but consistent enough that I knew something was actually broken.

I narrowed it down to DNS pretty quickly. My GL.iNet MT-3000 travel router was dropping queries or returning nothing for some domains.

The culprit turned out to be obvious in retrospect: before leaving I had shut down my Pi-hole servers at home. Those Pi-holes live on my Tailscale network, and my travel router connects back to that network. Somewhere, something was still trying to use them for DNS.

Claude Code's /copy Command

me@ssoriche.com (Shawn Sorichetti) — Thu, 19 Feb 2026 00:00:00 +0000

A coworker dropped /copy in our work Slack yesterday and I had to try it immediately. It’s a Claude Code slash command that copies Claude’s last response straight to your clipboard as markdown.

Before finding this, my workflow for grabbing a generated code snippet or shell command was embarrassingly manual — select text in the terminal, hope I got the boundaries right, paste it somewhere. Now I just type:

/copy

And the whole response lands in my clipboard, formatting intact — including code blocks. This is especially useful when Claude generates something multi-part, like a function plus its tests or a sequence of shell commands, where careful selection across scroll boundaries used to be the only option.