deploying to bucket outside the default region us-east-1 fails with cryptic 301: null error

[jm3]

this is basically user error on my part, but forgetting to pass the AWS region in the config {} for non-us-east-1 buckets causes gulp-awspublish to die with a cryptic 301: null error. it would be nice if this error was more helpful, e.g.:

BUCKET NOT FOUND: please check your bucket name and AWS region

gulp-awspublish version:

% npm list | grep aws
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ │ ├── [email protected]

error:

% gulp deploy
[15:11:18] Starting 'deploy'...
[15:11:18] Finished 'deploy' after 4.1 μs
gulp-awspublish/node_modules/aws-sdk/lib/request.js:32
          throw err;
                ^
301: null
    at Request.extractError (gulp-awspublish/node_modules/aws-sdk/lib/services/s3.js:359:35)
    at Request.callListeners (gulp-awspublish/node_modules/aws-sdk/lib/sequential_executor.js:100:18)
    at Request.emit (gulp-awspublish/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (gulp-awspublish/node_modules/aws-sdk/lib/request.js:604:14)
    at Request.transition (gulp-awspublish/node_modules/aws-sdk/lib/request.js:21:12)
    at AcceptorStateMachine.runTo (gulp-awspublish/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at gulp-awspublish/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (gulp-awspublish/node_modules/aws-sdk/lib/request.js:22:9)
    at Request.<anonymous> (gulp-awspublish/node_modules/aws-sdk/lib/request.js:606:12)
  at Request.callListeners (gulp-awspublish/node_modules/aws-sdk/lib/sequential_executor.js:104:18)

[pgherveou]

sorry for the hassle
its quite hard for me to investigate these kind of connection issues
can you try to manually pushing a file
using aws (see https://github.com/pgherveou/gulp-awspublish/blob/master/lib/index.js#L402 for example)
and see if you get the same error too

[pgherveou]

Glad you found the error,
We should look into aws to see if we can get better error messages, or send them an issue, I don't think this plugin should be in charge of that.

[JamieDixon]

I ran into this same issue today also. It would help if there was mention of the region parameter in the README to let users know that they need to specify the region. I'm happy to send a pull request with that change if you're good with it.

[jm3]

@JamieDixon good idea

[pgherveou]

PR are more than Welcome :)

Sent from my iPhone

On 24 avr. 2015, at 19:17, John Manoogian III [email protected] wrote:

@JamieDixon good idea

—
Reply to this email directly or view it on GitHub.

[alexgorbatchev]

We just pushed 2.0 out which takes straight S3 config options, so you are able to do quite a few other things like use a proxy. Do you think we still need to be explicit about the region in that case?

[jm3]

when there are many possible AWS regions and the error for wrong region is
a cryptic 301, i think it makes sense to have a more instructive error so
the developer knows what's wrong.

On Tue, Apr 28, 2015 at 9:11 AM Alex Gorbatchev [email protected]
wrote:

We just pushed 2.0 out which takes straight S3 config options, so you are
able to do quite a few other things like use a proxy. Do you think we still
need to be explicit about the region in that case?

Reply to this email directly or view it on GitHub
#53 (comment)
.

[alexgorbatchev]

I just used an invalid bucket name for the test and got a pretty digestible error. Perhaps it was addressed on AWS side?

  gulp-awspublish
    1) "before all" hook

  0 passing (155ms)
  1 failing

  1) gulp-awspublish "before all" hook:
     NoSuchBucket: The specified bucket does not exist
      at _stream_readable.js:943:16

[jm3]

try different region?
On Wed, Apr 29, 2015 at 6:26 AM Alex Gorbatchev [email protected]
wrote:

I just used an invalid bucket name for the test and got a pretty
digestible error. Perhaps it was addressed on AWS side?

gulp-awspublish
1) "before all" hook

0 passing (155ms)
1 failing

1. gulp-awspublish "before all" hook:
   NoSuchBucket: The specified bucket does not exist
   at _stream_readable.js:943:16

Reply to this email directly or view it on GitHub
#53 (comment)
.

[hiattp]

@alexgorbatchev Using v2, got the same cryptic 301. Adding to the readme or changing the error would definitely still help.

[kretz]

And for those who get this error and don't know how to specify the region:

  var publisher = $.awspublish.create({
    region: 'eu-west-1',
    params: {
      Bucket: '...'
    }
  });

[blaues0cke]

The region key for frankfurt is: eu-central-1.

[pachirel]

I encountered same error when I tried to upload wrong region.

I have a budget in us-west-2 region, but I specified ap-northeast-1 region.
To fix it, remove existing budget and create new one in correct region or specify correct region.

code example:

AWS = require('aws-sdk')
credentials = new AWS.SharedIniFileCredentials({profile: 'your-profile-name'})
AWS.config.credentials = credentials
AWS.config.region = 'region-the-budget-exists'
publisher = awspublish.create({
  params: {
    'Bucket': 'your-budget-name'
  }
})

[wembernard]

Thank you @kretz :)

[thewillhuang]

man, wasted so much time on this. in my ~/.aws config, my region is set to us-west-2 but the gulp task woulden't work unless i specify it. /facepalm

[pgherveou]

Thanks for the issue and workaround.
Can you guys add any info that could help others in the Readme with a PR?