fix(es): change endpoint format (#4353)

RoRoJ · web-flow · commit 398f2bf6db21 · 2025-02-26T15:15:28.000+01:00
diff --git a/pages/edge-services/concepts.mdx b/pages/edge-services/concepts.mdx
@@ -33,7 +33,7 @@ Edge Services is an additional feature for Scaleway Load Balancers and Object St
 
 ## Endpoint
 
-The endpoint from which a given Edge Services pipeline can be accessed, e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`. When a client requests content from the Edge Services endpoint, it is served by Edge Services and its cache, rather than from the origin (Object Storage bucket or Load Balancer backend servers) directly. Edge Services automatically manages redirection from HTTP to HTTPS.
+The endpoint from which a given Edge Services pipeline can be accessed, e.g. `https://pipeline-id.svc.edge.scw.cloud`. When a client requests content from the Edge Services endpoint, it is served by Edge Services and its cache, rather than from the origin (Object Storage bucket or Load Balancer backend servers) directly. Edge Services automatically manages redirection from HTTP to HTTPS.
 
 The endpoint can be customized with a user-defined subdomain, allowing you to replace the standardized endpoint with the subdomain of a domain you already own, e.g. `http://my-own-domain.com`. An associated [certificate](#certificate), and [CNAME record](#cname-record) will be required, in this case.
 
diff --git a/pages/edge-services/how-to/configure-custom-domain.mdx b/pages/edge-services/how-to/configure-custom-domain.mdx
@@ -108,7 +108,7 @@ After customizing your domain, you can edit it (or its certificate) at any time
 
 ## How to reset your customized domain
 
-Even though the original Edge Services endpoint (e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`) will continue to work after you add a customized domain, you can choose to remove your customized domain completely and go back to the original Edge Services endpoint only. This is done via the reset function:
+Even though the original Edge Services endpoint (e.g. `https://pipeline-id.svc.edge.scw.cloud`) will continue to work after you add a customized domain, you can choose to remove your customized domain completely and go back to the original Edge Services endpoint only. This is done via the reset function:
 
 1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to reset:
 
diff --git a/pages/edge-services/how-to/create-pipeline-bucket.mdx b/pages/edge-services/how-to/create-pipeline-bucket.mdx
@@ -58,11 +58,11 @@ You can create an Edge Services pipeline [from the Object Storage section of the
 
 ## How to access your bucket via Edge Services
 
-Once you have created an Edge Services pipeline for your bucket, you can access your bucket and its content via the following endpoints. Make sure that you replace `bucket-name` with the name of your bucket.
+Once you have created an Edge Services pipeline for your bucket, you can access your bucket and its content via the following endpoints. Make sure that you replace `bucket-name` or `pipeline-id` with relevant details for your bucket/pipeline.
 
 | Endpoint                                | Where to find this endpoint in the console | Notes                                                           |
 |-----------------------------------------|--------------------------|-----------------------------------------------------------------------------------|
 | `https://bucket-name.s3.nl-ams.scw.cloud` | The **Bucket settings** tab                | Edge Services is bypassed when the bucket is accessed via this endpoint  |
-| `https://bucket-name.svc.edge.scw.cloud`  | The **Edge Services** tab                  | Edge Services serves bucket content when this endpoint is used |
+| `https://pipeline-id.svc.edge.scw.cloud`  | The **Edge Services** tab                  | Edge Services serves bucket content when this endpoint is used |
 
 The two endpoints shown above are available as standard. However, with Edge Services, you can also choose to configure a **custom domain** from which your bucket can be accessed. Read more about this in the [next section](/edge-services/how-to/configure-custom-domain/).
diff --git a/pages/edge-services/how-to/create-pipeline-lb.mdx b/pages/edge-services/how-to/create-pipeline-lb.mdx
@@ -58,7 +58,7 @@ You can create an Edge Services pipeline from the Load Balancer section of the c
 
     You are returned to the **Pipelines** tab, where the newly created pipeline now displays. 
 
-    Click on the pipeline to go to its **Overview** page and start configuration. From the **Overview**, you can see the endpoint from which you can access your Load Balancer origin via Edge Services, e.g. `https://pipeline-id.edge.scw.cloud`.
+    Click on the pipeline to go to its **Overview** page and start configuration. From the **Overview**, you can see the endpoint from which you can access your Load Balancer origin via Edge Services, e.g. `https://pipeline-id.svc.edge.scw.cloud`.
 
 ## Troubleshooting pipeline creation
 
diff --git a/pages/edge-services/reference-content/cname-record.mdx b/pages/edge-services/reference-content/cname-record.mdx
@@ -30,7 +30,7 @@ When the client actually connects to `otherdomain.com`'s IP address, the web ser
 
 ## When and why do I need to create a CNAME record for Edge Services?
 
-When you create an Edge Services pipeline to an [origin](/edge-services/concepts/#origin) (Object Storage bucket or Load Balancer), initially the origin content is served through the standard Edge Services endpoint, e.g. `pipeline-id-or-bucket-name.svc.edge.scw.cloud`. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about CNAME records.
+When you create an Edge Services pipeline to an [origin](/edge-services/concepts/#origin) (Object Storage bucket or Load Balancer), initially the origin content is served through the standard Edge Services endpoint, e.g. `pipeline-id.svc.edge.scw.cloud`. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about CNAME records.
 
 However, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), a CNAME record must be created to point your subdomain to the Edge Services endpoint. 
 
@@ -47,22 +47,22 @@ The interface used by different domain providers varies, but creating your CNAME
 
 | Record                                     | Destination                              |
 |--------------------------------------------|------------------------------------------|
-| `my-chosen-subdomain.beautiful-domain.com` | `pipeline-id-or-bucket-name.svc.edge.scw.cloud.`         |
+| `my-chosen-subdomain.beautiful-domain.com` | `pipeline-id.svc.edge.scw.cloud.`         |
 
 | Subdomain                                  | Target host                                    |
 |--------------------------------------------|------------------------------------------------|
-| `my-chosen-subdomain`                      | `pipeline-id-or-bucket-name.svc.edge.scw.cloud.`               |
+| `my-chosen-subdomain`                      | `pipeline-id.svc.edge.scw.cloud.`               |
 
 | Host record                                | Points to                                      |
 |--------------------------------------------|------------------------------------------------|
-| `my-chosen-subdomain`                      | `pipeline-id-or-bucket-name.svc.edge.scw.cloud.`               |
+| `my-chosen-subdomain`                      | `pipeline-id.svc.edge.scw.cloud.`               |
 
 | `my-chosen-subdomain`                      | Record Type     | Value                                          |
 |--------------------------------------------|-----------------|------------------------------------------------|
-| `@`                                        | `CNAME`         | is an alias of `pipeline-id-or-bucket-name.svc.edge.scw.cloud.`|
+| `@`                                        | `CNAME`         | is an alias of `pipeline-id.svc.edge.scw.cloud.`|
 
 <Message type="tip">
-The trailing dot at the end of the target endpoint (`pipeline-id-or-bucket-name.svc.edge.scw.cloud.`) is implicitly added by some domain and DNS providers, and must be explicitly added for others. Check with yours whether the dot is necessary.
+The trailing dot at the end of the target endpoint (`pipeline-id.svc.edge.scw.cloud.`) is implicitly added by some domain and DNS providers, and must be explicitly added for others. Check with yours whether the dot is necessary.
 </Message>
 
 You may also see a `TTL` field, which stands for **T**ime **T**o **L**ive.  This tells the DNS resolver how long it can cache this record, before it must re-check the origin source in case something has changed. TTL is measured in seconds, and the default value is usually 12 hours (43200 seconds) or 24 hours (86400 seconds). 
@@ -82,7 +82,7 @@ See the table below for help with troubleshooting these errors:
 | Error message                             | Solution                                                            |
 |-------------------------------------------|---------------------------------------------------------------------|
 | No CNAME record found                     | Make sure you have created a valid DNS record of type **CNAME** (not **A**, **AAAA** or another type), where your subdomain points to the Edge Services endpoint.  |
-| Incorrect CNAME                           | Make sure your CNAME record points to the Edge Services endpoint in the format `bucket-name.svc.edge.scw.cloud.`, and that you have replaced `pipeline-id-or-bucket-name` with the name of your bucket in the case of an Object Storage origin, or the pipeline ID in the case of a Load Balancer origin.                                            |
+| Incorrect CNAME                           | Make sure your CNAME record points to the Edge Services endpoint in the format `pipeline-id.svc.edge.scw.cloud.`, and that you have replaced `pipeline-id` with the ID of your bucket or Load Balancer's Edge Services pipeline.        |
 | Domain does not exist                     | You must own the domain name you are attempting to configure. If you do not already own the domain name, you cannot create a subdomain or CNAME record for it. Register the domain name, for example using our [Domains and DNS](/domains-and-dns/how-to/register-internal-domain/) product, then create a CNAME record for the subdomain. Otherwise, ensure you did not make a typo when entering the domain name into the Scaleway console.                     |
 | scw.cloud is forbidden                    | You cannot use subdomains of the `scw.cloud` domain, as the domain is owned and managed by Scaleway and you cannot create DNS records for it. Use your own domain and subdomain.                   |
 | Invalid Top Level Domain                  | Make sure the Top-Level Domain (e.g. `.com`, `.fr`) you entered is correct.                    |
diff --git a/pages/edge-services/reference-content/ssl-tls-certificate.mdx b/pages/edge-services/reference-content/ssl-tls-certificate.mdx
@@ -28,7 +28,7 @@ The private key is also used by the host for generating digital signatures, whil
 
 ### When and why do I need an SSL/TLS certificate for Edge Services?
 
-When you create an Edge Services pipeline, initially your [origin's](/edge-services/concepts/#origin) content is served through the standard Edge Services endpoint, e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`. Scaleway's own SSL/TLS certificate, which covers this subdomain, is used to establish the encrypted connection between client and host. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about creating SSL/TLS certificates.
+When you create an Edge Services pipeline, initially your [origin's](/edge-services/concepts/#origin) content is served through the standard Edge Services endpoint, e.g. `https://pipeline-id.svc.edge.scw.cloud`. Scaleway's own SSL/TLS certificate, which covers this subdomain, is used to establish the encrypted connection between client and host. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about creating SSL/TLS certificates.
 
 However, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), Scaleway's own SSL/TLS certificate can no longer be used to establish encrypted connections to your subdomain. Client connections are now initially going to a different domain which needs to be "guaranteed" by its own certificate (despite the CNAME record for the subdomain pointing to the Scaleway endpoint). 
 
