This document lists some problems I encountered using s3cmd
on rsync.net and how I solved them.
s3cmd sync
doesn't support the --storage-class
argument, and even that doesn't support the ONEZONE_IA
storage class. You can still upload objects to that class by specifying the x-amz-storage-class
header,
but s3cmd sync
will ignore that. The best solution I have is to upload your files as you normally would,
then use s3cmd modify
to set the storage class after upload.
See here for prior art.
Running a command with s3cmd
on rsync.net might elicit this error:
ERROR: SSL certificate verification failure: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
rsync.net support has advised me that this can be solved by passing the --no-check-certificate
argument:
$ s3cmd sync --no-check-certificate ...
They did not reply to my request as to solutions to running s3cmd
without skipping certificate verification.
You may have already seen this article. The advice in the post works great for me, with two adjustments:
- Access can be restricted to only the target bucket (as opposed to all of your buckets)
- The
ListAllMyBuckets
permission is not necessary.
Here's a revised IAM policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:ListBucket",
"s3:PutObjectAcl"
],
"Resource": [
"arn:aws:s3:::YourBucketName",
"arn:aws:s3:::YourBucketName/*"
]
}
]
}
@abendy Unfortunately not. It might be worth raising the issue with support again.