How to work with S3 API using Swift3?
Hi there,
I am wondering if there is any more documentation on how to get swift3 to work with S3 API.
Specifically, if I created a swift account by
seki@OS-
https:/
And get the following
seki@OS-
...
< X-Storage-Url: https:/
< X-Storage-Token: AUTH_tka3599de5
< X-Auth-Token: AUTH_tka3599de5
...
Should I set the following variables
export EC2_ACCESS_
export EC2_SECRET_
export S3_URL=https:/
I've added to the following to /etc/swift/
[filter:swift3]
use = egg:swift#swift3
log_facility = LOG_LOCAL1
But I am still getting 401 error:
seki@OS-
Unknown option: get
WARNING: It isn't safe to put your AWS secret access key on the
command line! The recommended key management system is to store
your AWS secret access keys in a file owned by, and only readable
by you.
For example:
%awsSecretAcces
# personal account
personal => {
id => '1ME55KNV6SBTR7
key => 'zyMrlZUKeG9UcY
},
# corporate account
company => {
id => '1ATXQ3HHA59CYF
key => 'WQY4SrSS95pJUT
},
);
$ chmod 600 /home/seki/.s3curl
Will sleep and continue despite this problem.
Please set up /home/seki/.s3curl for future requests.
* About to connect() to 192.168.1.33 port 8080 (#0)
* Trying 192.168.1.33... connected
* Connected to 192.168.1.33 (192.168.1.33) port 8080 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
* subject: C=CA; ST=AB; L=Edmonton; O=VRS; OU=RD; CN=OS-CC; <email address hidden>
* start date: 2011-04-23 15:55:37 GMT
* expire date: 2011-05-23 15:55:37 GMT
* common name: OS-CC (does not match '192.168.1.33')
* issuer: C=CA; ST=AB; L=Edmonton; O=VRS; OU=RD; CN=OS-CC; <email address hidden>
* SSL certificate verify result: self signed certificate (18), continuing anyway.
> GET /v1/AUTH_
> User-Agent: curl/7.21.0 (x86_64-
> Host: 192.168.1.33:8080
> Accept: */*
> Date: Tue, 26 Apr 2011 16:42:05 +0000
> Authorization: AWS AUTH_tka3599de5
>
< HTTP/1.1 401 Unauthorized
< Content-Type: text/html; charset=UTF-8
< Content-Length: 364
< Date: Tue, 26 Apr 2011 16:42:05 GMT
<
<html>
<head>
<title>401 Unauthorized<
</head>
<body>
<h1>401 Unauthorized</h1>
This server could not verify that you are authorized to
access the document you requested. Either you supplied the
wrong credentials (e.g., bad password), or your browser
does not understand how to supply the credentials required.
<br /><br />
</body>
* Connection #0 to host 192.168.1.33 left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Shi Jin for more information if necessary.