-
Notifications
You must be signed in to change notification settings - Fork 242
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
aws-cli #78
Comments
Hello @guumaster As a first set of information to help us investigate, can you provide:
On our side, we'll try to reproduce it and tell you the status of the issue (bug, etc) |
Hi again, @guumaster After a bit of investigation (and some code grepping in the pip awscli package...), I found out that the only way with aws-cli to provide a different endpoint than the standard one is to use the aws --endpoint-url http://127.0.0.1:8000/ s3api create-bucket --bucket TestBucket Given this fact, I'm guessing that the ini config you showed as Could you try the endpoint-url option and tell me if it works for you ? |
I'm on linux and have DragonDisk or aws-cli. Both can't connect to it. I tried that command, and it worked with minor tweaks: $> aws --endpoint-url http://127.0.0.1:8000/ s3api create-bucket --bucket guumaster --profile=local #TestBucket seems to be a wrong name for aws-cli
$> aws --endpoint-url http://127.0.0.1:8000/ s3 cp README.md s3://guumaster/ --profile=local
$> aws --endpoint-url http://127.0.0.1:8000/ s3 ls s3://gustavo/ --profile=local
2016-06-23 15:25:28 1983 README.md The Thanks |
I am unsure whether you can actually set this option in the aws config file. Mhh the TestBucket worked for me, though, but I'll concede that it's not exactly dns compliant, so no surprise there, we might be using different versions of awscli. I will close this issue as "invalid" (not a bug), feel free to add more information after your investigations on the config improvements. |
Well, I couldn't find a way to save the endpoint-url on any config file, only by command line. But it works fine with that. Thanks. |
Hey @guumaster , |
Is there a way to connect
aws-cli
with this server?I've tried with a docker image and
npm start
, but every time I getInvalidAccessKeyId
error.This is my
~/.aws/config
:And
~/.aws/credentials
:The text was updated successfully, but these errors were encountered: