Figured out my own problem - it was a routing issue in the VPC. Sorry for the noise.
On Sat, Jan 18, 2014 at 7:37 PM, Ognen Duzlevski < [email protected]> wrote: > On Sat, Jan 18, 2014 at 2:09 PM, Ognen Duzlevski <[email protected] > > wrote: > >> Also, could this have to do with the fact that there is a "/" in the path >> to the S3 resource? >> > > Nope, the / has nothing to do with it, verified with a different file in > the same bucket. > Ognen >
