In our Hey!Watch account, we configured the path to our S2 bucket. Account settings > Developer an the s3 string in the correct format as specified s3://access_key:secret_key@bucket Still, the file isn’t sent to S3 after encoding. Nothing appears in the bucket. Where should we look to solve this?

Does the bucket exist?

the bucket has been used for storing audio files, so it exists and contains data

What is your username, so I can check it out?

nascom

I think I found the problem.

There is a PermanentRedirect error. We must upload to “bucket.s3.amazonaws.com” instead of “s3.amazonaws.com/bucket”.

Here is the error:

<Error>
  <Code>PermanentRedirect</Code>
  <Message>The bucket you are attempting to access must be addressed using the specified endpoint. 
   Please send all future requests to this endpoint.</Message>
  <RequestId>..</RequestId>
  <Endpoint>yourbucket.s3.amazonaws.com</Endpoint>
  <HostId>..</HostId>
  <Bucket>yourbucket</Bucket>
</Error>

You should disable the permanent redirect option and it will work perfectly.

This should do the trick. Thx!

Where can I disable this option? I cannot find it on our Amazon s3 account.

I don’t know, but you should have the answer in the amazon S3 doc: http://docs.amazonwebservices.com/AmazonS3/2006-03-01/index.html?BucketConfiguration.html

Hi, Bruno,

Bucket Access
To access Amazon S3 buckets and objects that were created using CreateBucketConfiguration, you must use the virtual hosted-style request. For example:
<a href="http://yourbucket.s3.amazonaws.com/yourobject">http://yourbucket.s3.amazonaws.com/yourobject</a>
You cannot use the path-style request:
<a href="http://s3.amazonaws.com/yourbucket/yourobject">http://s3.amazonaws.com/yourbucket/yourobject</a>
If you use the path-style request, you receive a permanent redirect.

There is no option to prevent a permanent redirect. If you have created your bucket with a CreateBucketConfiguration option, say for example to locate your bucket in Europe, it should be accessed with http://yourbucket.s3.amazonaws.com/yourobject url.

So could Heywatch service handle this ?

No, we only upload to “s3.amazonaws.com/bucket” at this time.

Hope you plan to support this uri scheme in the future.