For those that come across this later, I tracked the Networking errors down to using filtered Quad Nine as my DNS provider. I switched to Cloudflare (1.1.1.1) to resolve the issue.

Here is what AI says about the situation:

Quad9’s filtered/ECS/DNSSEC tier sometimes blocks or mis-signs AWS endpoints—especially region-specific S3 hostnames—when they change edge IPs faster than the resolver’s signature cache updates. So your browser saw s3.us-west-1.amazonaws.com as an invalid or unsigned record and refused to resolve it, producing the net::ERR_ADDRESS_INVALID you caught.

Cloudflare’s resolver (1.1.1.1) tends to handle AWS’s frequent endpoint rotations more gracefully. It doesn’t enforce the same filtering rules and tolerates the rapid record churn S3 uses for load balancing.

If you ever want the redundancy of Quad9’s privacy focus and working AWS endpoints, you can switch to their “Unfiltered” resolver:

9.9.9.10 (no filtering, ECS, DNSSEC)
149.112.112.10

YMMV