ceph radosgw (set)lifecycle - AWS v4 is broken
Posted on Wed 26 April 2017 in Ceph • 1 min read
First - s3cmd config
Setting signature_v2 = true is not enough! You have to set --signature-v2 as a parameter.
Second - 'Prefix' tag
You have specify a Prefix tag - and yes with a captial P!
without prefix tag
<LifecycleConfiguration>
<Rule>
<ID>ExampleRule</ID>
<Status>Enabled</Status>
<Expiration>
<Days>1</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>
[root@kraken ~]# s3cmd setlifecycle lc.xml s3://bucket1 --signature-v2
ERROR: S3 error: 403 (AccessDenied)
with closing prefix tag
<LifecycleConfiguration>
<Rule>
<ID>ExampleRule</ID>
</Prefix>
<Status>Enabled</Status>
<Expiration>
<Days>1</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>
[root@kraken ~]# s3cmd setlifecycle lc.xml s3://bucket1 --signature-v2
ERROR: S3 error: 403 (AccessDenied)
with prefix tag - working!
<LifecycleConfiguration>
<Rule>
<ID>ExampleRule</ID>
<Prefix></Prefix>
<Status>Enabled</Status>
<Expiration>
<Days>1</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>
[root@kraken ~]# s3cmd setlifecycle lc.xml s3://bucket1 --signature-v2
s3://bucket1/: Lifecycle Policy updated
version
ceph version 11.2.0 (f223e27eeb35991352ebc1f67423d4ebc252adb7)
s3cmd version 1.6.1