first proof guide.en-gb.md

Jessica41 · web-flow · commit 1e9c49a8d2ee · 2025-11-07T14:47:38.000-05:00
diff --git a/pages/network/load_balancer/create_http_https/guide.en-gb.md b/pages/network/load_balancer/create_http_https/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "Configuration of an OVHcloud Load Balancer service with HTTP/HTTPS"
 excerpt: "Configure your OVHcloud Load Balancer to distribute HTTP traffic and secure your connections with HTTPS"
-updated: 2025-11-06
+updated: 2025-11-07
 ---
 
 <style>
@@ -27,24 +27,24 @@ This guide aims to help you create your first HTTP/HTTPS service using the OVHcl
 
 A frontend will be created to listen on port 80, while another will listen on port 443 with an SSL/TLS certificate. These frontends will be configured to direct their traffic to a common HTTP farm. This farm can have one or more servers, depending on the chosen / adapted configuration.
 
-As a reminder, the OVHcloud Load Balancer service is composed of 4 elementary parts :
+As a reminder, the OVHcloud Load Balancer service is composed of 4 elementary parts:
 
-- the `frontends` ;
-- the `farms` of servers and their `servers` ;
-- the advanced `routes` between Frontends and Server Farms ;
+- the `frontends`;
+- the `farms` of servers and their `servers`;
+- the advanced `routes` between Frontends and Server Farms;
 - the `SSL/TLS` certificates allowing TCP and/or HTTP connections to be encrypted.
 
 ## Requirements
 
-- Have an [OVHcloud Load balancer](/links/network/load-balancer) offer in your OVHcloud account.
-- Be logged in to your [OVHcloud Control Panel](/links/manager).
+- Have an [OVHcloud Load balancer](/links/network/load-balancer) offer in your OVHcloud account
+- You must  be logged in to your [OVHcloud Control Panel](/links/manager)
 - Have a configured farm
 - Have a configured frontend
 - Have an SSL certificate
 
 ## Instructions
 
-**Table of contents**
+## Table of contents
 
 - [Add a server farm](#farm)
 - [Add a server](#server)
@@ -65,13 +65,13 @@ Before you start, it is recommended to consult the [OVHcloud Load Balancer prese
 > The order of element creation is important. In particular, server farms must be configured before being able to attach an SSL/TLS certificate or servers to them. Similarly, frontends must be configured after the server farms in order to be able to configure the frontend's default farm.
 > 
 
-The features detailed below are accessible from the OVHcloud Control Panel :
+The features detailed below are accessible from the OVHcloud Control Panel:
 
 ![OVHcloud Load Balancer Service](images/iplb_service.png){.thumbnail}
 
-For more information on the features of the OVHcloud Control Panel, consult the page « [Managing the Load Balancer service via the Control Panel](/pages/network/load_balancer/use-lb) ».
+For more information about the features of the OVHcloud Control Panel, see the [Managing the Load Balancer service via the OVHcloud Control Panel](/pages/network/load_balancer/use-lb) page.
 
-Via the OVHcloud API, use the following call :
+Via the OVHcloud API, use the following call:
 
 > [!api]
 >
@@ -86,51 +86,51 @@ We will add an HTTP server farm to our service. This part is responsible for dis
 
 #### From the OVHcloud Control Panel
 
-In the `Server Farms`{.action} tab, click on the `Add a server farm`{.action} button.
+In the `Server Farms`{.action} tab, click the `Add a server farm`{.action} button.
 
 Fill in the fields. The only mandatory fields for a simple configuration are the *Protocol* and the *Datacentre*. It is recommended to explicitly define a *Port*, generally port 80 for a web service. If no port is specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding frontend and the probes may not work as expected.
 
 If you add several servers in your farm, it is recommended to configure an HTTP `availability probe`. When a probe is configured, the OVHcloud Load Balancer service can automatically disable a server that is down or under maintenance, in order not to affect visitors.
 
 ![Adding a server farm via the OVHcloud Control Panel](images/add_backend.png){.thumbnail}
 
-Click on the `Add`{.action} button once the fields are filled in.
+Click the `Add`{.action} button once you have filled in the fields.
 
 Your server farm should appear in the list, under the `Server Farms`{.action} tab.
 
 ![Details of the created server farm](images/resume_backend.png){.thumbnail}
 
 #### From the OVHcloud API
 
-- List of HTTP server farms :
+- List of HTTP server farms:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm
 > 
 
-- Details of a specific HTTP server :
+- Details of a specific HTTP server:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId}
 > 
 
-- Adding a new HTTP server farm :
+- Adding a new HTTP server farm:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm
 > 
 
-- Modifying a specific server farm :
+- Modifying a specific server farm:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}
 > 
 
-- Deleting a specific server farm :
+- Deleting a specific server farm:
 
 > [!api]
 >
@@ -143,49 +143,49 @@ We will now add a server to our server farm.
 
 #### From the OVHcloud Control Panel
 
-Still in the `Server Farms`{.action} tab, select the farm to which you want to add a server by clicking on the corresponding line. The list of servers already configured in the farm appears below the list of farms, as well as a `Add a server`{.action} button. Click on this button to add a new server.
+Still in the `Server Farms`{.action} tab, select the farm to which you want to add a server by clicking on the corresponding line. The list of servers already configured in the farm appears below the list of farms, as well as the `Add a server`{.action} button. Click on this button to add a new server.
 
 Only the *IPv4 Address* field is mandatory. If a server does not use the same port as the one defined above in the farm, it is possible to override it in the server configuration. However, in order to maintain the most homogeneous and maintainable configuration possible, it is recommended to use this parameter only in advanced cases.
 
 ![Adding a server to a Farm.](images/add_server.png){.thumbnail}
 
-Click on the `Add`{.action} button once the fields are filled in.
+Click the `Add`{.action} button once you have filled in the fields.
 
 Your server should appear in the list of servers, in the `Server Farms`{.action} tab, just below the list of farms.
 
 ![Details of the created server.](images/resume_server.png){.thumbnail}
 
 #### From the OVHcloud API
 
-- List of servers in the farm :
+- List of servers in the farm:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server
 > 
 
-- Details of a specific server :
+- Details of a specific server:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server/{serverId}
 > 
 
-- Adding a new server :
+- Adding a new server:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server
 > 
 
-- Modifying a specific server :
+- Modifying a specific server:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server
 > 
 
-- Deleting a specific server :
+- Deleting a specific server:
 
 > [!api]
 >
@@ -198,51 +198,51 @@ We will now add a `frontend` to our service and connect it to our server farm. T
 
 #### From the OVHcloud Control Panel
 
-In the `Frontends`{.action} tab, click on the `Add a frontend`{.action} button.
+In the `Frontends`{.action} tab, click the `Add a frontend`{.action} button.
 
 Fill in the fields. The only mandatory fields for a simple configuration are the *Protocol*, the *Port* (80 for a standard HTTP web service) and the *Datacentre*. If you want your service to be available on several ports at the same time, you can specify a list of ports separated by commas or a range of ports in the form "START_PORT-END_PORT".
 
 If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a frontend to one or more specific Additional IPs.
 
 ![Adding a frontend](images/add_frontend.png){.thumbnail}
 
-Click on the `Add`{.action} button once the fields are filled in.
+Click the `Add`{.action} button once you have filled in the fields.
 
 Your frontend should appear in the list, under the `Frontends`{.action} tab.
 
 ![Details of the created frontend](images/resume_frontend.png){.thumbnail}
 
 #### From the OVHcloud API
 
-- List of HTTP frontends :
+- List of HTTP frontends:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/frontend
 > 
 
-- Details of a specific frontend :
+- Details of a specific frontend:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/frontend/{frontendId}
 > 
 
-- Adding a new frontend :
+- Adding a new frontend:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend
 > 
 
-- Modifying a specific frontend :
+- Modifying a specific frontend:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/frontend/{frontendId}
 > 
 
-- Deleting a specific frontend :
+- Deleting a specific frontend:
 
 > [!api]
 >
@@ -251,20 +251,20 @@ Your frontend should appear in the list, under the `Frontends`{.action} tab.
 
 ### Add an SSL/TLS certificate <a name="certificate"></a>
 
-The previous section described the general configuration for an HTTP frontend. This section describes the additional steps to enable support for the HTTPS protocol on an HTTP frontend. In particular, you will need to :
+The previous section described the general configuration for an HTTP frontend. This section describes the additional steps to enable support for the HTTPS protocol on an HTTP frontend. In particular, you will need to:
 
-- switch the frontend to port 443, the standard port for the HTTPS protocol ;
+- switch the frontend to port 443, the standard port for the HTTPS protocol;
 - configure an SSL/TLS certificate to authenticate and encrypt the connections.
 
-Whether you choose a configuration via the API or via the OVHcloud Control Panel, you will have a choice between 2 strategies for your SSL/TLS certificates. This choice depends on your needs as well as the current solutions in place :
+Whether you choose a configuration via the API or via the OVHcloud Control Panel, you will have a choice between 2 strategies for your SSL/TLS certificates. This choice depends on your needs as well as the current solutions in place:
 
 - Import an existing SSL/TLS certificate.
 - Order an automatically managed SSL/TLS certificate. The ordering of DV and EV certificates will be available soon.
 
 If you choose to import an SSL/TLS certificate that you have ordered and managed yourself, you will have to renew it periodically yourself and update it in your OVHcloud Load Balancer service. Most certificates are valid for 1 year. Some may be valid for longer. Let's Encrypt certificates are valid for 3 months. It is recommended to use the service managed automatically by your OVHcloud Load Balancer for Let's Encrypt certificates in order not to accidentally miss a deadline.
 
 If you choose a certificate managed by your OVHcloud Load Balancer service, it will be automatically ordered, validated, installed and renewed periodically by your OVHcloud Load Balancer.<br>
-For the validation and renewal operations to work, it is necessary that the domain(s) for which you order this certificate are routed to your OVHcloud Load Balancer service. This implies that the *A* and *AAAA* fields of your domain point respectively to the IPv4 and IPv6 of your OVHcloud Load Balancer or one of its Additional IPs. During the order, you will receive an email that will guide you through the validation steps.
+For the validation and renewal operations to work, the domain(s) you are ordering this certificate for must be routed to your OVHcloud Load Balancer service. This implies that the *A* and *AAAA* fields of your domain point respectively to the IPv4 and IPv6 of your OVHcloud Load Balancer or one of its Additional IPs. During the order, you will receive an email that will guide you through the validation steps.
 
 > [!primary]
 >
@@ -275,12 +275,15 @@ For the validation and renewal operations to work, it is necessary that the doma
 The certificates configured on your OVHcloud Load Balancer service are automatically available for all frontends of your OVHcloud Load Balancer service on which the *SSL* option is enabled.
 
 #### TLS 1.3 support
+
 With the constant evolution of security standards on the Internet, OVHcloud is committed to providing the most recent and secure technologies for your services. The OVHcloud Load Balancer now supports TLS 1.3.
 
-##### What is TLS 1.3 ?
+##### **What is TLS 1.3?**
+
 TLS 1.3 is the latest version of the TLS protocol, offering significant improvements in terms of security and performance compared to TLS 1.2. The key advantages include a faster *handshake* process, thus reducing the time needed to establish secure connections, and the use of safer encryption suites to strengthen the security of transmitted data.
 
-##### Why use TLS 1.3 with OVHcloud Load Balancer ?
+##### **Why use TLS 1.3 with OVHcloud Load Balancer?**
+
 By integrating TLS 1.3, your OVHcloud Load Balancer will benefit from enhanced security and improved performance, ensuring an optimal user experience for your visitors. The reduction in *handshake* time speeds up page loading, while the security improvements ensure that your data is protected with the most recent and secure standards.
 
 #### From the OVHcloud Control Panel
@@ -291,7 +294,7 @@ The list of SSL/TLS certificates configured on your OVHcloud Load Balancer servi
 
 If you choose to import an existing SSL/TLS certificate, click on `Add an SSL certificate`{.action}. The *Private Key* and *Certificate* fields are mandatory.
 
-Click on the `Add`{.action} button once the fields are filled in. Your certificate will then appear in the certificate list.
+Click the `Add`{.action} button once the fields are filled in. Your certificate will then appear in the certificate list.
 
 ![Adding an existing certificate](images/add_certificat_custom.png){.thumbnail}
 
@@ -303,27 +306,26 @@ Once your certificate(s) are configured, you can create an HTTPS frontend, on th
 Optionally, you can also enable the *HSTS* option. If this option is enabled, browsers will record that this website should *never again* be visited without HTTPS after their first visit in HTTPS. This strengthens overall security by protecting against "Man-in-the-middle" attacks in which a malicious actor could make your website appear unavailable in HTTPS and force your visitors to switch to "HTTP".
 
 > [!warning]
->
 > Although the added security is significant, it is recommended to wait a while before enabling this option, to make sure there are no side effects in HTTPS. Indeed, once HSTS is enabled, there is no going back.
 >
 
 #### From the OVHcloud API
 
-- List the existing SSL/TLS certificates :
+- List the existing SSL/TLS certificates:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/ssl
 > 
 
-- Get the details of an SSL/TLS certificate :
+- Get the details of an SSL/TLS certificate:
 
 > [!api]
 >
 > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/ssl/{id}
 > 
 
-- Adding a new existing SSL/TLS certificate :
+- Adding a new existing SSL/TLS certificate:
 
 > [!api]
 >
@@ -337,7 +339,7 @@ Optionally, you can also enable the *HSTS* option. If this option is enabled, br
 > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/ssl/{id}
 > 
 
-- Deleting a specific SSL/TLS certificate :
+- Deleting a specific SSL/TLS certificate:
 
 > [!api]
 >
@@ -352,7 +354,7 @@ If you have several zones, you will have to apply the same configuration for eac
 
 #### From the OVHcloud Control Panel
 
-Go to the home page of your OVHcloud Load Balancer service and click on the `Apply the configuration`{.action} button.
+Go to the home page of your OVHcloud Load Balancer service, click on the `...`{.action} dots next to the name of your service and click on `Apply the configuration`{.action}.
 
 ![Apply the configuration](images/btn_apply_configuration.png){.thumbnail}
 
@@ -362,7 +364,7 @@ Then select the list of zones you want to deploy and click on the `Apply the con
 
 #### From the OVHcloud API
 
-- Refresh a zone :
+- Refresh a zone:
 
 > [!api]
 >
@@ -375,4 +377,4 @@ Once all these steps are completed, you should have a functional load balancing
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
