Yes thanks for the tip! s3cmd was still working and an older version of
cyberduck is also working.
-----Original Message-----
Sent: Thursday, October 15, 2020 2:57 PM
To: ceph-users(a)ceph.io
Subject: [ceph-users] Re: radosgw bucket subdomain with tls
To my knowledge that's a S3 client setting only. Mostly referred to as
'path-style'. Kickin' in open doors here, but you could opt for a
wildcard certificate, that would be more future proof; Path-style will
not be supported anymore, at least not at Amazon[1], so client support
will fade away in time.
- Hans
[1]
https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-o…
On 10/15/20 2:18 PM, Marc Roos wrote:
I enabled a certificate on my radosgw, but I think I am running into
the
problem that the s3 clients are accessing the buckets
like
bucket.rgw.domain.com. Which fails my cert
rgw.domain.com.
Is there any way to configure that only
rgw.domain.com is being used?
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io