s3 sync's --exact-timestamp does not affect uploads. It seems the only way to...

s3 sync's --exact-timestamp does not affect uploads. It seems the only way to always have the files from a pipeline uploaded on deploy is to first run s3 rm on the bucket, then sync. see: https://github.com/aws/aws-cli/issues/4460

Does this cause any issues when a user has a cached index.html? The cached index.html would point to app.versionA.js, then s3 rm deletes app.versionA.js. I believe we have our TTL set to 0, so users should always get the latest index.html. Our Service Worker caching strategy may affect this, though, too. It's probably easiest to test it out rather than try to reason about it.