This thread provides some evidence to suggest that 404 responses from S3 are handled poorly by Files at the storage engine layer. The desired behavior is to raise an explicit error message at the point of the 404 response.
I haven't reproduced this yet, but suspect it will reproduce.