creating bucket via aws cli doesn't work.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 273
- Forks
- 391
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I wanted to try out stash followed the instructions here: https://docs.ovh.com/ca/en/kubernetes/backing-up-volumes-using-stash/
Getting the credentials via openstack ec2 credentials create worked fine - but the credentials won't work. aws cli: SignatureDoesNotMatch
Interestingly if I rename the profile [profile default] to for example [profile ovh], the error changes to:
aws --profile ovh s3 mb s3://s3-stash
make_bucket failed: s3://s3-stash An error occurred (InternalError) when calling the CreateBucket operation (reached max retries: 4): unexpected status code 500
I do believe that there cannot be a profile default and the default config would be under [default] and not [profile default] but I am not sure about that :]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Stash backup guide linked in the report and compare its credential and AWS CLI configuration instructions with the shown openstack ec2 credentials create and aws s3 mb commands. Confirm the correct profile configuration and document or test the steps until bucket creation succeeds without SignatureDoesNotMatch or the reported 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100