While you are fixing things, can you please make cloudfront send HTTP 1.1 instead of HTTP 1.0 for 206 (Partial Content) responses to range get requests. It is invalid since 206 is not part of HTTP 1.0, and Chrome refuses to cache the responses, which makes cloudfront terrible for delivering HTML5 media.
> CORS support is basically broken. S3 doesn't return the proper headers for browsers to understand how objects should be cached:
The S3 team is working to address this. We're investigating the other issues and always appreciate your feedback.