soypunk@lmorchard can I ask what you have your S3/CloudFront cache control settings at? Trying to determine what makes the most sense for a low traffic blog...
Les Orchard@Soypunk Hmm, I don't think I've really tweaked them from the defaults yet
@lmorchard it defaults to 24 hours which seems absurd.
@Soypunk Yeah, though I usually create an invalidation every time I push updates out, so that forcibly flushes the cache
@lmorchard yeah, I've been thinking about that ... I think... if I've parsed the docs correctly... you get a 1000 free invalidations but those could easily be a 1000 /* directives? Oi.
@Soypunk fwiw, this is what my "push to s3" script looks like https://gist.github.com/lmorchard/f96216da0547f49b6f052998542dda10
@lmorchard sweet, thanks. Looks the same as to what I was noodling with on the cli tool invalidation.
@Soypunk There's also the possibility to issue a more granular invalidation based on what actually changed, but I'm just kind of brute forcing it for now
@lmorchard poking around the cli tool I just figured out how to set the cache-control headers for certain s3 files so I'll probably just set the homepage and feed to no-cache and let the rest of it expire every hour. ¯\_(ツ)_/¯
@Soypunk i think there's also a cloudfront drop down option that ignores origin cache-control by default, but you can flip that around to honor headers
@lmorchard i left the respect origin on but I updated my CodeBuild script to copy everything to s3 with a 3600 max-age and then it runs a command that sets the no-cache header incantation on index.*. This seems more or less reasonable for now. I think.