In the tutorial "Object Storage - Enabling HTTPS on a static website using a custom domain"
https://help.ovhcloud.com/csm/en-ie-public-cloud-storage-s3-static-website-https?id=kb_article_view&sysparm_article=KB0058080#step-12-configure-a-server-cluster
We need to obtain an IPv4 for the bucket "website" domain.
However, when I look up the the IPv4, I see the static website default URL is a CNAME and not an IPv4. host xxx.s3-website.de.io.cloud.ovh.netxxx.s3-website.de.io.cloud.ovh.net is an alias for s3-website.de.io.cloud.ovh.net.s3-website.de.io.cloud.ovh.net has address 141.95.67.81
When I then use this 141.95.67.81 in the load balancer as "Server IP", the result is that I am redirected to https://www.ovhcloud.com/en/public-cloud/object-storage/ instead of the content of the bucket being served.
1. Is the tutorial missing important steps?
2. Do we need the "bare metal load balancer" as a front for an object-storage static-site, as mentioned in this tutorial, or do we need the new "Public Cloud" load balancer instead?
3. Can we obtain the IP address for a bucket itself at all? If not, is it possible at all to have a static site in object storage over SSL on a custom (root) domain?
Load Balancer in front of Object storage for custom domain and SSL
I already had question about it - Static site hosting options with SSL - OVHcloud Community EN
What are you missing is the
Hostheader. You have no single dedicated ip address for the bucket, that's why the tutorial shows adding a bare-metal load balancer (adding hefty 20e / month).Unfortunately I still believe OVH did not fully comprehend or support static hosting as a complete service. Other providers are having an option placing a CDN in front of the hosted bucket with small flat fee or pay-per-use. I managed to create a CDN service with other provider and it's working for may personal blog.
Thanks!
Indeed, debugging with curl confirms its the missing Host Header.
What CDN service did you end up using, if I may ask?
I used AWS CoudFront as PoC (it needs CachingDisabled and AllExceptHost policy to get it working). but any other CDN should do (CloudFlare, ...).
Regardless that I believe a complete solution from OVH could be welcome even with some pay-per-use or low flat fee. But at this time the OVH Bare Metal LB or the CDN are starting with quite high montly price, which could be justified only when serving very large content with high volume :/
There is a "roadmap" github somewhere, where OVH is picking up issues and making new features from them. It may be worth asking there.