Does object storage support multiple domain names accessing the same bucket?
AWS Object Storage can support multiple domain names accessing the same bucket. I would like to know whether Linode Object Storage supports it or how multiple domain names can access the same bucket? Thanks
1 Reply
It does if you only need http (not https) and you create multiple CNAME DNS entries pointing to the bucket.
I've just tested with a valid SSL certificate and it fails due to the default linode SSL cert being returned instead of the cert applied to the bucket (which in this case is a wildcard one for *.mydomain.com)
* Trying 172.172.172.172:443...
* TCP_NODELAY set
* Connected to testing123.mydomain.com (172.172.172.172) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=eu-central-1.linodeobjects.com
* start date: Mar 18 12:35:48 2024 GMT
* expire date: Jun 16 12:35:47 2024 GMT
* subjectAltName does not match testing123.mydomain.com
* SSL: no alternative certificate subject name matches target host name 'testing123.mydomain.com'
* Closing connection 0
* TLSv1.3 (OUT), TLS alert, close notify (256):
curl: (60) SSL: no alternative certificate subject name matches target host name 'testing123.mydomain.com'