Closed robksawyer closed 9 years ago
I think I've solved the problem. I checked my ~/.bash_profile and commented out the following. I then reinstalled python via brew, ran brew doctor, restarted the iTerm and now I get:
bash_profile nonsense:
# Setting PATH for Python 2.7
# The orginal version is saved in .bash_profile.pysave
#PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}"
#export PATH
# Setting PATH for MacPython 2.6
# The orginal version is saved in .bash_profile.pysave
#PATH="/Library/Frameworks/Python.framework/Versions/2.6/bin:${PATH}"
#export PATH
Now I get:
Robs-MacBook-Pro:~ me$ brenda-run init
Pushing ssh public key '/Users/me/.ssh/id_rsa.pub' to AWS under 'brenda' key pair.
KeyPair:brenda
Creating AWS security group 'brenda'.
Seems like a good start.
I'm on a retina Macbook pro running Yosemite and having an issue regarding Amazon certificates and getting Brenda setup.
I've run the
s3cmd --configure
and it has completed successfully, but I'm still unable to usebrenda-work
. See the output below for more details. It appears to be a certificate issue. I will say that I'm pretty new to EC2, so I could have the configuration wrong or something. Maybe I'm using the wrong values for the ACCESS and SECRET keys? I pulled these values from the Access Keys (Access Key ID and Secret Access Key) section of Your Security Credentials inside of the Amazon Web Services Console. Any ideas?Now when running
brenda-run init
, I get the following:Out of curiousity I tried
brenda-work status
and the following is happening.