For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.us.ovhcloud.com/en/storage-and-backup/object-storage/website-https.md.
  • English

Object Storage - Enabling HTTPS on a static website using a custom domain

View as Markdown

Learn how to configure your website and the OVHcloud Load Balancer to enable HTTPS.

OVHcloud Object Storage can host a static website inside an Object Storage bucket.

Info

A static website contains only static content (HTML pages, images, videos, client-side scripts), whereas a dynamic website relies on server-side processing to process data and help render content.

However, OVHcloud Object Storage static website hosting does not support HTTPS. If you want to use HTTPS, you can use OVHcloud Load Balancer to serve a static website hosted on OVHcloud Object Storage and act as an SSL gateway.

 

Requirements

OVHcloud Control Panel Access

  • Direct link: Load Balancer
  • Navigation path: Network > Load Balancer > Select your service

 

Instructions

Step 1 - Configuring the Load Balancer

Step 1.1 - Add your certificate

Select your Load Balancer from the list, choose the SSL certificates tab, then click Add an SSL certificate.

Info

Optionally, you can also order a free certificate.

Manager load balancer ssl certificates tab

On the next screen, fill in the fields and click Add.

Manager load balancer add SSL certificate

Step 1.2 - Configure a server cluster

You now need to configure a server cluster and add it to your Load Balancer. A server cluster is a pool of backend machines that will handle the workload.

Still from the Load Balancer section of the OVHcloud Control Panel, click the Server clusters tab, then click Add a server cluster.

Server cluster tab empty

Enter the configuration of the new server cluster...

  • Name (optional)
  • Protocol: HTTP
  • Port: 80
  • Datacenter: Choose the region in which you have hosted your website

...and click Add.

Manager load balancer add server cluster

You now need to add servers to your server cluster. Click the Add a server button.

Manager load balancer server cluster details

Enter the configuration information of your server:

  • Name (optional)
  • IPv4 address: Enter the public IP associated with your static website default URL in the form of <bucket_name>.s3-website.<region>.io.cloud.ovh.us

You can retrieve this IP address by doing a dig command on the URL.

Example: using dig command

dig <bucket_name>.s3-website.<region>.io.cloud.ovh.us
; <<>> DiG 9.16.1-Ubuntu <<>> my-site.s3-website.us-east-va.io.cloud.ovh.us
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22041
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;my-site.s3-website.us-east-va.io.cloud.ovh.us. IN A

;; ANSWER SECTION:
my-site.s3-website.us-east-va.io.cloud.ovh.us. 3600 IN A 141.95.161.77

;; Query time: 12 msec
;; SERVER: 10.15.25.129#53(10.15.25.129)
;; WHEN: Mon Jun 05 16:09:56 CEST 2023
;; MSG SIZE  rcvd: 84

Example: using host command

host <bucket_name>.s3-website.<region>.io.cloud.ovh.us
my-site.s3-website.us-east-va.io.cloud.ovh.us has address 141.95.161.77

Manager load balancer add server

Step 1.3 - Configure your front-ends

The next step is to add front-ends to your Load Balancer. A front-end will be the internet-facing element of your Load Balancer and is responsible for handling and routing incoming requests.

In the Load Balancer section of the OVHcloud Control Panel, click the Front-ends tab, then click Add a front-end.

Frontends empty - Website https

Add two frontends:

  • One frontend whose sole purpose is to handle all incoming HTTP requests and redirect them to your domain name in HTTPS

    • name (optional)
    • protocol: HTTP
    • port: 80
    • datacenter: all
    • default server cluster: none
    • advanced settings > HTTP Redirection: https://<domain_name>

  • One frontend that will handle all incoming HTTPS requests and perform the role of the SSL gateway

    • name (optional)
    • protocol: HTTPS
    • port: 443
    • datacenter: the region where your bucket sits
    • default server cluster: the server cluster previously created
    • certificate: the certificate that you created
    • advanced settings > HTTP Header: Host <website_endpoint> in the form <bucket_name>.s3-website.<region>.io.cloud.ovh.us

Manager load balancer add front end

Step 1.4 - Apply changes

Once you have created and configured all the resources, do not forget to click the Apply configuration button to apply all the changes to the Load Balancer.

Manager load balancer apply configuration

 

Step 2: Configure your DNS

Edit the two A records to add the public IP address of your Load Balancer.

Warning

NOTE: Check with the provider of your external domain for instructions to do this.

Info

You can find the public IP address of your Load Balancer on the home page of the Load Balancer section in the OVHcloud Control Panel.

Home tab - Website https

 

Step 3: Test your website

Check that the website and the redirect work properly. Open a private browser to ensure that you have a clean cache and type your domain name.

Example:

Storage backup object S3 https images test

 

Go further

How to configure your OVHcloud Load Balancer

Browse all the Object Storage (S3™-compatible) guides.

Browse the rest of the OVHcloud US documentation for guides on our other products and services.

Learn more about Object Storage on the OVHcloud US website.

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.

*S3 is a trademark filed by Amazon Technologies, Inc. OVHcloud's service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.