Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

403 Forbidden #11

Open
hornetmadness opened this issue Jan 4, 2013 · 1 comment
Open

403 Forbidden #11

hornetmadness opened this issue Jan 4, 2013 · 1 comment

Comments

@hornetmadness
Copy link

running the below gives the error, but putting the key and secret in the cli works fine.
boto-rsync --access-key /etc/awsapi-key --secret-key /etc/awsapi-key --glob /var/log/nginx/access.log s3://nginx-access-logs/

I used the example in the boto config link
[Credentials]
aws_access_key_id =
aws_secret_access_key =

Any thoughts? I'm at a loss as to the why.

@ghost
Copy link

ghost commented Jan 4, 2013

I'm not sure. You may be reading the config doc wrong. Put both the access key and secret key in the config file, and put that either in /etc/boto.cfg or ~/.boto. You shouldn't need to specify a path to the config file then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant