git-s3 icon indicating copy to clipboard operation
git-s3 copied to clipboard

deploy returning NotImplementedException

Open phivk opened this issue 11 years ago • 4 comments

Im following the guidelines in EXAMPLE.md, but get stuck during the git-s3 deploy step:

$ git-s3 deploy
Uploading newTestFile
[Aws\S3\Exception\NotImplementedException]                           
A header you provided implies functionality that is not implemented  
deploy

I used the following in git-s3 config:

Enter your AWS access key ID: [my access key ID]
Enter your AWS secret access key: [my secret access key]
Enter your Region name (default: eu-west-1): eu-west-1
Enter your bucket title: [my-bucket-name]
Enter the path (relative or absolute) where your repo lives: testRepo
Do you want to clone your repo? (default: "n"): n
Configuration was successful.

My bucket has region Ireland aka eu-west-1 (I tried specifying "Ireland" as Region name without success)

Am I missing something?

phivk avatar Aug 12 '14 14:08 phivk

After getting "Access denied" errors in the AWS CLI, I figured out it was because I didn't have permissions set for my user. Fixed this by adding my IAM user to a group and setting the right permissions in the Management Console.

phivk avatar Aug 13 '14 11:08 phivk

I also got this error when I installed git-s3 into the same dir as my repo. When I did in the dir above it, it all worked.

njcameron avatar May 10 '15 18:05 njcameron

I'm also getting this error when I git-s3 deploy. I'm using security credentials from my AWS account (not an IAM user). I tried creating an IAM user, giving them AdministrativeAccess and using their credentials, but I got the same error. I set the access permissions in my bucket wide open. I also have git-s3 configured in the directory above my repo just like the example.

I am still getting the error

$ git-s3 deploy
Uploading index.html


  [Aws\S3\Exception\NotImplementedException]                           
  A header you provided implies functionality that is not implemented  


deploy

config.yml looks like this

key: [my access ID]
secret: [my secret key]
region: us-west-1
bucket: [bucket name]
path: repo

Can anyone help me straighten this out?

wyattsweet avatar Sep 28 '15 18:09 wyattsweet

I just got this to work after putting content into the index.html file.

I ran $echo "test" >> index.html

Then I pushed it again and the it deployed. Posting my solution in case somebody else runs into the same error.

wyattsweet avatar Sep 28 '15 18:09 wyattsweet