Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm working on getting git setup for my application on Elastic Beanstalk. I've been following the instructions provided by amazon. After pushing the changes I get this error

git aws.push

error: The requested URL returned error: 403 while accessing https://<Access Key Removed>:20130117T213945Z538f1c7baf8c89b4b547cb6717aabbaa7dfab3c52e0911d71e17b06765b922b2@git.elasticbeanstalk.us-east-1.amazonaws.com/v1/repos/54696d73546573744170706c69636174696f6e/commitid/62323130316462646264373436303536343265633861333035633133633265666466393633303133/environment/54696d7374657374656e7669726f6e6d656e74/info/refs?service=git-receive-pack
fatal: HTTP request failed

Here's my .config file

git config -l

credential.helper=osxkeychain
user.name=Tim xxxxxxxxxx
user.email=xxxxxxxxx@gmail.com
core.bare=false
core.repositoryformatversion=0
core.filemode=true
core.logallrefupdates=true
core.ignorecase=true
aws.endpoint.us-east-1=git.elasticbeanstalk.us-east-1.amazonaws.com
aws.endpoint.ap-northeast-1=git.elasticbeanstalk.ap-northeast-1.amazonaws.com
aws.endpoint.eu-west-1=git.elasticbeanstalk.eu-west-1.amazonaws.com
aws.endpoint.us-west-1=git.elasticbeanstalk.us-west-1.amazonaws.com
aws.endpoint.us-west-2=git.elasticbeanstalk.us-west-2.amazonaws.com
aws.endpoint.ap-southeast-1=git.elasticbeanstalk.ap-southeast-1.amazonaws.com
aws.endpoint.ap-southeast-2=git.elasticbeanstalk.ap-southeast-2.amazonaws.com
aws.endpoint.sa-east-1=git.elasticbeanstalk.sa-east-1.amazonaws.com
alias.aws.elasticbeanstalk.remote=!.git/AWSDevTools/aws.elasticbeanstalk.push --remote-url
alias.aws.elasticbeanstalk.push=!.git/AWSDevTools/aws.elasticbeanstalk.push
alias.aws.elasticbeanstalk.config=!.git/AWSDevTools/aws.elasticbeanstalk.config
alias.aws.push=!git aws.elasticbeanstalk.push
alias.aws.config=!git aws.elasticbeanstalk.config

Thanks for your help. Please let me know if I can provide you with additional info. I don't really know what else to check or do. Thanks again.

share|improve this question
    
HTTP 403? I would check that the account that you're using has proper permissions. Are you using a set of keys from an IAM account? If so, double check that you have the correct permissions (or policy) associated with the account. –  jamieb Jan 18 '13 at 14:59
    
Where would I check the permissions? I'm not using IAM keys, in the documentation there's a link to the "Access Credentials". I followed that link and got the Key and Secret Key from there. docs.aws.amazon.com/elasticbeanstalk/latest/dg/… –  TimSum Jan 18 '13 at 16:34
    
Yes, the main account keys will give you full access (or should, anyhow). I'm not really sure how to help. Have you tried posting in the AWS support forums? This might need the attention of AWS staff to resolve. –  jamieb Jan 18 '13 at 17:50
    
Yeah... I posted there. Haven't heard anything yet... –  TimSum Jan 18 '13 at 18:38

1 Answer 1

up vote 0 down vote accepted

The problem was that I didn't have the HTTPS (443) port open in my Security Group. Working like a dream now that that's adjusted.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.