This could work, but only if you could automate billing caps too. I imagine for a low-traffic blog this could easily fit within free-tier requirements, but you don't want to suddenly get a bill when a page gets HN'd or something. Ideally the service should just fail when it hits free-tier limits and you can use the local js to display "Comments unavailable due to high traffic" or whatever.
If any of this is not automatable it fails as an idea, because configuring AWS requires a colossal amount of effort from someone who hasn't already used it.
Spending limits are far more complicated than they might seem since these services are designed to be billed by usage and many accrue charges even in a steady state.
What exactly is supposed to happen when the billing limit is hit? Delete everything? That's the only way to actually stop billing completely and I'm not sure who would actually want that.
No service that I know of deletes everything even when there are billing issues. No public access is nearly equivalent from the end user's perspective, and usually there is a grace period before everything is deleted. All in all it is an interesting conflict of interest on the cloud provider's part.
If any of this is not automatable it fails as an idea, because configuring AWS requires a colossal amount of effort from someone who hasn't already used it.