If Amazon is running a general-purpose web server with persistent state for S3 static hosting, I'd argue they're doing something very wrong.
If Amazon is running a general-purpose web server with persistent state for S3 static hosting, I'd argue they're doing something very wrong. It's not hard to write a web server that reads from persistent storage but has no need or ability to write to persistent storage. (You can give it a cache, but the cache is destroyable.) So you can attack the web server in memory (maybe), but there's no way to persist the attack. As soon as the web server gets restarted, the attack goes away, and there's also no way to spread the attack from one web server to any of the countless others. Then it's a simple matter of load-balancing at scale and restarting these stateless web servers on a regular basis to make exploits infeasible, at least until you get to substantially more motivated and funded attackers. And Amazon is a fan of both load-balancing at scale and restarting things.
Posted by geofft on Jul 9, 2015, 5:31 AM
Tags
Related issues
- [Codex Desktop][Windows] Weekly quota jumped 67 points in 38 seconds (Oct 16, 2026; 18:10 UTC)
- I loathe how difficult Matrix is for normal people though.
- Fragile against upgrades, tons of unmaintained plugins, admin panel UX is a mess where you struggle to find the stuff your are looking fo...
- Unfortunately there doesn’t seem to be any decent alternative.
- I'm wondering how much of that is bad developer UX and defaults, and how much of that is inherent complexity in the problem space.
- Pulumi support
Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments
ux (Sysadmin)
[Codex Desktop][Windows] Weekly quota jumped 67 points in 38 seconds (Oct 16, 2026; 18:10 UTC)
I loathe how difficult Matrix is for normal people though.
Fragile against upgrades, tons of unmaintained plugins, admin panel UX is a mess where you struggle to find the stuff your are looking fo...
Unfortunately there doesn’t seem to be any decent alternative.
I'm wondering how much of that is bad developer UX and defaults, and how much of that is inherent complexity in the problem space.
Pulumi support
[Feature]: managing cnpg in GitOps workflows (FluxCD, ArgoCD ...)
Merge the platform and UI threads
If Amazon is running a general-purpose web server with persistent state for S3 static hosting, I'd argue they're doing something very wrong.
If Amazon is running a general-purpose web server with persistent state for S3 static hosting, I'd argue they're doing something very wrong. It's not hard to write a web server that reads from persistent storage but has no need or ability to write to persistent storage. (You can give it a cache, but the cache is destroyable.) So you can attack the web server in memory (maybe), but there's no way to persist the attack. As soon as the web server gets restarted, the attack goes away, and there's also no way to spread the attack from one web server to any of the countless others. Then it's a simple matter of load-balancing at scale and restarting these stateless web servers on a regular basis to make exploits infeasible, at least until you get to substantially more motivated and funded attackers. And Amazon is a fan of both load-balancing at scale and restarting things.
Comments (0)
No comments yet. Start the discussion.