Looks like AWS ranges implementation could not responce 416 status code in case of range out of file size. And it is hard to fix, because client header line Range processed after some data send to the client socket.