diff --git a/faq/assets/scaleway-edge-services-pipeline.webp b/faq/assets/scaleway-edge-services-pipeline.webp new file mode 100644 index 0000000000..49ffb573d9 Binary files /dev/null and b/faq/assets/scaleway-edge-services-pipeline.webp differ diff --git a/faq/edge-services.mdx b/faq/edge-services.mdx index a903a69be2..5be9dc3dae 100644 --- a/faq/edge-services.mdx +++ b/faq/edge-services.mdx @@ -12,7 +12,11 @@ category: network ## What is Edge Services? -Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets, currently available in [Public Beta](https://www.scaleway.com/en/betas/). It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/network/edge-services/concepts/#origin), and a customizable and secure endpoint for accessing content via Edge Services, which can be set to a subdomain of your choice. +Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets. Creating Edge Services [pipelines](/network/edge-services/concepts/#pipeline) towards your Load Balancers or Object Storage buckets provides: +-A [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/network/edge-services/concepts/#origin), and +- A customizable and secure endpoint for accessing content via Edge Services, which can be set to a subdomain of your choice and secured with an SSL/TLS certificate. + + ## Which products are compatible with Edge Services? @@ -20,7 +24,9 @@ Edge Services is currently available for Scaleway [Object Storage buckets](/stor ## How much does Edge Services cost? -Since Edge Services is currently in Public Beta, it is free to use and not billed. On November 1st 2024, it will transition to General Availability, and pricing will be based on subscription plans. See our documentation for help with understanding the [transition to General Availability](/network/edge-services/reference-content/understanding-ga/). +On November 1st 2024, Edge Services transitioned from Public Beta to General Availability, and became billable. Pricing is based on [monthly subscription plans](https://www.scaleway.com/en/pricing/network/#edge-services): three plans are available, each allowing a fixed number of pipelines, and a certain amount of egress cache data. Any consumption that exceeds the limits of the plan is charged at an additional rate. + +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page. ## If I customize my Edge Services endpoint with my own domain, can it serve content over HTTPS? diff --git a/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx b/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx index 3f8b85c27c..8fe8dbcc20 100644 --- a/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx +++ b/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx @@ -377,6 +377,14 @@ Additional IP addresses and placement groups are available with our compute offe |---------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Load Balancers | 50 | 50 | +## Edge Services + + + +| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +|---------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| +| Edge Services pipelines | 20 | 20 | + ## Domains and DNS diff --git a/macros/edge-services/assets/scaleway-edge-services-pipeline.webp b/macros/edge-services/assets/scaleway-edge-services-pipeline.webp new file mode 100644 index 0000000000..49ffb573d9 Binary files /dev/null and b/macros/edge-services/assets/scaleway-edge-services-pipeline.webp differ diff --git a/macros/edge-services/edge-services-bucket-benefits.mdx b/macros/edge-services/edge-services-bucket-benefits.mdx new file mode 100644 index 0000000000..929b4d22a7 --- /dev/null +++ b/macros/edge-services/edge-services-bucket-benefits.mdx @@ -0,0 +1,10 @@ +--- +macro: edge-services-bucket-benefits +--- + +- Customize your bucket's endpoint using a subdomain of your own domain +- Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/), or generate a managed Let's Encrypt certificate, so your subdomain can serve content from your bucket over HTTPS +- Enhance performance by caching your stored objects, to be served directly by Edge Services from the cache +- Finely control your cached objects via purging (cache invalidation) + + \ No newline at end of file diff --git a/macros/edge-services/edge-services-lb-benefits.mdx b/macros/edge-services/edge-services-lb-benefits.mdx new file mode 100644 index 0000000000..3b61e4baac --- /dev/null +++ b/macros/edge-services/edge-services-lb-benefits.mdx @@ -0,0 +1,16 @@ +--- +macro: edge-services-lb-benefits +--- + +Creating an Edge Services pipeline for your Load Balancer helps to reduce load on your Load Balancer's backend servers. The origin configuration you define is used by Edge Services to connect to your Load Balancer and request content, which is then stored in the cache. Then, when your Load Balancer origin is accessed via its customizable Edge Services endpoint, the requested content is served from the cache (if present), without the need to fetch this content via the Load Balancer and its backend servers. + + + +Edge Services lets you: + +- Define the specific origin (Load Balancer, frontend port, and host) for a given pipeline and its associated cache +- Choose the TTL for cached objects, and purge the entire cache or specific cached objects at any time (cache invalidation) +- Customize your Edge Services pipeline endpoint using a subdomain of your own domain +- Add an SSL/TLS certificate so that Edge Services can serve content over HTTPS for your subdomain + +An Edge Services pipeline can be created for any Load Balancer with a public IP address. Load Balancers with frontends/backends using both TCP and/or HTTP are supported. [Private Load Balancers](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services. \ No newline at end of file diff --git a/macros/edge-services/network-edge-services.mdx b/macros/edge-services/network-edge-services.mdx new file mode 100644 index 0000000000..02ae76b484 --- /dev/null +++ b/macros/edge-services/network-edge-services.mdx @@ -0,0 +1,5 @@ +--- +macro: network-edge-services +--- + +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a caching service to improve performance by reducing load on your origin, and a customizable and secure endpoint for accessing content via Edge Services, which can be set to a subdomain of your choice. \ No newline at end of file diff --git a/menu/navigation.json b/menu/navigation.json index b5ae132c4b..0cb68654ac 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3075,6 +3075,10 @@ "label": "Use a Load Balancer with a Private Network", "slug": "use-with-private-network" }, + { + "label": "Set up an Edge Services pipeline", + "slug": "use-edge-services" + }, { "label": "Set up a customized error page", "slug": "set-up-s3-failover" @@ -3193,6 +3197,10 @@ }, { "items": [ + { + "label": "Subscribe to Edge Services", + "slug": "subscribe-edge-services" + }, { "label": "Create an Object Storage pipeline", "slug": "create-pipeline-bucket" @@ -3214,8 +3222,12 @@ "slug": "monitor-cockpit" }, { - "label": "Delete or disable an Edge Services pipeline", + "label": "Delete an Edge Services pipeline", "slug": "delete-pipeline" + }, + { + "label": "Terminate an Edge Services subscription", + "slug": "terminate-edge-services" } ], "label": "How to", @@ -3231,6 +3243,10 @@ "label": "CNAME records for Edge Services", "slug": "cname-record" }, + { + "label": "Understanding pricing", + "slug": "understanding-pricing" + }, { "label": "Understanding General Availability", "slug": "understanding-ga" @@ -4230,6 +4246,10 @@ "label": "Use Object Storage with Private Networks", "slug": "use-obj-stor-with-private-networks" }, + { + "label": "Set up an Edge Services pipeline", + "slug": "get-started-edge-services" + }, { "label": "Delete an object", "slug": "delete-an-object" diff --git a/network/edge-services/assets/scaleway-create-pipeline-lb.webp b/network/edge-services/assets/scaleway-create-pipeline-lb.webp new file mode 100644 index 0000000000..b2840e1f6b Binary files /dev/null and b/network/edge-services/assets/scaleway-create-pipeline-lb.webp differ diff --git a/network/edge-services/assets/scaleway-edge-create-pipeline-os.webp b/network/edge-services/assets/scaleway-edge-create-pipeline-os.webp new file mode 100644 index 0000000000..bdeb85751f Binary files /dev/null and b/network/edge-services/assets/scaleway-edge-create-pipeline-os.webp differ diff --git a/network/edge-services/assets/scaleway-edge-pipelines.webp b/network/edge-services/assets/scaleway-edge-pipelines.webp new file mode 100644 index 0000000000..49f8cb4408 Binary files /dev/null and b/network/edge-services/assets/scaleway-edge-pipelines.webp differ diff --git a/network/edge-services/assets/scaleway-edge-services-pipeline.webp b/network/edge-services/assets/scaleway-edge-services-pipeline.webp new file mode 100644 index 0000000000..49ffb573d9 Binary files /dev/null and b/network/edge-services/assets/scaleway-edge-services-pipeline.webp differ diff --git a/network/edge-services/concepts.mdx b/network/edge-services/concepts.mdx index a3421def7d..6815b51a1d 100644 --- a/network/edge-services/concepts.mdx +++ b/network/edge-services/concepts.mdx @@ -8,7 +8,7 @@ content: tags: edge-services edge services pipeline custom-domain cache dates: creation: 2024-07-24 - validation: 2024-07-24 + validation: 2024-10-14 categories: - networks --- @@ -29,7 +29,7 @@ The CNAME record pointing your subdomain to the Edge Services endpoint, if you h ## Edge Services -Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets, currently available in [Public Beta](https://www.scaleway.com/en/betas/). It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice. +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice. ## Endpoint @@ -56,9 +56,11 @@ The Load Balancer defined by the user as origin for a given Edge Services pipeli ## Pipeline + + An Edge Services pipeline consists of an [origin](#origin) for which Edge Services requests and [caches](#cache) content, and an [endpoint](#endpoint) from which this content is served via Edge Services. The pipeline's endpoint can be customized with a user-defined [subdomain](#subdomain) and associated [certificate](#certificate) so that Edge Services can serve content over HTTPS. -You can create one or more Edge Services pipelines for each of your Object Storage buckets or Load Balancer origins. +You can create an Edge Services pipeline for each of your Object Storage buckets or Load Balancer origins. Note that the cache can be enabled and disabled at will, so it is an optional part of the pipeline, as is the customization of the endpoint. ## Protocol diff --git a/network/edge-services/how-to/assets/scaleway-create-pipeline-lb.webp b/network/edge-services/how-to/assets/scaleway-create-pipeline-lb.webp new file mode 100644 index 0000000000..b2840e1f6b Binary files /dev/null and b/network/edge-services/how-to/assets/scaleway-create-pipeline-lb.webp differ diff --git a/network/edge-services/how-to/assets/scaleway-edge-create-pipeline-os.webp b/network/edge-services/how-to/assets/scaleway-edge-create-pipeline-os.webp new file mode 100644 index 0000000000..bdeb85751f Binary files /dev/null and b/network/edge-services/how-to/assets/scaleway-edge-create-pipeline-os.webp differ diff --git a/network/edge-services/how-to/assets/scaleway-edge-pipelines.webp b/network/edge-services/how-to/assets/scaleway-edge-pipelines.webp new file mode 100644 index 0000000000..49f8cb4408 Binary files /dev/null and b/network/edge-services/how-to/assets/scaleway-edge-pipelines.webp differ diff --git a/network/edge-services/how-to/assets/scaleway-edge-services-pipeline.webp b/network/edge-services/how-to/assets/scaleway-edge-services-pipeline.webp new file mode 100644 index 0000000000..49ffb573d9 Binary files /dev/null and b/network/edge-services/how-to/assets/scaleway-edge-services-pipeline.webp differ diff --git a/network/edge-services/how-to/assets/scaleway-edge-services-splash.webp b/network/edge-services/how-to/assets/scaleway-edge-services-splash.webp deleted file mode 100644 index 16412c63db..0000000000 Binary files a/network/edge-services/how-to/assets/scaleway-edge-services-splash.webp and /dev/null differ diff --git a/network/edge-services/how-to/configure-cache.mdx b/network/edge-services/how-to/configure-cache.mdx index 86ede6eab2..653ce172f7 100644 --- a/network/edge-services/how-to/configure-cache.mdx +++ b/network/edge-services/how-to/configure-cache.mdx @@ -6,7 +6,7 @@ content: h1: How to configure an Edge Services cache paragraph: Learn how to configure a cache for Edge Services. Enhance performance and finely control your cached objects via purging (cache invalidation). dates: - validation: 2024-07-24 + validation: 2024-10-15 posted: 2024-07-24 tags: object-storage edge-services cdn network cache purge categories: @@ -19,7 +19,7 @@ You can disable and enable caching at will, as well as control the lifetime of a ## How to enable the cache -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin for which you want to enable caching: +1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline on which you want to enable caching: @@ -41,7 +41,7 @@ The cache is now enabled. Purging objects clears all objects from your cache. Afterward, Edge Services will retrieve fresh copies from the origin (Object Storage bucket or Load Balancer) before it stores them again in the cache. -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose cache you want to purge: +1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge: @@ -57,7 +57,7 @@ Purging objects clears all objects from your cache. Afterward, Edge Services wil This allows you to specify the precise objects that you want to clear from the cache. Afterward, Edge Services will retrieve fresh copies from the origin (Object Storage bucket or Load Balancer) before it stores them again in the cache. -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose cache you want to purge: +1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge: @@ -88,9 +88,19 @@ This allows you to specify the precise objects that you want to clear from the c The specified objects are purged from your cache and you are returned to the Edge Services dashboard. +## How to use Cache-Control + +To avoid repeated purging, you can also set the `Cache-Control` HTTP header directly on your files/objects. This allows you to define how long items should remain in the cache before being freshly retrieved from the origin. Edge Services will respect this header when determining where to fetch content. + +For Object Storage bucket origins, the following example call to the S3 API updates the `Cache-Control` header for **all** objects in the bucket, setting a maximum age of 60 seconds before they must be freshly retrieved. + +``` +./s3cmd --recursive modify --add-header="Cache-Control:max-age=60" s3://yourbucket/ +``` + ## How to disable your cache -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose cache you want to disable: +1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to disable: diff --git a/network/edge-services/how-to/configure-custom-domain.mdx b/network/edge-services/how-to/configure-custom-domain.mdx index e16214e7e8..df883a4694 100644 --- a/network/edge-services/how-to/configure-custom-domain.mdx +++ b/network/edge-services/how-to/configure-custom-domain.mdx @@ -6,7 +6,7 @@ content: h1: How to configure a custom domain for Edge Services paragraph: Learn how to configure an Edge Services endpoint with a custom subdomain. Access your Object Storage bucket or Load Balancer origin via your own domain name instead of the standardized endpoint. dates: - validation: 2024-07-24 + validation: 2024-10-15 posted: 2024-07-24 tags: object-storage edge-services cdn network domain ssl tls https categories: @@ -23,7 +23,7 @@ You cannot customize your endpoint with a primary domain directly (e.g. `beautif The procedure for adding a customized endpoint is as follows: -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to customize: +1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline whose domain you want to customize: @@ -94,7 +94,7 @@ If you chose to generate a managed Let's Encrypt certificate, allow a few minute After customizing your domain, you can edit it (or its certificate) at any time as follows: -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to customize: +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 customize: @@ -110,7 +110,7 @@ After customizing your domain, you can edit it (or its certificate) at any time 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: -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to reset: +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/network/edge-services/how-to/create-pipeline-bucket.mdx b/network/edge-services/how-to/create-pipeline-bucket.mdx index f56b8589ec..65217fa161 100644 --- a/network/edge-services/how-to/create-pipeline-bucket.mdx +++ b/network/edge-services/how-to/create-pipeline-bucket.mdx @@ -6,52 +6,49 @@ content: h1: How to create an Edge Services pipeline for an Object Storage bucket paragraph: This page explains how to configure an Edge Services pipeline for a Scaleway Object Storage bucket. Set up your own custom domain to point to your bucket, and enable a caching service for faster and more efficient delivery. dates: - validation: 2024-07-24 + validation: 2024-10-15 posted: 2024-07-24 tags: object-storage edge-services cdn network cache domain https categories: - network --- -Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets, currently available in [Public Beta](https://www.scaleway.com/en/betas/). +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. Creating an Edge Services pipeline towards your Object Storage bucket brings you a number of possible benefits: -Enabling Edge Services on your Object Storage bucket creates an Edge Services pipeline which brings you a number of possible benefits: + -- Customize your bucket's endpoint using a subdomain of your own domain -- Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/), or generate a managed Let's Encrypt certificate, so your subdomain can serve content from your bucket over HTTPS -- Enhance performance by caching your stored objects, to be served directly by Edge Services from the cache -- Finely control your cached objects via purging (cache invalidation) - -Read on to learn how to create an Edge Services pipeline by enabling Edge Services on your bucket. +Read on to learn how to create an Edge Services pipeline for your Object Storage bucket. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An active [Edge Services subscription](/network/edge-services/how-to/subscribe-edge-services/) - An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) ## How to create an Edge Services pipeline -Edge Services is available as a feature on Object Storage buckets. You enable it on a bucket-by-bucket basis. When you enable Edge Services on a particular bucket, a [pipeline](/network/edge-services/concepts/#pipeline) is automatically created for that bucket. + +You can create an Edge Services pipeline [from the Object Storage section of the console](/storage/object/how-to/get-started-edge-services/), by navigating to your bucket's dashboard and clicking the **Edge Services** tab. However, in this documentation, we describe how to create a pipeline directly from the **Edge Services** section of the console. + -1. Click **Object Storage** in the **Storage** section of the Scaleway console side menu. The list of your buckets displays. +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Click the name of the bucket you want to enable Edge Services on. - +2. Click **Create pipeline**. The pipeline creation wizard displays. -3. Click the **Edge Services** tab. + - +3. Select **Object Storage** as the origin type. -4. Click **Enable Edge Services for free**. +4. Choose the bucket you want this pipeline to serve content for, under **Origin bucket**. - A pop-up informs you that your bucket will be exposed via Edge Services and that you can disable Edge Services at any time. Edge Services is free during the beta stage, and you will be notified before it becomes billable. +5. Enter a name for the pipeline, or leave the randomly generated name in place. -5. Click **Enable Edge Services** to confirm. +6. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**. - Edge Services is enabled on your bucket, and a pipeline is automatically created. Various features are now visible on the Edge Services tab, ready to be configured. + 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. @@ -61,7 +58,7 @@ Edge Services is available as a feature on Object Storage buckets. You enable it ## How to access your bucket via Edge Services -Once you have enabled Edge Services on 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` with the name of your bucket. | Endpoint | Where to find this endpoint in the console | Notes | |-----------------------------------------|--------------------------|-----------------------------------------------------------------------------------| diff --git a/network/edge-services/how-to/create-pipeline-lb.mdx b/network/edge-services/how-to/create-pipeline-lb.mdx index 91ece045fd..75c5d0fd9d 100644 --- a/network/edge-services/how-to/create-pipeline-lb.mdx +++ b/network/edge-services/how-to/create-pipeline-lb.mdx @@ -6,71 +6,59 @@ content: h1: How to create an Edge Services pipeline for a Load Balancer paragraph: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery. dates: - validation: 2024-07-24 + validation: 2024-10-15 posted: 2024-07-24 tags: load-balancer edge-services cdn network cache domain https categories: - network --- -Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets, currently available in [Public Beta](https://www.scaleway.com/en/betas/). +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. -Creating an Edge Services pipeline for your Load Balancer helps to reduce load on your Load Balancer's backend servers. The origin configuration you define is used by Edge Services to connect to your Load Balancer and request content, which is then stored in the cache. Then, when your Load Balancer origin is accessed via its customizable Edge Services endpoint, the requested content is served from the cache (if present), without the need to fetch this content via the Load Balancer and its backend servers. - -Edge Services lets you: - -- Define the specific origin (Load Balancer, frontend port, and host) for a given pipeline and its associated cache -- Choose the TTL for cached objects -- Purge the entire cache or specific cached objects at any time (cache invalidation) -- Customize your Edge Services pipeline endpoint using a subdomain of your own domain -- Add an SSL/TLS certificate so that Edge Services can serve content over HTTPS for your subdomain - -An Edge Services pipeline can be created for any Load Balancer with a public IP address. Load Balancers with frontends/backends using both TCP and/or HTTP are supported. [Private Load Balancers](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services. + - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An active [Edge Services subscription](/network/edge-services/how-to/subscribe-edge-services/) - A [Load Balancer](/network/load-balancer/how-to/create-load-balancer/) ## How to create an Edge Services pipeline for Load Balancer -You can create one or more Edge Services pipelines for each of your Load Balancers. Each pipeline has its own [origin](/network/edge-services/concepts/#origin), [endpoint](/network/edge-services/concepts/#endpoint), and [cache](/network/edge-services/concepts/#cache). If you create multiple Edge Services pipelines for the same origin Load Balancer, each one must be configured for a different frontend. - -Follow the steps below to create an Edge Services pipeline. + +You can create an Edge Services pipeline from the Load Balancer section of the console, via the **Edge Services** tab there. However, in this documentation, we describe how to create a pipeline directly from the **Edge Services** section of the console. + -1. Click **Load Balancers** in the **Network** section of the Scaleway console side menu. The list of your Load Balancers displays. - - - -2. Click the **Edge Services** tab. +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. -3. Click **Create Edge Services pipeline**. The pipeline creation wizard displays. +2. Click **Create pipeline**. The pipeline creation wizard displays. - + -4. Configure the [origin](/network/edge-services/concepts/#origin) for this pipeline: - - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content. - - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend. +3. Configure the [origin](/network/edge-services/concepts/#origin) for this pipeline: + - Select **Load Balancer** as the origin type. + - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content. + - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend. - - For Kubernetes Load Balancers, see our [dedicated documentation](#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend. + + For Kubernetes Load Balancers, see our [dedicated documentation](#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend. - + -5. Define the protocol and origin host for this pipeline: - - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup. - - Optionally, enter an [origin host](/network/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. +4. Define the protocol and origin host for this pipeline: + - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup. + - Optionally, enter an [origin host](/network/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. -6. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place. +5. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place. - Edge Services for Load Balancer is free during Public Beta. You will be notified before the service leaves beta and becomes billable. + The summary cost for the creation of this pipeline is displayed, notably whether it falls within the limits of your current [subscription plan](/network/edge-services/reference-content/understanding-edge-pricing/) -7. Click **Create Edge Services pipeline** to finish. +6. Click **Create Edge Services pipeline** to finish. - Your pipeline is created and you are taken to its **Overview** page. The endpoint displays from which you can access your Load Balancer origin via Edge Services, e.g. `https://pipeline-id.edge.scw.cloud`. + 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`. ## Troubleshooting pipeline creation diff --git a/network/edge-services/how-to/delete-pipeline.mdx b/network/edge-services/how-to/delete-pipeline.mdx index 2ec3410e6b..5f03278cdb 100644 --- a/network/edge-services/how-to/delete-pipeline.mdx +++ b/network/edge-services/how-to/delete-pipeline.mdx @@ -1,68 +1,42 @@ --- meta: title: How to delete an Edge Services pipeline - description: Learn how to delete or disable a Scaleway Edge Services pipeline with this step-by-step guide. Follow our instructions to ensure a smooth process and manage your domains and SSL/TLS certificates effectively. + description: Learn how to delete a Scaleway Edge Services pipeline with this step-by-step guide. Follow our instructions to ensure a smooth process and manage your domains and SSL/TLS certificates effectively. content: h1: How to delete an Edge Services pipeline - paragraph: Learn how to delete or disable a Scaleway Edge Services pipeline with this step-by-step guide. Follow our instructions to ensure a smooth process and manage your domains and SSL/TLS certificates effectively. + paragraph: Learn how to delete a Scaleway Edge Services pipeline with this step-by-step guide. Follow our instructions to ensure a smooth process and manage your domains and SSL/TLS certificates effectively. dates: - validation: 2024-07-24 + validation: 2024-10-15 posted: 2024-07-24 tags: load-balancer edge-services cdn network pipeline categories: - network --- -You can delete an Edge Services pipeline at any time. Follow the steps below, depending on whether your pipeline is towards an Object Storage bucket origin or a Load Balancer origin. +You can delete an Edge Services pipeline at any time by following the steps below. -## How to disable Edge Services for an Object Storage bucket + -1. Click **Object Storage** in the **Storage** section of the Scaleway console side menu. The list of your buckets displays. +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An Edge Services pipeline -2. Click the name of the bucket you want to disable Edge Services for. +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The **Pipelines** tab displays. -3. Click the **Edge Services** tab. +2. Click the pipeline that you want to delete. You are taken to the pipeline's **Overview** page - - -4. In the **Disable Edge Services** panel at the bottom of the screen, click **Disable Edge Services**. +4. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**. - A pop-up displays, informing you that the bucket will be removed from Edge Services. - - The bucket will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint. + A pop-up displays, asking you to confirm that you want to delete the pipeline. + - The Load Balancer/Object Storage bucket will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint. - Any files stored in the Edge Services cache will be removed. Remember to: - - Delete your CNAME record from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you. - - Delete any SSL/TLS certificates you imported into Secret Manager (if no longer required elsewhere, so that you are no longer billed for it). If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you. + - Delete any CNAME records created for this pipeline from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you. + - Delete any SSL/TLS certificates you imported into Secret Manager for this pipeline (if no longer required elsewhere), so that you are no longer billed for them. If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you. -5. Click **Disable Edge Services**. - - Edge Services is disabled and the pipeline for this bucket is deleted. You can enable it again at any time to create a new pipeline, but you will need to reconfigure your custom domain, and the cache will initially be empty. - -## How to delete an Edge Services pipeline for a Load Balancer origin - -1. Click **Load Balancers** in the **Network** section of the Scaleway console side menu. The list of your Load Balancers displays. - -2. Click the **Edge Services** tab. A list of your pipelines displays. - -3. Click the pipeline you want to delete. The Edge Services dashboard for that pipeline displays. - - - -4. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**. - - A pop-up displays, informing you that the pipeline will be deleted - - The Load Balancer origin will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint. - - Any files stored in the Edge Services cache for this pipeline will be removed. - - - If you set up a customized domain for your Edge Services endpoint, remember to: - - Delete your CNAME record from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you. - - Delete any SSL/TLS certificates you imported into Secret Manager (if no longer required elsewhere, so that you are no longer billed for it). If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you. - - -5. Click **Confirm*. +5. Click **Confirm**. - The Edge Services pipeline for this Load Balancer origin is deleted. You create a new pipeline at any time, but you will need to reconfigure any custom domains, and the cache will initially be empty. \ No newline at end of file + The Edge Services pipeline is deleted. You can create a new pipeline for this origin at any time, but you will need to reconfigure your custom domain, and the cache will initially be empty. \ No newline at end of file diff --git a/network/edge-services/how-to/monitor-cockpit.mdx b/network/edge-services/how-to/monitor-cockpit.mdx index 05b9028787..fbfeeda2a7 100644 --- a/network/edge-services/how-to/monitor-cockpit.mdx +++ b/network/edge-services/how-to/monitor-cockpit.mdx @@ -6,7 +6,7 @@ content: h1: How to monitor Edge Services with Scaleway Cockpit paragraph: Get easy access to your Edge Services metrics via Scaleway Cockpit. Monitor ingress, egress, request rate and cache hit ratio in a convenient managed Grafana dashboard. dates: - validation: 2024-07-24 + validation: 2024-10-15 posted: 2024-07-24 tags: load-balancer edge-services cdn cache-hit-ratio grafana observability categories: @@ -15,7 +15,12 @@ categories: You can view your Edge Services metrics via [Scaleway Cockpit](/observability/cockpit/quickstart/). This allows you to monitor your ingress, egress, request rate, and cache hit ratio as well as other metrics, in a convenient managed Grafana dashboard. -Access your Edge Services dashboard in the Scaleway console via the shortcut in the Edge Services tab of the pipeline in question. Note that you will first need to [create a Grafana user and credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +Access your Edge Services dashboard in the Scaleway console via either + +- Clicking **Track your Edge Services metrics with Cockpit** shortcut in the **Edge Services** dashboard of the pipeline in question. +- The **Metrics** tab in the **Edge Services** section of the console. + +Note that you will first need to [create a Grafana user and credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). ### Understanding the dashboard diff --git a/network/edge-services/how-to/subscribe-edge-services.mdx b/network/edge-services/how-to/subscribe-edge-services.mdx new file mode 100644 index 0000000000..be3c0298bc --- /dev/null +++ b/network/edge-services/how-to/subscribe-edge-services.mdx @@ -0,0 +1,69 @@ +--- +meta: + title: How to subscribe to Edge Services + description: Find out how to take your first steps with Scaleway Edge Services by subscribing to a pricing plan. Learn how to choose the best plan for your needs and change your plan at the click of a button. +content: + h1: How to subscribe to Edge Services + paragraph: Find out how to take your first steps with Scaleway Edge Services by subscribing to a pricing plan. Learn how to choose the best plan for your needs and change your plan at the click of a button. +dates: + validation: 2024-10-15 + posted: 2024-10-15 +tags: object-storage edge-services subscription-plan subscribe billing pricing +categories: + - network +--- + +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It lets you benefit from a powerful caching service to reduce the load on your origin servers and streamline delivery. On top of this, you get a customizable Edge Services endpoint and can set it to a subdomain of your choice, securing it with an SSL/TLS certificate. + +To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes: + +- A fixed number of Edge Services [pipelines](/network/edge-services/concepts/#pipeline). You can create pipelines for either Load Balancers, Object Storage buckets, or a mixture of both, with your subscription plan. +- A certain amount of egress [cache](/network/edge-services/concepts/#cache) data (the quantity of data transferred from Edge Services' caches, not including the transfer from the origin bucket or Load Balancer). +- A custom domain and SSL certificate (managed or custom) for each pipeline. + +If you create more pipelines than are included in your plan, or your pipelines' caches egress more data than is included, you will be charged additionally for this. The rates per pipeline/GB of data are indicated on the [pricing](https://www.scaleway.com/en/pricing/network/#edge-services) page. + +Subscriptions are pro-rata, meaning you can cancel your subscription or change your plan at any time, and you will be charged proportionally. + +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-edge-pricing/) page. + +## How to subscribe to Edge Services + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + + +You can subscribe to Edge Services from the Object Storage or Load Balancer dashboards of the Scaleway console. However, the instructions below detail how to describe from the dedicated Edge Services section of the console. Whichever path you use, the same pricing plans and subscription mechanisms apply. Subscribing from the Object Storage or Load Balancer dashboards does **not** limit you to only creating pipelines for that product with your subscription. Subscription plans are scoped to a single Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). + + +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. + +2. Click **Subscribe to Edge Services**. + + Information about available [pricing plans](https://www.scaleway.com/en/pricing/network/#edge-services) is displayed. All pricing plans have a fixed monthly price, and include a certain number of pipelines and a certain amount of cache data (data egressed from all your Edge Services pipelines' caches). Any extra pipelines or cache egress data are charged at the additional rates shown. + +3. Select a plan, and click **Subscribe to Edge Services**. + + Your subscription is created, and you are returned to the Edge Services dashboard, on the **Pipelines** tab. All your Edge Services pipelines will display here. + +## How to change your subscription plan + +You can change your Edge Services subscription plan at any time. Subscriptions are pro-rata: the monthly price will be applied based on the proportion of the month you are subscribed to the plan. + +If you upgrade your plan, any additional charges (for extra pipelines or cache data) that you had already accumulated before the time of upgrade will still stand. + +Find out more about how Edge Service subscription plans and billing works, including scenarios for changing your plan mid-month, on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-edge-pricing/) page. + +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays. + +2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription. + +3. Scroll down to the **Manage your plan subscription** section, and click **Select plan** on the plan you want to switch to. + + A pop-up displays, asking you to confirm that you want to change plans. + +4. Click **change plan** to confirm. + +Your subscription plan is updated, and you are returned to the **Plans** tab of your Edge Services dashboard. \ No newline at end of file diff --git a/network/edge-services/how-to/terminate-edge-services.mdx b/network/edge-services/how-to/terminate-edge-services.mdx new file mode 100644 index 0000000000..9dea44dfbd --- /dev/null +++ b/network/edge-services/how-to/terminate-edge-services.mdx @@ -0,0 +1,39 @@ +--- +meta: + title: How to terminate an Edge Services subscription + description: Find out how to terminate your Scaleway Edge Services subscription whenever you want, at the click of a button. +content: + h1: How to terminate an Edge Services subscription + paragraph: Find out how to terminate your Scaleway Edge Services subscription whenever you want, at the click of a button.ow to choose the best plan for your needs and change your plan at the click of a button. +dates: + validation: 2024-10-15 + posted: 2024-10-15 +tags: object-storage edge-services subscription-plan subscribe billing pricing terminate cancel +categories: + - network +--- + +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It lets you benefit from a powerful caching service to reduce the load on your origin servers and streamline delivery. On top of this, you get a customizable Edge Services endpoint and can set it to a subdomain of your choice, securing it with an SSL/TLS certificate. To use Edge Services, you must subscribe to a monthly plan. + +## How to terminate your Edge Services subscription + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An active [Edge Services subscription](/network/edge-services/how-to/subscribe-edge-services/) +- [Deleted all your Edge Services pipelines](/network/edge-services/how-to/delete-pipeline/) + +You can terminate your Edge Services subscription at any time, as long as you have deleted all your pipelines. You will be charged pro-rata for the month you cancel, based on how much of that month your subscription was active. + +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays. + +2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription. + +3. Scroll down to the **Terminate subscription** section, and click **Terminate subscription**. + + A pop-up displays, asking you to confirm that you want to terminate your subscription. + +4. Type **DELETE** in the box, and click **Terminate** to confirm. + + Your Edge Services subscription is terminated. You can subscribe again at any time. \ No newline at end of file diff --git a/network/edge-services/index.mdx b/network/edge-services/index.mdx index 2ca0b62282..bbb72cca7e 100644 --- a/network/edge-services/index.mdx +++ b/network/edge-services/index.mdx @@ -4,6 +4,13 @@ meta: description: Dive into Scaleway Edge Services with our quickstart guides, how-tos, tutorials and more. --- + + Edge Services for Object Storage and Load Balancers is now in General Availability, and a subscription-based pricing plan applies. Find out more in our [dedicated documentation](/network/edge-services/reference-content/understanding-ga/). + + @@ -21,75 +25,82 @@ Edge Services is an additional feature for Scaleway Load Balancers and Object St - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Created either a [Load Balancer](/network/load-balancer/how-to/create-load-balancer/) or an [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -## How to create an Edge Services pipeline - -The process differs depending on whether you want to create a pipeline for an Object Storage bucket or a Load Balancer. Choose the correct tab for your case below.

- - - - 1. Click **Object Storage** in the **Storage** section of the Scaleway console side menu. The list of your buckets displays. +## How to subscribe to Edge Services - 2. Click the name of the bucket you want to enable Edge Services on. +To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes a fixed number of pipelines, and a certain amount of egress cache data. Any consumption that exceeds the limits of the plan is charged at an additional rate. - 3. Click the **Edge Services** tab. +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page, or follow the steps below to subscribe. - +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. - 4. Click **Enable Edge Services for free**. +2. Click **Subscribe to Edge Services**. Information about available [pricing plans](https://www.scaleway.com/en/pricing/network/#edge-services) is displayed. - A pop-up informs you that your bucket will be exposed via Edge Services and that you can disable Edge Services at any time. Edge Services is free during the beta stage, and you will be notified before it becomes billable. +3. Select a plan, and click **Subscribe to Edge Services**. - 5. Click **Enable Edge Services** to confirm. + Your subscription is created, and you are returned to the Edge Services dashboard, on the **Pipelines** tab. All your Edge Services pipelines will display here. - Edge Services is enabled on your bucket, and a pipeline is automatically created. Various features are now visible on the Edge Services tab, ready to be configured. +## How to create an Edge Services pipeline - +You can create [pipelines](/network/edge-services/concepts/#pipeline) for either Object Storage buckets or Load Balancer origins. - +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. - For more detailed information about correctly enabling Edge Services in relation to bucket visibility, see the [dedicated documentation](/network/edge-services/how-to/create-pipeline-bucket/). You can also find out here how to access your bucket via Edge Services. - - - - 1. Click **Load Balancers** in the **Network** section of the Scaleway console side menu. The list of your Load Balancers displays. +2. Click **Create pipeline**. The pipeline creation wizard displays. - +3. Choose an **origin type**, the type of resource which Edge Services will connect to to fetch content to serve. This can either be **Load Balancer** or **Object Storage**. - 2. Click the **Edge Services** tab. + Follow the steps below depending on whether you are creating a Load Balancer or Object Storage pipeline
- 3. Click **create Edge Services pipeline**. The pipeline creation wizard displays. + + - + - 4. Configure the [origin](/network/edge-services/concepts/#origin) for this pipeline: + 4. Configure the [origin](/network/edge-services/concepts/#origin) for this pipeline: + - Select **Load Balancer** as the origin type. - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content. - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend. - For Kubernetes Load Balancers, see our [dedicated documentation](/network/edge-services/how-to/create-pipeline-lb/#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend. + For Kubernetes Load Balancers, see our [dedicated documentation](#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend. - 5. Define the protocol and origin host for this pipeline: + 5. Define the protocol and origin host for this pipeline: - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup. - Optionally, enter an [origin host](/network/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. - 6. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place. + 6. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place. - Edge Services for Load Balancer is free during Public Beta. You will be notified before the service leaves beta and becomes billable. + 7. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**. - 7. Click **Create Edge Services pipeline** to finish. + + + + + + 4. Select **Object Storage** as the origin type. - Your pipeline is created and you are taken to its **Overview** page. The endpoint displays from which you can access your Load Balancer origin via Edge Services, e.g. `https://pipeline-id.edge.scw.cloud`. + 5. Choose the bucket you want this pipeline to serve content for, under **Origin bucket**. + + 6. Enter a name for the pipeline, or leave the randomly generated name in place. + + 7. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**. + + + Your bucket's [visibility](/storage/object/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/storage/object/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. + - + + + 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. ## How to configure a custom domain If you already own a domain, you can customize an Edge Services pipeline endpoint with a subdomain of your choice, e.g. `subdomain.mydomain.com`. This means you can access your Object Storage bucket or Load Balancer origin through Edge Services via your own subdomain rather than the standardized Edge Services endpoint. -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to customize: +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 customize: @@ -155,7 +166,7 @@ The cache feature allows you to cache your origin's content with Edge Services. You can disable and enable caching at will, as well as control the lifetime of an object in the cache. You can also purge your entire cache, or specific objects within it. A log is displayed to help you track your purge events. -1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin for which you want to enable caching: +1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline for which you want to enable caching: @@ -177,57 +188,38 @@ For information on purging your cache, see our [dedicated documentation](/networ ## How to delete an Edge Services pipeline -You can delete an Edge Services pipeline at any time. Follow the steps below, depending on whether your pipeline is towards an Object Storage bucket origin or a Load Balancer origin.

+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The **Pipelines** tab displays. - - - 1. Click **Object Storage** in the **Storage** section of the Scaleway console side menu. The list of your buckets displays. +2. Click the pipeline that you want to delete. You are taken to the pipeline's **Overview** page - 2. Click the name of the bucket you want to disable Edge Services for. +4. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**. - 3. Click the **Edge Services** tab. - - - - 4. In the **Disable Edge Services** panel at the bottom of the screen, click **Disable Edge Services**. + A pop-up displays, asking you to confirm that you want to delete the pipeline. + - The Load Balancer/Object Storage bucket will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint. + - Any files stored in the Edge Services cache will be removed. + + + Remember to: + - Delete any CNAME records created for this pipeline from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you. + - Delete any SSL/TLS certificates you imported into Secret Manager for this pipeline (if no longer required elsewhere), so that you are no longer billed for them. If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you. + - A pop-up displays, informing you that the bucket will be removed from Edge Services. - - The bucket will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint. - - Any files stored in the Edge Services cache will be removed. - - - Remember to: - - Delete your CNAME record from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you. - - Delete any SSL/TLS certificates you imported into Secret Manager (if no longer required elsewhere, so that you are no longer billed for it). If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you. - +5. Click **Confirm**. -5. Click **Disable Edge Services**. + The Edge Services pipeline is deleted. You can create a new pipeline for this origin at any time, but you will need to reconfigure your custom domain, and the cache will initially be empty. - Edge Services is disabled and the pipeline for this bucket is deleted. You can enable it again at any time to create a new pipeline, but you will need to reconfigure your custom domain, and the cache will initially be empty. - - - 1. Click **Load Balancers** in the **Network** section of the Scaleway console side menu. The list of your Load Balancers displays. +## How to terminate an Edge Services subscription - 2. Click the **Edge Services** tab. A list of your pipelines displays. +You can terminate your Edge Services subscription at any time, as long as you have deleted all your pipelines. You will be charged pro-rata for the month you cancel, based on how many days in that month your subscription was active. - 3. Click the pipeline you want to delete. The Edge Services dashboard for that pipeline displays. +1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays. - +2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription. - 4. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**. +3. Scroll down to the **Terminate subscription** section, and click **Terminate subscription**. - A pop-up displays, informing you that the pipeline will be deleted - - The Load Balancer origin will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint. - - Any files stored in the Edge Services cache for this pipeline will be removed. - - - If you set up a customized domain for your Edge Services endpoint, remember to: - - Delete your CNAME record from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you. - - Delete any SSL/TLS certificates you imported into Secret Manager (if no longer required elsewhere, so that you are no longer billed for it). If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you. - + A pop-up displays, asking you to confirm that you want to terminate your subscription. - 5. Click **Confirm*. +4. Type **DELETE** in the box, and click **Terminate** to confirm. - The Edge Services pipeline for this Load Balancer origin is deleted. You create a new pipeline at any time, but you will need to reconfigure any custom domains, and the cache will initially be empty. - - \ No newline at end of file + Your Edge Services subscription is terminated. You can subscribe again at any time. \ No newline at end of file diff --git a/network/edge-services/reference-content/assets/scaleway-current-conso.webp b/network/edge-services/reference-content/assets/scaleway-current-conso.webp new file mode 100644 index 0000000000..4ef75bb663 Binary files /dev/null and b/network/edge-services/reference-content/assets/scaleway-current-conso.webp differ diff --git a/network/edge-services/reference-content/assets/scaleway-pipelines-limit.webp b/network/edge-services/reference-content/assets/scaleway-pipelines-limit.webp new file mode 100644 index 0000000000..67f0561d69 Binary files /dev/null and b/network/edge-services/reference-content/assets/scaleway-pipelines-limit.webp differ diff --git a/network/edge-services/reference-content/ssl-tls-certificate.mdx b/network/edge-services/reference-content/ssl-tls-certificate.mdx index 611338c16c..aaaaa9fdfd 100644 --- a/network/edge-services/reference-content/ssl-tls-certificate.mdx +++ b/network/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 enable Edge Services, initially your [origin's](/network/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](/network/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. However, if you choose to [customize your Edge Services endpoint with your own subdomain](/network/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). diff --git a/network/edge-services/reference-content/understanding-ga.mdx b/network/edge-services/reference-content/understanding-ga.mdx index 47247764cc..5844cfbccf 100644 --- a/network/edge-services/reference-content/understanding-ga.mdx +++ b/network/edge-services/reference-content/understanding-ga.mdx @@ -1,28 +1,29 @@ --- meta: title: Understanding Edge Services General Availability - description: Scaleway Edge Services is leaving Public Beta and going into General Availability. This page answers all your questions about the timeline, pricing and any action you need to take. + description: Scaleway Edge Services has left Public Beta and gone into General Availability. This page answers all your questions about the timeline, pricing and any action you need to take. content: h1: Understanding Edge Services General Availability - paragraph: Scaleway Edge Services is leaving Public Beta and going into General Availability. This page answers all your questions about the timeline, pricing and any action you need to take. + paragraph: Scaleway Edge Services has left Public Beta and gone into General Availability. This page answers all your questions about the timeline, pricing and any action you need to take. tags: edge-services public-beta general-availability pricing billing ga dates: - validation: 2024-09-27 + validation: 2024-10-16 + creation: 2024-09-27 categories: - network --- -Scaleway Edge Services is leaving Public Beta and going into General Availability. Read on to find out more about when this will happen, what it means for current users, and how the product will be billed. +Scaleway Edge Services has left Public Beta and gone into General Availability. Read on to find out more about this transition. ## Edge Services Public Beta -Edge Services for Object Storage and Load Balancer is currently in Public Beta. This means that the product is ready to be tested by customers, but some features may be missing, and usage is intended for test environments rather than production. Edge Services is free to use during Public Beta, and is not billed. +Edge Services for Object Storage and Load Balancer was in Public Beta until November 1 2024. This meant that the product was ready to be tested by customers, but some features may have been missing, and usage was intended for test environments rather than production. Edge Services was free to use during Public Beta, and was not billed. ## Edge Services General Availability -From **November 1st 2024** Edge Services will transition to General Availability, for both Object Storage and Load Balancer usage. This means that: -- We consider that the product is ready for production environments. -- The product will no longer be free to use, and will be billed. +From **November 1st 2024** Edge Services went into General Availability, for both Object Storage and Load Balancer usage. This means that: +- We considered that the product was ready for production environments. +- The product was no longer be free to use, and is now billed. ## Edge Services pricing @@ -30,34 +31,29 @@ From **November 1st 2024** Edge Services will transition to General Availability Check out the [Edge Services pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for full pricing details. -Once in General Availability, Edge Services will be billed via **subscription**. Three different subscription plans will be available, each including different amounts of monthly usage for **cache size** and **number of pipelines**. If your consumption of Edge Services in a given month exceeds the cache size and number of pipelines included in your subscription, you will be billed for this extra usage on top of your plan. +Edge Services is billed via **subscription**. Three different subscription plans are available, each including different amounts of monthly usage for **cache size** and **number of pipelines**. If your consumption of Edge Services in a given month exceeds the cache size and number of pipelines included in your subscription, you are billed for this extra usage on top of your plan. -An Edge Services pipeline consists of an origin for which Edge Services requests and caches content, and an endpoint from which this content is served via Edge Services. In the case of Object Storage, a pipeline corresponds to a bucket Edge Services is enabled on. If Edge Services is enabled on three different buckets, this equals three pipelines. In the case of Load Balancer, pipelines are already an explicit concept in the console. +An Edge Services pipeline consists of an origin for which Edge Services requests and caches content, and an endpoint from which this content is served via Edge Services. In the case of Object Storage during Public Beta, a pipeline corresponded to a bucket Edge Services was enabled on. If Edge Services was enabled on three different buckets, this equaled three pipelines. In the case of Load Balancer, pipelines were already an explicit concept in the console. -At the start of October 2024, current Edge Services users will receive an email with full details of the three subscription plans. +At the start of October 2024, current Edge Services users received an email with full details of the three subscription plans. Pricing plan details can also be viewed on the [Scaleway pricing page](https://www.scaleway.com/en/pricing/network/). ## Transitioning from free to paid use -At the end of October 2024, we will automatically select the most cost-effective subscription plan for each existing Edge Services user, based on their current usage. When billing starts on the 1st of November 2024, you will therefore see in the [Scaleway console](https://console.scaleway.com/) that you are subscribed to the plan we have selected for you. +At the end of October 2024, we automatically selected the most cost-effective subscription plan for each existing Edge Services user, based on their usage. When billing started on the 1st of November 2024, users therefore saw in the [Scaleway console](https://console.scaleway.com/) that they were subscribed to the plan we had selected for them. Billing for Edge Services is pro-rata, and you can cancel or change your subscription plan at any time. -If you do not wish to be billed for Edge Services, you must disable it on all your buckets, and delete any Load Balancer pipelines you had created **before November 1st 2024**. See the documentation on how to [disable or delete Edge Services](/network/edge-services/how-to/delete-pipeline/). +If you did not wish to be billed for Edge Services, you were warned that you must disable it on all your buckets, and delete any Load Balancer pipelines you had created **before November 1st 2024**. -### How can I estimate how much I'll be charged? +### Estimating your billing and understanding pricing -To estimate your billing for Edge Services, calculate: - -- **How many Edge Services pipelines you are using** (see tip [above](#edge-services-pricing)). -- **How much cache you are using** (this information can be found via [Scaleway Cockpit](/network/edge-services/how-to/monitor-cockpit/)) - -Cross reference the above information with the details given on the [pricing page](https://www.scaleway.com/en/pricing/network/). Remember, we'll automatically transfer you to the most cost-effective plan for your usage, and any extra usage above that plan will be billed additionally according to the rates shown. +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-edge-pricing/) page. ## Further support diff --git a/network/edge-services/reference-content/understanding-pricing.mdx b/network/edge-services/reference-content/understanding-pricing.mdx new file mode 100644 index 0000000000..fb8cc0c9d8 --- /dev/null +++ b/network/edge-services/reference-content/understanding-pricing.mdx @@ -0,0 +1,164 @@ +--- +meta: + title: Understanding Edge Services pricing + description: Find answers to all your questions about how pricing for Edge Services works, how to calculate your billing, and the different subscription plans available. Different scenarios are presented, with explanations of how you would be billed in each one. +content: + h1: Understanding Edge Services pricing + paragraph: Find answers to all your questions about how pricing for Edge Services works, how to calculate your billing, and the different subscription plans available. Different scenarios are presented, with explanations of how you would be billed in each one +tags: edge-services general-availability pricing billing subscription-plan pro-rata +dates: + validation: 2024-10-16 + creation: 2024-10-16 +categories: + - network +--- + +Find out everything you need to know about how Edge Services is billed in this document. + +## Edge Services billing basics + +Edge Services billing is based on [monthly subscription plans](https://www.scaleway.com/en/pricing/network/#edge-services). Three plans are available, with different prices and consumption limits: + +- **Starter** +- **Professional** +- **Advanced** + +When you subscribe to a plan, you are billed its flat monthly fee, which allows you to: + +- Run a fixed maximum number of Edge Services [pipelines](/network/edge-services/concepts/#pipeline) for the month. They can be for Object Storage or Load Balancer origins, or a mixture of both. +- Egress a fixed maximum amount of data from all your pipelines' [caches](/network/edge-services/concepts/#cache). + +If you subscribe to a plan, and exceed its monthly limits for pipelines or cache data, you will incur additional charges that month. + +Essentially, your Edge Services monthly bill is made up of your **monthly subscription plan price** + **any additional pipeline charges incurred** + **any additional cache charges incurred**. + +For full details of the price and limits of each plan, refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services). Subscription plans are scoped to a single Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). + +## Keeping track of your Edge Services consumption + +You can check the number of pipelines you have at any one time in the **Pipelines** tab of the Edge Services dashboard in the Scaleway console. [Scaleway Cockpit](/network/edge-services/how-to/monitor-cockpit/) can be used to monitor the data egressing from your Edge Services caches. + +## Included usage vs additional charges + +Additional charges apply when you either: + +- Have more pipelines in existence (at any given time) than the limit of your monthly plan +- Egress more data from all your pipelines' caches combined, than the limit of your monthly plan + +Read on to understand more about how additional charges are applied. + +### Additional pipeline charges + +Additional pipeline charges are based on a monthly fee per additional pipeline. This monthly fee is applied pro-rata based on how long you had additional pipelines in existence during the calendar month. + +For example: + + +The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information. + + +- For the entire month of November, you are subscribed to the **Starter** plan, which has a limit of 1 pipeline. +- You start the month with 1 pipeline (A) in existence, which runs until the end of the month. +- On November 5 you create a second pipeline (B), which you later delete on November 10. +- On November 15 you create another pipeline (C), which runs until the end of the month. + +There are 30 days in the month of November. +- Pipeline A falls within the limit of your Starter plan, so is not billed. +- Pipeline B was an additional pipeline which existed for 5 days +- Pipeline C is an additional pipeline which existed for 15 days + +Your November Edge Services billing, in terms of additional pipeline charges, is therefore calculated as follows: + +`({Monthly flat fee for an additional pipeline} / 30 days) * 5 days` + `({Monthly flat fee for an additional pipeline} / 30 days) * 15 days`
+e.g. `(4 / 30) * 5 = €0.67` + `(4 / 30) * 15 = €2` = `€2.67` + +### Additional cache charges + +Cache consumption is based on the volume of data egressed from all your Edge Services pipelines' caches combined, in a given month. The transfer of data from the origin bucket or Load Balancer into the cache, or directly from the origin to a user, does not count towards the limit of your plan, and does not incur any additional charges. + +For every extra GB of data that is egressed from your Edge Services caches in a month, **beyond** the limit of your monthly plan, an additional charge applies. + +For example: + + +The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information. + + +- For the entire month of November, you are subscribed to the **Starter** plan, which has a limit of 100 GB of cache data. +- Over the course of the month, a total of 300 GB of data is egressed from your Edge Services caches. + +You consumed 200 GB of cache data that was not included within your monthly plan. Your November Edge Services billing, in terms of additional cache charges, is therefore calculated as follows: + +`{Fee per GB of additional cache} * 200 GB`
+e.g. `0.0135 * 200 = €2.70` + +## Changing your subscription plan + +You can upgrade or downgrade your subscription plan at any time. Read on to understand how changing plan mid-month affects your billing. + +### Monthly plan price + +You will be billed pro-rata for the old and new monthly plan prices, based on how long you were subscribed to each plan during the billing month. + +For example: + + +The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information. + + +- From November 1-10 you are subscribed to the **Starter** plan. +- On November 11, you switch to the **Professional** plan. +- You remain subscribed to the **Professional** plan for the rest of the month (ending November 30) + +There are 30 days in the month of November, and you spent 10 of them subscribed to the Starter plan, and 20 of them subscribed to the Professional plan. Your November Edge Services billing, in terms of the monthly plan price, is therefore calculated as follows: + +`({Monthly price for Starter plan} / 30 days) * 10 days` + `({Monthly price for Professional plan} / 30 days) * 20 days`
+e.g. `(0.99 / 30) * 10 = 0.33` + `(12.99 / 30) * 20 = 8.66 ` = `€8.99` + +### Pipeline charges + +Any additional pipeline charges accumulated when you had more pipelines in existence than the previous plan's limit will remain on your monthly bill. From the moment you change your plan, you can consume pipelines up to the new plan's monthly limit without being charged. + +Additional pipeline charges are based on a monthly fee per additional pipeline. This monthly fee is applied pro-rata based on how long you had additional pipelines in existence during the calendar month. + +For example: + + +The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information. + + +- From November 1-10 you are subscribed to the **Starter** plan, which has a limit of 1 pipeline. +- You have 2 pipelines in existence during these 10 days. +- On November 11, you upgrade to the **Professional** plan, which has a limit of 10 pipelines. +- You create 8 more pipelines, which you keep for the rest of the month: you finish the month with 10 pipelines. + +There are 30 days in the month of November. For 10 of these days, you had an extra pipeline beyond the limits of your **Starter** plan. After upgrading, and even after creating more pipelines, you were within the pipeline limits of your new plan. Your November Edge Services billing, in terms of the additional pipeline charges, is therefore calculated as follows: + +`({Monthly flat fee for an additional pipeline} / 30 days) * 10 days`
+e.g. `(4 / 30) * 10 = €1.33` + +### Cache charges + +Any additional cache charges accumulated when you exceeded your previous plan's cache limit will remain on your monthly bill. From the moment you change your plan, your cache consumption resets to 0. During the rest of the month, you can consume cache up to the new plan's limit without being charged. + + +- If you **downgrade** your plan, all the data egressed from the cache within the hour of changing plans will count towards the cache consumption of the new plan. +- If you **upgrade** your plan, all the data egressed from the cache within the hour of changing plans will count towards the cache consumption of the old plan. + + +For example: + + +The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information. + + +- From November 1-10 you are subscribed to the **Starter** plan, which has a cache limit of 100 GB. +- From November 1-10 you consume 300 GB of cache data. +- On November 11, you upgrade to the **Professional** plan, which has a limit of 1 TB of cache data. Your cache usage resets to 0. +- Between November 11 and the end of the month, you consume 1 TB of cache data. + +You consumed 200 GB of cache data that was not included within your monthly Starter plan, between November 1-10. For the rest of the month, you were within the limits of your new Professional plan. Your November Edge Services billing, in terms of the additional cache charges, is therefore calculated as follows: + +`{Fee per GB of additional cache} * 200 GB`
+e.g. `0.0135 * 200 = €2.70` + diff --git a/network/load-balancer/how-to/assets/scaleway-create-es-pipeline-lb.webp b/network/load-balancer/how-to/assets/scaleway-create-es-pipeline-lb.webp new file mode 100644 index 0000000000..75d89eb2b6 Binary files /dev/null and b/network/load-balancer/how-to/assets/scaleway-create-es-pipeline-lb.webp differ diff --git a/network/load-balancer/how-to/use-edge-services.mdx b/network/load-balancer/how-to/use-edge-services.mdx new file mode 100644 index 0000000000..2880c4cf71 --- /dev/null +++ b/network/load-balancer/how-to/use-edge-services.mdx @@ -0,0 +1,57 @@ +--- +meta: + title: How to create an Edge Services pipeline for a Load Balancer + description: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery. +content: + h1: How to create an Edge Services pipeline for a Load Balancer + paragraph: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery. +dates: + validation: 2024-10-15 + posted: 2024-10-15 +tags: load-balancer edge-services cdn network cache domain https +categories: + - network +--- + +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. + + + +Read on to learn how to create an Edge Services pipeline for your Load Balancer origin. + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Load Balancer](/storage/object/how-to/create-a-bucket/) + +## How to subscribe to Edge Services + +To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan lets you create a certain number of pipelines and consume a certain amount of cache data. + +Find out more about pricing plans and how to subscribe to Edge Services in our [dedicated documentation](/network/edge-services/how-to/subscribe-edge-services/). + +## How to create an Edge Services pipeline for Load Balancer + + +You can create an Edge Services pipeline from the **Edge Services** section of the console, however, in this documentation, we describe how to initiate pipeline creation directly from the **Load Balancers** dashboard. + + +1. Click **Load Balancers** in the **Network** section of the Scaleway console side menu. The list of your Load Balancers displays. + +2. Click the **Edge Services** tab. + +3. Click **Create Edge Services pipeline**. The pipeline creation wizard displays. + + + +4. [Follow step 3 onwards](/network/edge-services/how-to/create-pipeline-lb/#how-to-create-an-edge-services-pipeline-for-load-balancer) in our dedicated Edge Services documentation to finish creating your pipeline. + +## How to configure your pipeline + +See the dedicated Edge Services section of the documentation for help with: + +- [Customizing your Edge Services endpoint](/network/edge-services/how-to/configure-custom-domain/) +- [Configuring your Edge Services cache](/network/edge-services/how-to/configure-cache/) + +To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/network/edge-services/) page. \ No newline at end of file diff --git a/network/edge-services/how-to/assets/scaleway-edge-services-dashboard.webp b/storage/object/how-to/assets/scaleway-edge-services-dashboard.webp similarity index 100% rename from network/edge-services/how-to/assets/scaleway-edge-services-dashboard.webp rename to storage/object/how-to/assets/scaleway-edge-services-dashboard.webp diff --git a/storage/object/how-to/assets/scaleway-edge-services-os-splash.webp b/storage/object/how-to/assets/scaleway-edge-services-os-splash.webp new file mode 100644 index 0000000000..dfbf2d1866 Binary files /dev/null and b/storage/object/how-to/assets/scaleway-edge-services-os-splash.webp differ diff --git a/network/edge-services/how-to/assets/scaleway-edge-services-select-bucket.webp b/storage/object/how-to/assets/scaleway-edge-services-select-bucket.webp similarity index 100% rename from network/edge-services/how-to/assets/scaleway-edge-services-select-bucket.webp rename to storage/object/how-to/assets/scaleway-edge-services-select-bucket.webp diff --git a/storage/object/how-to/get-started-edge-services.mdx b/storage/object/how-to/get-started-edge-services.mdx index e1ff888c32..c0df717b8b 100644 --- a/storage/object/how-to/get-started-edge-services.mdx +++ b/storage/object/how-to/get-started-edge-services.mdx @@ -1,20 +1,77 @@ --- meta: - title: How to get started with Edge Services - description: Introduction to getting started with Scaleway Edge Services. + title: How to set up an Edge Services pipeline for an Object Storage bucket + description: This page explains how to configure an Edge Services pipeline for a Scaleway Object Storage bucket. Set up your own custom domain to point to your bucket, and enable a caching service for faster and more efficient delivery. content: - h1: How to get started with Edge Services - paragraph: Introduction to getting started with Scaleway Edge Services. + h1: How to set up an Edge Services pipeline for an Object Storage bucket + paragraph: This page explains how to configure an Edge Services pipeline for a Scaleway Object Storage bucket. Set up your own custom domain to point to your bucket, and enable a caching service for faster and more efficient delivery. tags: object storage edge services edge-services cdn content delivery network cache domain certificate custom-domain https dates: - - validation: 2024-09-25 + validation: 2024-10-15 posted: 2023-09-14 categories: - storage - object-storage --- -Edge Services is an additional feature for Scaleway Object Storage buckets and Load Balancers, currently available in [Public Beta](https://www.scaleway.com/en/betas/). +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. Creating an Edge Services pipeline towards your Object Storage bucket brings you a number of possible benefits: + + + +Read on to learn how to create an Edge Services pipeline for your Object Storage bucket. + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) + +## How to subscribe to Edge Services + +To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan lets you create a certain number of pipelines and consume a certain amount of cache data. + +Find out more about pricing plans and how to subscribe to Edge Services in our [dedicated documentation](/network/edge-services/how-to/subscribe-edge-services/). + +## How to create an Edge Services pipeline + +Once you have subscribed to Edge Services, you are ready to create a pipeline. Follow the steps below. + + +You can create an Edge Services pipeline from the **Edge Services** section of the console, however, in this documentation, we describe how to create a pipeline directly from your bucket's dashboard in the **Objet Storage** section. + + +1. Click **Object Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com/) side menu. + +2. Click the name of the bucket you want to create an Edge Services pipeline for. + + +3. Click the **Edge Services** tab. + + + +4. Click **Create pipeline**. + + A pop-up asks you to confirm that you want to create a pipeline to expose the bucket via Edge Services. + +5. Click **Create pipeline** to confirm. + + Edge Services is enabled on your bucket, and a pipeline is automatically created. Various features are now visible on the Edge Services tab, ready to be configured. + + + + Your bucket's [visibility](/storage/object/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/storage/object/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. + + + +## How to access your bucket via Edge Services + +Once you have created an Edge Services for your bucket, you can access your bucket and its content via its original Object Storage endpoint, and via its new customizable Edge Storage endpoint. Get full details in the [Edge Services](/network/edge-services/how-to/create-pipeline-bucket/#how-to-access-your-bucket-via-edge-services) section of the documentation. + +## How to configure your pipeline + +See the dedicated Edge Services section of the documentation for help with: + +- [Customizing your Edge Services endpoint](/network/edge-services/how-to/configure-custom-domain/) +- [Configuring your Edge Services cache](/network/edge-services/how-to/configure-cache/) -Documentation has moved to the new dedicated [Edge Services](/network/edge-services/) section. +To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/network/edge-services/) page.