This is precisely why netlify's offering is valuable. It works out of the box with zero config. If you're using a common static site generator you don't even need to setup the build process, just give it your git repo, and push when you want to deploy.
That's not really a compelling reason when it's literally a single input field on a form to setup. Also, if you're in the business of web development, HTTP cache control headers are something you should know about regardless.
As with a lot of AWS, it's easy if you know you need to do it, but there are a lot of gotchas which can be very expensive if hit (and there's no way to limit expenditure).
Comments
This is precisely why netlify's offering is valuable. It works out of the box with zero config. If you're using a common static site generator you don't even need to setup the build process, just give it your git repo, and push when you want to deploy.
That's not really a compelling reason when it's literally a single input field on a form to setup. Also, if you're in the business of web development, HTTP cache control headers are something you should know about regardless.
As with a lot of AWS, it's easy if you know you need to do it, but there are a lot of gotchas which can be very expensive if hit (and there's no way to limit expenditure).