diff --git a/pages/apple-silicon/how-to/adjust-available-bandwidth.mdx b/pages/apple-silicon/how-to/adjust-available-bandwidth.mdx index ae025acdb4..d87dc32004 100644 --- a/pages/apple-silicon/how-to/adjust-available-bandwidth.mdx +++ b/pages/apple-silicon/how-to/adjust-available-bandwidth.mdx @@ -10,7 +10,7 @@ categories: - bare-metal --- -Every Mac mini comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 10Gbps, all with unlimited traffic. +Every Mac mini comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 10 Gbps, all with unlimited traffic. diff --git a/pages/apple-silicon/how-to/use-private-networks.mdx b/pages/apple-silicon/how-to/use-private-networks.mdx index bb4cd88e4a..08696ba4bc 100644 --- a/pages/apple-silicon/how-to/use-private-networks.mdx +++ b/pages/apple-silicon/how-to/use-private-networks.mdx @@ -1,6 +1,6 @@ --- title: How to use Private Networks with your Mac mini -description: Learn how to get the most from the Private Networks 1Gbps feature for your Mac mini. Find out how to activate the feature, attach your Mac mini to Private Networks, and enable secure communication with your other Scaleway resources. +description: Learn how to get the most from the Private Networks 1 Gbps feature for your Mac mini. Find out how to activate the feature, attach your Mac mini to Private Networks, and enable secure communication with your other Scaleway resources. tags: mac-mini mac-mini apple-silicon private-network vpc dates: validation: 2025-08-05 @@ -70,7 +70,7 @@ Once you have attached the resource, some manual configuration of the network in You must configure the virtual network interface on each Mac mini you have attached to a Private Network. Traffic from the public internet and traffic from a Private Network will pass through the same network interface of the Mac mini. We must therefore separate the traffic by adding a VLAN interface. -To configure the interface, you must connect to your Mac mini, either via SSH or the remote desktop and carry out the instructions given. +To configure the interface, you must connect to your Mac mini, either via SSH or the remote desktop, and carry out the instructions given. ### Via SSH and networksetup diff --git a/pages/elastic-metal/faq.mdx b/pages/elastic-metal/faq.mdx index a7874f7790..c2dd888f89 100644 --- a/pages/elastic-metal/faq.mdx +++ b/pages/elastic-metal/faq.mdx @@ -3,7 +3,7 @@ title: Elastic Metal FAQ description: Explore Scaleway Elastic Metal servers, pioneering 100% cloud bare metal solutions. Learn about billing, server ranges, installation guides, and more. hero: assets/elasticmetal.webp dates: - validation: 2025-09-23 + validation: 2025-09-24 productIcon: ElasticMetalProductIcon --- @@ -42,6 +42,10 @@ Elastic Metal servers are available in the following regions and Availability Zo * Paris, France (`PAR-1` and `PAR-2`) * Warsaw, Poland (`WAW-2` and `WAW-3`) +### Do you provide an IPv6 address by default with Elastic Metal? + +Yes, Elastic Metal servers are delivered with an IPv6 address (/128) pre-configured. + ## Pricing and billing ### How am I billed for Elastic Metal servers? @@ -75,10 +79,6 @@ It is not possible to get a cash refund of the engagement fees. ## Specifications -### How long does it take to boot an Elastic Metal server? - -An Elastic Metal server is delivered to your account within a few minutes. You can then launch the server installation, which can take up to one hour. - ### Which OSEs can be installed on Elastic Metal servers? We provide a range of Linux and Windows Server distributions for automatic installation from the Scaleway console. @@ -88,7 +88,7 @@ We provide a range of Linux and Windows Server distributions for automatic insta Yes, you have the flexibility to modify the bandwidth available for your Elastic Metal server according to your requirements. Each Elastic Metal dedicated server comes with an allocated bandwidth allowance. However, you can easily increase or decrease this bandwidth through your Scaleway console at any time. -Scaleway offers high-performance bandwidth options of up to 25Gbps per server, all of which include unlimited traffic. +Scaleway offers high-performance bandwidth options of up to 25 Gbps per server, all of which include unlimited traffic. For step-by-step instructions on how to modify the available bandwidth for your Elastic Metal server, refer to our documentation on [how to modify the available bandwidth for an Elastic Metal server](/elastic-metal/how-to/adjust-available-bandwidth/). @@ -97,6 +97,10 @@ For step-by-step instructions on how to modify the available bandwidth for your ## Usage and management +### How long does it take to boot an Elastic Metal server? + +An Elastic Metal server is delivered to your account within a few minutes. You can then launch the server installation, which can take up to one hour. + ### How can I reinstall an Elastic Metal server? You can reinstall an Elastic Metal server with a few clicks at any time, [directly from your Scaleway console](/elastic-metal/how-to/install-server/). @@ -139,10 +143,6 @@ Each failover IP consists of a `/64` IPv6 subnet (18,446,744,073,709,551,616 IPv When you configure the reverse DNS of a failover IPv6, the configuration is applied only to the first IP of each block (`XXXX:0`). -### Do you provide an IPv6 address by default with Elastic Metal? - -Yes, Elastic Metal servers are delivered with an IPv6 address (/128) pre-configured. - ### Can I attach Block Storage volumes to my Elastic Metal server? Elastic Metal is not currently compatible with Block Storage, but this functionality is planned for the future. diff --git a/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx b/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx index cdf561a8ce..8cfda2b28e 100644 --- a/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx +++ b/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -Every Elastic Metal server comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 25Gbps, all with unlimited traffic. +Every Elastic Metal server comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 25 Gbps, all with unlimited traffic. diff --git a/pages/interlink/reference-content/overview.mdx b/pages/interlink/reference-content/overview.mdx index 60049ef3af..d07fae788b 100644 --- a/pages/interlink/reference-content/overview.mdx +++ b/pages/interlink/reference-content/overview.mdx @@ -28,7 +28,7 @@ Scaleway plans to offer two types of InterLink, though currently only the **host A hosted InterLink is provisioned via a [partner](/interlink/concepts/#partner). Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink. -By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100Mbps - 25Gbps) across the InterLink. +By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100 Mbps - 25 Gbps) across the InterLink. #### How to choose a partner @@ -57,11 +57,11 @@ While each InterLink can only be attached to a single Scaleway VPC, it is possib ## Routing across an InterLink -InterLink uses [**B**order **G**ateway **P**rotocol](/interlink/concepts/#border-gateway-protocol-bgp) to exchange routing information between the customer’s network and the Scaleway VPC. +InterLink uses [**B**order **G**ateway **P**rotocol](/interlink/concepts/#border-gateway-protocol-bgp) to exchange routing information between the customer’s network and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes. This facilitates efficient traffic flow across the link towards these destinations, providing that [routing policies](#routing-policies) and [route propagation](#route-propagation) have been correctly set up. -In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions. +In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions. When both BGP sessions are up, the InterLink has `Active` status. If one BGP session is up, and the other down, the status moves to `Limited Connectivity`. If both BGP sessions are down, the status is marked as `Down`. See the page on [InterLink statuses](/interlink/reference-content/statuses) for full information. @@ -71,4 +71,4 @@ By default, **all route announcements from both sides are blocked** by InterLink ### Route propagation -Even after attaching a routing policy, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/interlink/reference-content/configuring/) page for more information on route propagation. \ No newline at end of file +Even after attaching a routing policy, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism, enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/interlink/reference-content/configuring/) page for more information on route propagation. \ No newline at end of file diff --git a/pages/public-gateways/faq.mdx b/pages/public-gateways/faq.mdx index 24fad77c05..cf45395fc5 100644 --- a/pages/public-gateways/faq.mdx +++ b/pages/public-gateways/faq.mdx @@ -2,26 +2,21 @@ title: Public Gateways FAQ description: Discover Scaleway Public Gateways and get answers to all your questions about IP addressing, bandwidth, regionalization and more. dates: - validation: 2025-05-05 + validation: 2025-09-24 productIcon: PublicGatewayProductIcon --- -## What is a Public Gateway? +## Overview + +### What is a Public Gateway? Public Gateways sit at the border of Private Networks. They provide services to deal with traffic entering and exiting the network (NAT), and SSH bastion. A Public Gateway can be attached to up to 8 Private Networks, and up to 50 Public Gateways are supported per [Organization](/organizations-and-projects/concepts/#organization). The Public Gateway can be configured through the console or the [API](https://www.scaleway.com/en/developers/api/public-gateway/). -## Does the Public Gateway require a public IPv4 address? - -No. A public IPv4 address (aka. flexible IP) must be assigned to the Public Gateway at creation time, but you can detach it and delete it afterward if you do not require it to be publically accessible. +## Offering and availability -## Can my Instances and other resources access the internet via a Public Gateway without a public IP address? - -Yes. The Public Gateway can advertise itself as the [default route to the internet](/public-gateways/concepts/#default-route) over the Private Network it is attached to, so that Instances and other resources can access the internet via the gateway. Resources attached to other Private Networks than the gateway's network in the VPC can [opt in](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) to receive its default route advertisement. -Moreover, the Public Gateway supports [static NAT](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) (aka. port forwarding), so that ingress traffic from the public internet can reach Instances on the Private Network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the VPC. - -## What happened to static leases (DHCP reservations) when DHCP moved from the Public Gateway to Private Networks? +### What happened to static leases (DHCP reservations) when DHCP moved from the Public Gateway to Private Networks? On 12 July 2023, DHCP functionality moved from Public Gateways to Private Networks. See our [dedicated migration documentation](/vpc/reference-content/vpc-migration/) for full details. @@ -29,15 +24,15 @@ Pre-existing static leases created via the Public Gateway were fully migrated an Read our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) to learn how to put your gateway into IPAM-mode and replicate static DHCP reservation functionality with Scaleway IPAM. -## Why is my Public Gateway labeled as Legacy? +### Why is my Public Gateway labeled as Legacy? **Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatibility with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources Your gateway is a legacy gateway if you created it prior to 17 October 2023 and you never recreated it in IPAM mode. Legacy gateways are now deprecated, as they are incompatible with v2 of the Public Gateways API. Such gateways must be [moved to IPAM mode](/public-gateways/reference-content/understanding-v2/) before October 2025 to ensure ongoing functionality. -## I received a message about v1 of the Public Gateways API being deprecated, do I need to take action? +### I received a message about v1 of the Public Gateways API being deprecated, do I need to take action? -The Public Gateways API v1 is now deprecated, and will be removed on 1 October 2025. Only IPAM-mode gateways will be compatible with the new version of the API (v2). Whether or not you need to take action depends on the following two points: +The Public Gateways API v1 is now deprecated, and will be removed on 1 November 2025. Only IPAM-mode gateways will be compatible with the new version of the API (v2). Whether or not you need to take action depends on the following two points: - Consider whether you manage your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts: @@ -53,16 +48,33 @@ The Public Gateways API v1 is now deprecated, and will be removed on 1 October 2 See our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) for full details. -## Do I need a Public Gateway for each Availability Zone (AZ)? +## Specifications + +### Does the Public Gateway require a public IPv4 address? + +No. A public IPv4 address (also known as flexible IP) must be assigned to the Public Gateway at creation time, but you can detach it and delete it afterward if you do not need it to be publicly accessible. + +### Do I need a Public Gateway for each Availability Zone (AZ)? VPC and Private Networks are both [regional](/public-gateways/concepts/#region-and-availability-zone), meaning they span all AZs across a given region. Even though Public Gateways are zoned and not regional, one Public Gateway attached to a regional Private Network is functionally enough, and will cover the whole region. That is to say a Public Gateway created in PAR-1 can serve Instances in PAR-2 and PAR-3, as long as they are all attached to the same PAR-region Private Network. -## How can I achieve truly High Availability (HA) networking when the Public Gateway is a zoned resource? +## Access and security + +### Can my Instances and other resources access the internet via a Public Gateway without a public IP address? + +Yes. The Public Gateway can advertise itself as the [default route to the internet](/public-gateways/concepts/#default-route) over the Private Network it is attached to, so that Instances and other resources can access the internet via the gateway. Resources attached to other Private Networks than the gateway's network in the VPC can [opt in](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) to receive its default route advertisement. +Moreover, the Public Gateway supports [static NAT](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) (also known as port forwarding), so that ingress traffic from the public internet can reach Instances on the Private Network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the VPC. + +## Usage and management + +### How can I achieve High Availability (HA) networking when the Public Gateway is a zoned resource? Notwithstanding the answer to the previous question, if you have a single Public Gateway in, for example, PAR-1, serving resources from other AZs on the same Private Network and there is an outage in the PAR-1 zone, the gateway will not be able to serve the resources from other unaffected AZs. We are working to improve and develop our Public Gateway product to counteract this. In the meantime, if this is a concern, you could consider attaching several Public Gateways from different AZs to a single Private Network, each advertising a default route to the internet. As long as you are using a recent kernel (e.g. Ubuntu Jammy, Debian bookworm), the traffic will be spread across the different gateways. In the case of an outage in one AZ, you will only lose the gateway in that zone, and the others will continue to serve traffic. -## I need more than 1Gbps bandwidth for my Public Gateway, what can I do? +## Support and troubleshooting + +### I need more than 1 Gbps bandwidth for my Public Gateway, what can I do? -We have introduced a `VPC-GW-L` offer with 3Gbps bandwidth, and a `VPC-GW-XL` offer with 10Gbps of bandwidth, to accommodate customers with this type of need. For pricing details, see our [dedicated page](https://www.scaleway.com/en/pricing/network/). You can upgrade your existing Public Gateway to one of these new offers via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-upgrade-a-public-gateway-to-the-latest-version-andor-to-a-different-commercial-offer-type) or the [Scaleway console](/public-gateways/how-to/upgrade-public-gateway/). \ No newline at end of file +We have introduced a `VPC-GW-L` offer with 3 Gbps bandwidth, and a `VPC-GW-XL` offer with 10 Gbps of bandwidth, to accommodate customers with this type of need. For pricing details, see our [dedicated page](https://www.scaleway.com/en/pricing/network/). You can upgrade your existing Public Gateway to one of these new offers via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-upgrade-a-public-gateway-to-the-latest-version-andor-to-a-different-commercial-offer-type) or the [Scaleway console](/public-gateways/how-to/upgrade-public-gateway/). \ No newline at end of file diff --git a/pages/queues/faq.mdx b/pages/queues/faq.mdx index 8ed428d707..8a8100a88e 100644 --- a/pages/queues/faq.mdx +++ b/pages/queues/faq.mdx @@ -2,23 +2,35 @@ title: Queues FAQ description: Discover Scaleway Queues, and get answers to common questions about the capabilities of the product, how to manage your queues, billing and more. dates: - validation: 2025-04-02 + validation: 2025-09-24 posted: 2025-04-02 productIcon: SqsProductIcon --- -## What is Scaleway Queues? +## Overview -Scaleway Queues is a product for creating managed message queues, using an in-house implementation of AWS SQS protocol. Queues allows you to implement your message queues without the hassle of managing the infrastructure, scaling or updates. Message queues are ideal for facilitating asynchronous job processing and communication between microservices. +### What is Scaleway Queues? -## What is the relationship between Scaleway Queues and AWS SQS? +Scaleway Queues is a product for creating managed message queues, using an in-house implementation of AWS SQS protocol. Queues allows you to implement your message queues without the hassle of managing the infrastructure, scaling, or updates. Message queues are ideal for facilitating asynchronous job processing and communication between microservices. + +### What is the relationship between Scaleway Queues and AWS SQS? **S**imple **Q**ueue **S**ervice, or SQS, is AWS's distributed message [queuing](#queuing) service, that supports programmatic sending of messages via web service applications. Scaleway has developed its own service based on AWS SQS protocol. Scaleway Queues does not have any dependencies on the AWS SQS infrastructure or offering, we use our own stack which is fully self-hosted and developed in-house. -## Is the Scaleway Queues gateway compatible with my application, framework or tool? +## Pricing and billing + +### How is Scaleway Queues billed? + +Billing is based on [queue volume](/queues/concepts/#queue-volume) - the combined size of the messages travelling through queues. For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/). + +## Compatibility and integration + +### Is the Scaleway Queues gateway compatible with my application, framework, or tool? We currently implement the API endpoints listed [here](/queues/reference-content/queues-support/), which makes Scaleway Queues compatible with the AWS SDK as well as many other tools and frameworks including [KEDA](https://keda.sh/) and [Symfony](https://symfony.com/). Note that you need to specify both Regions and URL to ensure compatibility. -## How is Scaleway Queues billed? +### Do Scaleway FIFO queues support the `MessageGroupId` identifier? + +No, as stated on our [Supported Actions](/queues/reference-content/queues-support/) page, Scaleway Queues do not currently support `MessageGroupid`. -Billing is based on [queue volume](/queues/concepts/#queue-volume) - the combined size of the messages travelling through queues. For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/). \ No newline at end of file +To ensure strict message ordering, FIFO queues on Scaleway are designed to allow only one message to be in flight at a time per queue. Because of this, there is no concept of message grouping. If you are using a Serverless Function triggered by the queue, the system will only deliver one message at a time, limiting horizontal scaling, as concurrent processing of independent message batches is not possible. \ No newline at end of file diff --git a/pages/secret-manager/faq.mdx b/pages/secret-manager/faq.mdx index 2c306a7f07..7ec3946ab4 100644 --- a/pages/secret-manager/faq.mdx +++ b/pages/secret-manager/faq.mdx @@ -2,39 +2,49 @@ title: Secret Manager FAQ description: Explore Scaleway Secret Manager with our comprehensive FAQ covering security, secret types, and more. dates: - validation: 2025-04-15 + validation: 2025-09-24 productIcon: SecretManagerProductIcon --- -## Why should you use Scaleway Secret Manager? +## Overview + +### Why should you use Scaleway Secret Manager? Scaleway Secret Manager is a secret management service that allows you to secure access to your applications, services and IT resources. The service makes it easy to manage credentials, API keys and other secrets throughout their lifecycle. You can use Secret Manager to handle the secrets used to access Scaleway products, third-party resources, or on-premises services. -## What types of secrets can I manage with Secret Manager? +## Offering and availability + +### What types of secrets can I manage with Secret Manager? You can manage different types of secrets, such as identifiers for databases, SaaS applications, third-party API keys, SSH keys, or certificates. Secret Manager also allows you to store your secrets in JSON format. The maximum size of a secret is 64 KB. -## How can my applications access these secrets? +### In which regions is Secret Manager available? -To access the secrets stored in Secret Manager, you must create an Identity and Access Management (IAM) policy for your application. Then, you can replace the plain text secrets with code to retrieve the stored secrets through the Secret Manager API. For more information, see the [related documentation](/secret-manager/quickstart/). +The Secret Manager service is deployed in all Scaleway regions: PAR, WAW and AMS. Stored secrets are replicated in different zones within a region. -## In which regions is Secret Manager available? +## Pricing and billing -The Secret Manager service is deployed in all Scaleway regions: PAR, WAW and AMS. Stored secrets are replicated in different zones within a region. +### How is Scaleway Secret Manager billed? -## How does Secret Manager guarantee the security of my secrets? +At the end of the month, you are billed for the number of secret versions stored and API requests made on the service. +A secret version is billed if it is in an enabled or disabled state. +If, for example, you have used a secret version for five days, you will only be billed for the five days and not for the whole month. Find out more about pricing on our [dedicated page](https://www.scaleway.com/en/pricing/?tags=available). + +Recovering secrets [scheduled for deletion](/secret-manager/concepts/#scheduled-deletion) is billed €0.01 per version associated with the secret. + +## Specifications + +### How does Secret Manager guarantee the security of my secrets? Secret Manager allows you to control access to secrets through IAM policies. When you retrieve a secret, Secret Manager decrypts it and transmits it securely via TLS to your local environment. At no point does the service write or cache secrets in plain text on permanent storage. -## How does Secret Manager encrypt my secrets? +### How does Secret Manager encrypt my secrets? Secret Manager uses envelope encryption (AES-256 encryption algorithm) to encrypt your secrets with an internal key management service. -To understand the secrets encryption process, refer to our [related documentation](/secret-manager/reference-content/data-encryption-with-secret-manager/). +To understand the secret encryption process, refer to our [related documentation](/secret-manager/reference-content/data-encryption-with-secret-manager/). -## How is Scaleway Secret Manager billed? +## Usage and management -At the end of the month, you are billed for the number of secret versions stored and API requests made on the service. -A secret version is billed if it is in an enabled or disabled state. -If, for example, you have used a secret version for five days, you will only be billed for the five days and not for the whole month. Find out more about pricing on our [dedicated page](https://www.scaleway.com/en/pricing/?tags=available). +### How can my applications access these secrets? -Recovering secrets [scheduled for deletion](/secret-manager/concepts/#scheduled-deletion) is billed €0.01 per version associated with the secret. \ No newline at end of file +To access the secrets stored in Secret Manager, you must create an Identity and Access Management (IAM) policy for your application. Then, you can replace the plain text secrets with code to retrieve the stored secrets through the Secret Manager API. For more information, see the [related documentation](/secret-manager/quickstart/). \ No newline at end of file diff --git a/pages/serverless-containers/faq.mdx b/pages/serverless-containers/faq.mdx index d66c27cd84..6e5b96e9ac 100644 --- a/pages/serverless-containers/faq.mdx +++ b/pages/serverless-containers/faq.mdx @@ -2,7 +2,7 @@ title: Serverless Containers FAQ description: Discover Serverless Containers and Serverless architecture. dates: - validation: 2025-04-02 + validation: 2025-09-24 productIcon: ContainersProductIcon --- import ContainerRegistryNote from '@macros/serverless/container-registry-note.mdx' @@ -20,22 +20,17 @@ Serverless computing is a cloud execution model where the cloud provider dynamic These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings. -Refer to the [dedicated documentation](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on the differences between Containers, Functions and Jobs. - -### Can I run any application on Serverless Containers? - -Yes. Because Serverless Containers supports any containerized application, you can choose the language, runtime, and framework that best suits your needs. As long as it can run in a container and respond to HTTP requests, Serverless Containers can host it. +Refer to the [dedicated documentation](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on the differences between Containers, Functions, and Jobs. ### What are the cost benefits of using serverless services like Serverless Containers? With serverless, you only pay for the computing resources you use. There are no upfront provisioning costs or paying for idle capacity. When your application traffic is low, the cost scales down, and when traffic spikes, the platform automatically scales up, ensuring you never overpay for unused resources. -### Are applications deployed on Serverless Containers stateless? - -Yes, all applications deployed on Serverless Containers are stateless. This means the server does not store any state about the client session. Instead, the session data is stored on the client and passed to the server as needed. +### How does scaling work in these serverless services? +Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention. -## Billing +## Pricing and billing ### How am I billed for Serverless Containers? @@ -67,11 +62,11 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource * **vCPU consumption:** €1.00 per 100 000 vCPU-s, and we provide a **200 000 vCPU-s free tier** per account per month. | CPU | Price per second | - |------------ |------------------ | - | 0.07 vCPU | €0.0000007 | - | 0.14 vCPU | €0.0000014 | + |-------------- |------------------ | + | 0.07 vCPU | €0.0000007 | + | 0.14 vCPU | €0.0000014 | | 0.28 vCPU | €0.0000028 | - | 0.56 vCPU | €0.0000056 | + | 0.56 vCPU | €0.0000056 | | 1.12 vCPU | €0.0000112 | #### Example @@ -104,69 +99,75 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource You can create billing alerts to get notifications when your costs exceed a certain threshold. Refer to the [dedicated documentation](/billing/how-to/use-billing-alerts/) for more information. -## Resources and performance +## Specifications -### Can I upgrade Serverless Container resources (vCPU and RAM) at any time? +### Are applications deployed on Serverless Containers stateless? -Yes, Serverless Containers resources can be changed at any time without causing downtime. +Yes, all applications deployed on Serverless Containers are stateless. This means the server does not store any state about the client session. Instead, the session data is stored on the client and passed to the server as needed. -### How does scaling work in these serverless services? +## Quotas and limitations -Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform spins up additional instances to handle the load. When demand decreases, instances spin down. This ensures optimal performance without manual intervention. +### What are the limitations of Serverless Containers? -### Can updates of Serverless Containers cause downtime? +Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless-containers/reference-content/containers-limitations/) for more information. -No, deploying a new version of your Serverless Container generates a **rolling update**. This means that a new version of the service is gradually rolled out to your users without downtime. Here is how it works: +## Compatibility and integration -* When a new version of your container is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed. -* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime. -* The old version is decommissioned once the new version is fully serving traffic. +### Which Linux syscalls are supported? -This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it. +Serverless Containers offer two sandboxing environments: -### Can I migrate existing applications to Serverless Containers? +- [Sandbox](/serverless-containers/concepts/#sandbox) v1 guarantees full compatibility with Linux syscalls. -Yes. Many traditional applications can be containerized and deployed to Serverless Containers. This makes it easier to modernize legacy systems without a complete rewrite. By moving to a serverless platform, you gain automatic scaling, reduced operational overhead, and a simpler infrastructure management experience. +- [Sandbox](/serverless-containers/concepts/#sandbox) v2 relies on [gVisor](https://gvisor.dev/), which implements a selection of syscalls. -### How can I select the right resources (vCPU/RAM/ephemeral storage) for Serverless Containers? +Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-sandbox/) for more information on sandboxing environments. -Insufficient vCPU, RAM or ephemeral storage can lead to containers going to error status. Make sure to provision enough resources for your container. +### Which protocols are supported by Serverless Containers? -We recommend you set high values, [use metrics to monitor](/serverless-containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly. +Serverless Containers support **http1** and **http2**. **http1** is enabled by default, but some services (e.g., gRPC) only support **http2**. -### How can I reduce the cold-starts of Serverless Containers? +You can [modify the protocol](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) used by your container from the **Requests tab** of the **Advanced options**. -* **Optimize the startup**: Cold-starts can be affected by loading a large number of dependencies and opening several resources at startup. -Ensure that your code avoids heavy computations or long-running initialization at startup and optimize the number of loaded libraries. + +HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information. + -* **Keep your container warm**: You can use CRON triggers at certain intervals to keep your container warm or set the min-scale parameter to `1` when required. +### Can I use Serverless Containers with Edge Services? -* **Increase resources**: Adding more vCPU and RAM can help to significantly reduce the cold-starts of your container. +You cannot use Serverless Containers with Edge Services because there are no native integrations between the two products yet. -* **Use sandbox v2**: We recommend you use sandbox v2 (advanced settings) to reduce cold starts. +### Can I use the IP address of a Serverless Container? -* **Reduce image size**: Ensure your image is small and clean. [Read our tips for keeping image sizes down](/serverless-containers/reference-content/containers-limitations/#image-size). +By design, it is not possible to guarantee static IPs on Serverless compute resources. -### Which Linux syscalls are supported? +### Can I use my own TLS certificates for custom domains? -Serverless Containers offer two sandboxing environments: +No, you cannot use your own TLS certificates. Scaleway uses Let's Encrypt to generate and automatically renew certificates on your [Custom Domains](https://www.scaleway.com/en/docs/serverless-containers/concepts/#custom-domain). -- [Sandbox](/serverless-containers/concepts/#sandbox) v1 guarantees full compatibility with Linux syscalls. +### Can I run any application on Serverless Containers? -- [Sandbox](/serverless-containers/concepts/#sandbox) v2 relies on [gVisor](https://gvisor.dev/), which implements a selection of syscalls. +Yes. Because Serverless Containers supports any containerized application, you can choose the language, runtime, and framework that best suits your needs. As long as it can run in a container and respond to HTTP requests, Serverless Containers can host it. -Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-sandbox/) for more information on sandboxing environments. +## Access and security -### What are the limitations of Serverless Containers? +### Can I connect to my container using SSH? -Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless-containers/reference-content/containers-limitations/) for more information. +No, it is not possible to connect to Serverless Containers using SSH. Serverless Containers is a fully managed, and stateless compute environment that does not provide direct access to the underlying infrastructure due to several features, such as autoscaling. -### Why does my container have an instance running after deployment, even with min-scale 0? +For monitoring and debugging purposes, you can inspect your container, and interact with it using [Scaleway Cockpit](/serverless-containers/how-to/monitor-container/). + +### Can updates of Serverless Containers cause downtime? -Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum -scale is set to 0. This behavior is not configurable at this time. +No, deploying a new version of your Serverless Container generates a **rolling update**. This means that a new version of the service is gradually rolled out to your users without downtime. Here is how it works: -## Usage +* When a new version of your container is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed. +* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime. +* The old version is decommissioned once the new version is fully serving traffic. + +This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to it. + +## Usage and management ### How can I deploy my containers? @@ -222,77 +223,79 @@ Your application is compatible with Serverless Containers if it meets the follow - It must fit the [Serverless Containers limitations](/serverless-containers/reference-content/containers-limitations/) - It must expose a webserver port and be listening on `0.0.0.0`. -## Network and storage +### How can I store data in my Serverless resource? -### Can I redirect all HTTP traffic to HTTPS? +Serverless resources are by default [stateless](/serverless-containers/concepts/#stateless), local storage is ephemeral. -Yes, you can [redirect all inbound HTTP connections to HTTPS](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) by enabling **HTTPS connections only** in the **Security** tab of the **Advanced options** of your container. +For certain use cases, such as saving analysis results or exporting data, it can be important to have permanent storage to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose: -### Can I whitelist the IPs of my containers? +#### Databases -Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information. +* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. +* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. +* [Managed Database for Redis®](/managed-databases-for-redis/): Fully managed Redis®* in seconds. +* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database. -### Which protocols are supported by Serverless Containers? +#### Storage -Serverless Containers support **http1** and **http2**. **http1** is enabled by default, but some services (e.g., gRPC) only support **http2**. +* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data. +* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. -You can [modify the protocol](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) used by your container from the **Requests tab** of the **Advanced options**. + +Explore all Scaleway products in the console and select the right product for your use case. - -HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information. +Further integrations are also possible even if not listed above, for example, [Secret Manager](/secret-manager/) can help you to store information that requires versioning. -### Why does my gRPC container not respond? +### How can I attach Block Storage to a Serverless Container? -Containers use **http1** by default, yet the gRPC protocol requires `http2`. You can upgrade the protocol to `http2` (`h2c`). +Scaleway Serverless Containers do not currently support attaching Block Storage. These containers are designed to be stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage. -### How can I configure access to a Private Network or Virtual Private Cloud (VPC)? +### Can I upgrade Serverless Container resources (vCPU and RAM) at any time? -Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information. +Yes, Serverless Containers resources can be changed at any time without causing downtime. -### Can I use my own TLS certificates for custom domains? +### Can I redirect all HTTP traffic to HTTPS? -No, you cannot use your own TLS certificates. Scaleway uses Let's Encrypt to generate and automatically renew certificates on your [Custom Domains](https://www.scaleway.com/en/docs/serverless-containers/concepts/#custom-domain) +Yes, you can [redirect all inbound HTTP connections to HTTPS](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) by enabling **HTTPS connections only** in the **Security** tab of the **Advanced options** of your container. -### Can I connect to my container using SSH? +### Can I whitelist the IPs of my containers? -No, it is not possible to connect to Serverless Containers using SSH. Serverless Containers is a fully managed, and stateless compute environment that does not provide direct access to the underlying infrastructure due to several features, such as autoscaling. +Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information. -For monitoring and debugging purposes, you can inspect your container, and interact with it using [Scaleway Cockpit](/serverless-containers/how-to/monitor-container/). +### How can I configure access to a Private Network or Virtual Private Cloud (VPC)? -### How can I attach Block Storage to a Serverless Container? +Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information. -Scaleway Serverless Containers do not currently support attaching Block Storage. These containers are designed to be -stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage. +### Can I migrate existing applications to Serverless Containers? -### How can I store data in my Serverless resource? +Yes. Many traditional applications can be containerized and deployed to Serverless Containers. This makes it easier to modernize legacy systems without a complete rewrite. By moving to a serverless platform, you gain automatic scaling, reduced operational overhead, and a simpler infrastructure management experience. -Serverless resources are by default [stateless](/serverless-containers/concepts/#stateless), local storage is ephemeral. +### How can I select the right resources (vCPU/RAM/ephemeral storage) for Serverless Containers? -For certain use cases, such as saving analysis results or exporting data, it can be important to have permanent storage to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose: +Insufficient vCPU, RAM or ephemeral storage can lead to containers going to error status. Make sure to provision enough resources for your container. -#### Databases +We recommend you set high values, [use metrics to monitor](/serverless-containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly. -* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. -* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. -* [Managed Database for Redis®](/managed-databases-for-redis/): Fully managed Redis®* in seconds. -* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database. +## Support and troubleshooting -#### Storage +### Why does my gRPC container not respond? -* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data. -* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. +Containers use **http1** by default, yet the gRPC protocol requires `http2`. You can upgrade the protocol to `http2` (`h2c`). - -Explore all Scaleway products in the console and select the right product for your use case. +### How can I reduce the cold-starts of Serverless Containers? -Further integrations are also possible even if not listed above, for example, [Secret Manager](/secret-manager/) can help you to store information that requires versioning. - +* **Optimize the startup**: Cold-starts can be affected by loading a large number of dependencies and opening several resources at startup. +Ensure that your code avoids heavy computations or long-running initialization at startup and optimize the number of loaded libraries. -### Can I use Serverless Containers with Edge Services? +* **Keep your container warm**: You can use CRON triggers at certain intervals to keep your container warm or set the min-scale parameter to `1` when required. -You cannot use Serverless Containers with Edge Services because there are no native integrations between the two products yet. +* **Increase resources**: Adding more vCPU and RAM can help to significantly reduce the cold-starts of your container. -### Can I use the IP address of a Serverless Container? +* **Use sandbox v2**: We recommend you use sandbox v2 (advanced settings) to reduce cold starts. -By design, it is not possible to guarantee static IPs on Serverless compute resources. +* **Reduce image size**: Ensure your image is small and clean. [Read our tips for keeping image sizes down](/serverless-containers/reference-content/containers-limitations/#image-size). + +### Why does my container have an instance running after deployment, even with min-scale 0? + +Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum scale is set to 0. This behavior is not configurable at this time. \ No newline at end of file diff --git a/pages/serverless-functions/faq.mdx b/pages/serverless-functions/faq.mdx index e55f9a2c68..720dd21574 100644 --- a/pages/serverless-functions/faq.mdx +++ b/pages/serverless-functions/faq.mdx @@ -2,7 +2,7 @@ title: Serverless Functions FAQ description: Discover Serverless Functions and Serverless architecture. dates: - validation: 2025-04-08 + validation: 2025-09-24 productIcon: FunctionsProductIcon --- @@ -23,7 +23,43 @@ These services allow you to build highly scalable, event-driven, and pay-as-you- With serverless, you only pay for the computing resources you use. There are no upfront provisioning costs or paying for idle capacity. When your application traffic is low, the cost scales down, and when traffic spikes, the platform automatically scales up, ensuring you never overpay for unused resources. -## Billing +### How do Serverless Functions namespaces and Container Registry namespaces interact? + +Serverless Functions namespaces and Container Registry namespaces observe the following behaviors: + +- Creating a Serverless Functions namespace implicitly creates an empty Container Registry namespace. When a Serverless Function is deployed, the built image will be stored in the Container Registry namespace created. + +- Creating a Container Registry namespace **does not** create a Serverless Functions namespace. + +- Deploying a function in a Serverless Functions namespace creates an image in the corresponding Container Registry namespace. + +- If you delete the Container Registry namespace associated with a Serverless Functions namespace, it will be created again when deploying a function within this Serverless Functions namespace. + +### How does scaling work in these serverless services? + +Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform creates additional instances to handle the load. When demand decreases, instances that are not used anymore are removed. This ensures optimal performance without manual intervention. + +## Offering and availability + +### What runtimes are available on Serverless Functions? + +Serverless Functions enables you to deploy functions using popular languages: `Go`, `Node`, `Python`, `PHP`, and `Rust`. + +Refer to our dedicated page about [Serverless Functions Runtimes Lifecycle](/serverless-functions/reference-content/functions-runtimes/). + +### Which protocols are supported by Serverless Functions? + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + +## Specifications + +### How to select the right resources (vCPU/RAM) for Serverless Functions? + +Insufficient vCPU and RAM resources can lead to functions going to error status. Make sure to provision enough resources for your function. + +We recommend you set high values, [use metrics to monitor](/serverless-functions/how-to/monitor-function/) the resource usage of your function, then adjust the value accordingly. + +## Pricing and billing ### How am I billed for Serverless Functions? @@ -31,7 +67,7 @@ With serverless, you only pay for the computing resources you use. There are no Serverless Functions is billed on a pay-as-you-go basis. Three components are taken into account: -* **Monthly request number:** each time your function is invoked we increase a counter. +* **Monthly request number:** each time your function is invoked, we increase a counter. * **Resource consumption:** this component is obtained by multiplying the memory tiers chosen by the duration of each function invocation. @@ -83,7 +119,7 @@ The scheme below illustrates our billing model: | Provision/minimum instances | 0 | * **Resources consumption** - * *Service usage duration:* 30 000 000 Requests x 1 s = 30 000 000 seconds used + * *Service usage duration:* 30 000 000 requests x 1 s = 30 000 000 seconds used * *Memory conversion:* 128 MB = 0.125 GB * *Resources consumed:* 30 000 000 s x 0.125 GB = 3 750 000 GB-s * *Free tier:* 400 000 GB-s @@ -92,7 +128,7 @@ The scheme below illustrates our billing model: * **Requests:** * *Free tier:* 1 000 000 requests - * *Billed requests:* 30 000 000 - 1 000 000 = 29 000 000 Requests + * *Billed requests:* 30 000 000 - 1 000 000 = 29 000 000 requests * *Cost:* 29 000 000 x €0.00000015 = **€4.35** **Total monthly cost: €44.55** @@ -122,8 +158,8 @@ The scheme below illustrates our billing model: * **Requests:** * *Free tier:* 1 000 000 requests - * *Billed requests:* 30 000 000 - 1 000 000 = 29 000 000 Requests - * *Cost:* 29 000 000 x €0.00000015 = **€4.35** + * *Billed requests:* 30 000 000 - 1 000 000 = 29 000 000 requests + * *Cost:* 29 000 000 x €0.00000015 = **€4.35** **Total monthly cost: €45.72** @@ -131,103 +167,50 @@ The scheme below illustrates our billing model: You can create billing alerts to get notifications when your costs exceed a certain threshold. Refer to the [dedicated documentation](/billing/how-to/use-billing-alerts/) for more information. -## Resources and performance - -### How to select the right resources (vCPU/RAM) for Serverless Functions? - -Insufficient vCPU and RAM resources can lead to functions going to error status. Make sure to provision enough resources for your function. - -We recommend you set high values, [use metrics to monitor](/serverless-functions/how-to/monitor-function/) the resource usage of your function, then adjust the value accordingly. - -### How does scaling work in these serverless services? - -Scaling in Serverless Containers and Serverless Functions is handled automatically by the platform. When demand increases - more requests or events - the platform creates additional instances to handle the load. When demand decreases, instances that are not used anymore are removed. This ensures optimal performance without manual intervention. - -### Can I upgrade Serverless Function resources (vCPU and RAM) at any time? - -Yes, Serverless Functions resources can be changed at any time without causing downtime. Refer to the next question for full details. - -### Does updating a Serverless Function cause downtime? - -No, deploying a new version of your Serverless Function generates a **rolling update**. This means that a new version of the service is gradually -rolled out to your users without downtime. Here is how it works: - -* When a new version of your function is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed. -* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime. -* The old version is decommissioned once the new version is fully serving traffic. - -This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to them. - -### How to reduce cold-start of Serverless Functions? - -* **Optimize the startup**: Cold-start can be affected by a loading a large number of dependencies and opening lot of resources at startup. -Ensure that your code avoids heavy computations or long-running initialization at startup and optimize the number of loaded libraries. - -* **Keep your function warm**: You can use CRON triggers at certain intervals to keep your function warm or set the min-scale parameter to one when required. - -* **Increase resources**: Adding more vCPU and RAM can help to significantly reduce the cold-starts of your function. - -* **Use sandbox v2**: We recommend using sandbox v2 (advanced settings) to reduce cold start. +## Quotas and limitations ### What are the limitations of Serverless Functions? Refer to our dedicated page about [Serverless Functions limitations and configuration restrictions](/serverless-functions/reference-content/functions-limitations/) for more information. -### What runtimes are available on Serverless Functions? - -Serverless Functions enables you to deploy functions using popular languages: `Go`, `Node`, `Python`, `PHP`, and `Rust`. - -Refer to our dedicated page about [Serverless Functions Runtimes Lifecycle](/serverless-functions/reference-content/functions-runtimes/). - -### Why does my function have an instance running after deployment, even with min-scale 0? - -Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum -scale is set to `0`. This behavior is not configurable at this time. - -## Usage - -### How can I deploy my functions? - -There are [several ways to deploy Serverless Functions](/serverless-functions/reference-content/deploy-function/), to accommodate a broad range of use cases. +## Compatibility and integration ### How do I integrate my serverless solutions with other Scaleway services? Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/queues/concepts/#queues) and [Topics and Events](/topics-and-events/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. -### How do Serverless Functions namespaces and Container Registry namespaces interact? - -Serverless Functions namespaces and Container Registry namespaces observe the following behaviors: - -- Creating a Serverless Functions namespace implicitly creates an empty Container Registry namespace. When a Serverless Function is deployed, the built image will be stored in the Container Registry namespace created. +### Can I use Serverless Functions with Edge Services? -- Creating a Container Registry namespace **does not** create a Serverless Functions namespace. +You cannot use Serverless Functions with Edge Services because there are no native integrations between the two products yet. -- Deploying a function in a Serverless Functions namespace creates an image in the corresponding Container Registry namespace. +### Can I use the IP address of a Serverless Function? -- If you delete the Container Registry namespace associated with a Serverless Functions namespace, it will be created again when deploying a function within this Serverless Functions namespace. +By design, it is not possible to guarantee static IPs on Serverless Compute resources. -### How can I check build errors? +## Usage and management -Some Serverless runtimes (ex: `Go`, `Rust`) will compile your code in order to make your function executable. -Compilation can fail if errors are present in the code, for example syntax errors and missing libraries. +### How can I deploy my functions? -Build errors are sent to the Observability platform on Scaleway Cockpit. +There are [several ways to deploy Serverless Functions](/serverless-functions/reference-content/deploy-function/), to accommodate a broad range of use cases. -In the `Serverless Functions Logs` dashboard, you will then be able to read information about your log build outputs, if errors occurred during compilation. +### Can I upgrade Serverless Function resources (vCPU and RAM) at any time? -### How can I test my functions locally? +Yes, Serverless Functions resources can be changed at any time without causing downtime. Refer to the next question for full details. -Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless-functions/reference-content/local-testing/) for more information. +### Does updating a Serverless Function cause downtime? -### How can I call my functions periodically? +No, deploying a new version of your Serverless Function generates a **rolling update**. This means that a new version of the service is gradually +rolled out to your users without downtime. Here is how it works: -Scaleway Serverless Functions natively support CRON triggers to call your functions periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting. +* When a new version of your function is deployed, the platform automatically starts routing traffic to the new version incrementally, while still serving requests from the old version until the new one is fully deployed. +* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime. +* The old version is decommissioned once the new version is fully serving traffic. -Periodic CRON triggers also allow you to maintain your functions active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. +This process ensures a seamless update experience, minimizing user disruption during deployments. If needed, you can also manage traffic splitting between versions during the update process, allowing you to test new versions with a subset of traffic before fully migrating to them. -Refer to the [dedicated documentation](/serverless-functions/how-to/add-trigger-to-a-function/) for more information on how to create CRON triggers for your functions. +### How can I test my functions locally? -To learn more about how CRONs work, refer to our [CRON schedule reference documentation](/serverless-functions/reference-content/cron-schedules/). +Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless-functions/reference-content/local-testing/) for more information. ### Where can I find some advanced code examples for functions? @@ -239,27 +222,19 @@ On a Serverless Function, you can change the runtime if the new runtime is from See the [functions runtimes documentation](/serverless-functions/reference-content/functions-runtimes/) for more information about runtimes. -## Network and storage - -### How can I configure access to a Private Network or Virtual Private Cloud (VPC)? - -Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information. - -### Can I allow to list the IPs of my functions? - -Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information. +### How can I call my functions periodically? -### Can I use Serverless Functions with Edge Services? +Scaleway Serverless Functions natively support CRON triggers to call your functions periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting. -You cannot use Serverless Functions with Edge Services because there are no native integrations between the two products yet. +Periodic CRON triggers also allow you to maintain your functions active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. -### Can I use the IP address of a Serverless Function? +Refer to the [dedicated documentation](/serverless-functions/how-to/add-trigger-to-a-function/) for more information on how to create CRON triggers for your functions. -By design, it is not possible to guarantee static IPs on Serverless Compute resources. +To learn more about how CRONs work, refer to our [CRON schedule reference documentation](/serverless-functions/reference-content/cron-schedules/). -### Which protocols are supported by Serverless Functions? +### How can I configure access to a Private Network or Virtual Private Cloud (VPC)? -Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. +Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information. ### How can I attach Block Storage to a Serverless Function? @@ -289,3 +264,33 @@ Explore all Scaleway products in the console and select the right product for yo Some products are not listed but for example, on specific use cases Secret Manager can help you to store information that requires versioning. + +### Can I allow to list the IPs of my functions? + +Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information. + +## Support and troubleshooting + +### How to reduce cold-start of Serverless Functions? + +* **Optimize the startup**: Cold-start can be affected by a loading a large number of dependencies and opening lot of resources at startup. +Ensure that your code avoids heavy computations or long-running initialization at startup and optimize the number of loaded libraries. + +* **Keep your function warm**: You can use CRON triggers at certain intervals to keep your function warm or set the min-scale parameter to one when required. + +* **Increase resources**: Adding more vCPU and RAM can help to significantly reduce the cold-starts of your function. + +* **Use sandbox v2**: We recommend using sandbox v2 (advanced settings) to reduce cold start. + +### How can I check build errors? + +Some Serverless runtimes (ex: `Go`, `Rust`) will compile your code in order to make your function executable. +Compilation can fail if errors are present in the code, for example syntax errors and missing libraries. + +Build errors are sent to the Observability platform on Scaleway Cockpit. + +In the `Serverless Functions Logs` dashboard, you will then be able to read information about your log build outputs, if errors occurred during compilation. + +### Why does my function have an instance running after deployment, even with min-scale 0? + +Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum scale is set to `0`. This behavior is not configurable at this time. \ No newline at end of file diff --git a/pages/serverless-jobs/faq.mdx b/pages/serverless-jobs/faq.mdx index fdb7f463e0..ebb1237ad1 100644 --- a/pages/serverless-jobs/faq.mdx +++ b/pages/serverless-jobs/faq.mdx @@ -2,7 +2,7 @@ title: Serverless Jobs FAQ description: Discover Scaleway's Serverless Jobs dates: - validation: 2025-04-08 + validation: 2025-09-24 productIcon: ServerlessJobsProductIcon --- import ContainerRegistryNote from '@macros/serverless/container-registry-note.mdx' @@ -26,7 +26,7 @@ Serverless computing is a cloud execution model where the cloud provider dynamic These services allow you to build highly scalable, event-driven, and pay-as-you-go solutions. Serverless Containers and Functions help you create applications and microservices without worrying about server management, while Serverless Jobs lets you run large-scale, parallel batch-processing tasks efficiently. This can lead to faster development cycles, reduced operational overhead, and cost savings. -## Billing +## Pricing and billing ### How am I billed for Serverless Jobs? @@ -81,7 +81,7 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum * *Cost:* 464 000 * €0.0000010 = **€0.47** * **vCPU consumption** * *Allocated vCPU conversion:* 1120 mvCPU = 1.12 vCPU - * *Resource consumption:* 432 000 s * 1.12 vCPU = 483 840 vCPU-s + * *Resource consumption:* 432 000 s * 1.12 vCPU = 483 840 vCPU-s * *Free tier:* 200 000 vCPU-s * *Billed resources:* 483 840 - 200 000 = 283 840 vCPU-s * *Cost:* 283 840 * €0.0000100 = **€2.84** @@ -92,19 +92,23 @@ Serverless Jobs are billed on a pay-as-you-go basis, strictly on resource consum You can create billing alerts to get notifications when your costs exceed a certain threshold. Refer to the [dedicated documentation](/billing/how-to/use-billing-alerts/) for more information. -## Resources and performance +## Compatibility and integration ### How do I integrate my serverless solutions with other Scaleway services? Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/queues/) and [Topics and Events](/topics-and-events/), and can easily communicate with services like [Managed Databases](/managed-databases-for-postgresql-and-mysql/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object-storage/), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. -### Can I update Serverless Jobs resources (vCPU and RAM) at any time? +## Access and security -Yes, resources of your Job Definition can be updated at any time. +### Can I connect to my job using SSH? -Ongoing job runs will keep using the resources defined when they started. +No, it is not possible to connect to Serverless Jobs using SSH. Serverless Jobs is a fully managed, and stateless compute environment that does not provide direct access to the underlying infrastructure. -## Usage +For monitoring and debugging purposes, you can inspect your job, and interact with it using [Scaleway Cockpit](/serverless-jobs/how-to/monitor-job/). + +To inject specific commands into a job run, you can add a [startup command](/serverless-jobs/concepts/#startup-command) to a job. + +## Usage and management ### How can I monitor the activity of my Serverless Jobs? @@ -155,22 +159,6 @@ Serverless Jobs can only reference secrets stored in the same [region](/secret-m Job runs are retained for a period of 60 days. Refer to the [dedicated troubleshooting page](/serverless-jobs/troubleshooting/cannot-see-old-job-runs/) for more information on how to store job runs for a longer period of time. -## Network and storage - -### How can I configure access to a Private Network or Virtual Private Cloud (VPC)? - -Scaleway Serverless Jobs does not currently support Scaleway VPC or Private Networks, though this feature is under development. - -To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses. - -### Can I connect to my job using SSH? - -No, it is not possible to connect to Serverless Jobs using SSH. Serverless Jobs is a fully managed, and stateless compute environment that does not provide direct access to the underlying infrastructure. - -For monitoring and debugging purposes, you can inspect your job, and interact with it using [Scaleway Cockpit](/serverless-jobs/how-to/monitor-job/). - -To inject specific commands into a job run, you can add a [startup command](/serverless-jobs/concepts/#startup-command) to a job. - ### How can I store data in my Serverless resource? Serverless resources are by default [stateless](/serverless-functions/concepts/#stateless), local storage is ephemeral. @@ -192,4 +180,16 @@ For some use cases, such as saving analysis results, exporting data etc., it can Explore all Scaleway products in the console and select the right product for your use case. Some products are not listed but for example, on specific use cases Secret Manager can help you to store information that requires versioning. - \ No newline at end of file + + +### Can I update Serverless Jobs resources (vCPU and RAM) at any time? + +Yes, resources of your Job Definition can be updated at any time. + +Ongoing job runs will keep using the resources defined when they started. + +### How can I configure access to a Private Network or Virtual Private Cloud (VPC)? + +Scaleway Serverless Jobs does not currently support Scaleway VPC or Private Networks, though this feature is under development. + +To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses. \ No newline at end of file diff --git a/pages/serverless-sql-databases/faq.mdx b/pages/serverless-sql-databases/faq.mdx index 454f5f82c9..51e1062146 100644 --- a/pages/serverless-sql-databases/faq.mdx +++ b/pages/serverless-sql-databases/faq.mdx @@ -2,11 +2,25 @@ title: Serverless SQL Databases FAQ description: Discover Scaleway's Serverless SQL Databases dates: - validation: 2025-04-16 + validation: 2025-09-24 productIcon: ServerlessDbProductIcon --- -## How am I billed for Serverless SQL Databases? +## Overview + +### What are the differences between Serverless SQL Databases and PostgreSQL databases? + +Serverless SQL Database is compatible with most PostgreSQL-compatible clients and tools. Due to connection pooling support, some minor features are disabled or will not work as expected. Refer to the [Known differences with default PostgreSQL](/serverless-sql-databases/reference-content/known-differences/) for more information. + +## Offering and availability + +### Which PostgreSQL extensions are available? + +Refer to the [supported PostgreSQL extensions](/serverless-sql-databases/reference-content/supported-postgresql-extensions/) page for a list of all available extensions and more details about each one. + +## Pricing and billing + +### How am I billed for Serverless SQL Databases? You are billed both for the compute resources provisioned and the storage used. You can see the cost estimate in the Database creation wizard. @@ -18,7 +32,7 @@ You are billed both for the compute resources provisioned and the storage used. You will not be billed if your database is configured with 0 vCPU as a minimum and is in **idle** status. -## How am I billed for database backups? +### How am I billed for database backups? The 7 days of backups are free. Backup creation and restore operations are considered regular database activity (including the automatic daily backups), so you will be billed according to the resources consumed during the restore operation. @@ -28,22 +42,18 @@ Backup creation and restore operation duration depend on several factors, such a Backup and restore operations for databases that are less than 10 GB usually last a couple of minutes, but they can take longer if you rely heavily on indexes or constraints, or other time-consuming restore operations. -## What are the differences between Serverless SQL Databases and PostgreSQL databases? +## Specifications -Serverless SQL Database is compatible with most PostgreSQL-compatible clients and tools. Due to connection pooling support, some minor features are disabled or will not work as expected. Refer to the [Known differences with default PostgreSQL](/serverless-sql-databases/reference-content/known-differences/) for more information. - -## How many simultaneous connections can my database receive? - -Serverless SQL Database handles connection pooling seamlessly. The number of maximum simultaneous connections will scale with CPU and RAM. Refer to the [Serverless SQL Databases overview](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) for more information on technical specifications. - -Refer to the [Serverless SQL Databases billing](/serverless-sql-databases/faq/#how-am-i-billed-for-serverless-sql-databases) for more information. - -## Is there any latency linked to scaling or cold starts? +### Is there any latency linked to scaling or cold starts? Scaling an active database or waking up an idle database will be seamless for clients connected to the database as the connections will be maintained, but queries performed during these operations may experience a few seconds of delay. You can avoid cold starts by provisioning a minimum of 1 vCPU or more. -## Which PostgreSQL extensions are available? +## Quotas and limitations + +### How many simultaneous connections can my database receive? + +Serverless SQL Database handles connection pooling seamlessly. The number of maximum simultaneous connections will scale with CPU and RAM. Refer to the [Serverless SQL Databases overview](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) for more information on technical specifications. -Refer to our the [supported PostgreSQL extensions](/serverless-sql-databases/reference-content/supported-postgresql-extensions/) page for a list of all available extensions and more details about each one. \ No newline at end of file +Refer to the [Serverless SQL Databases billing](/serverless-sql-databases/faq/#how-am-i-billed-for-serverless-sql-databases) for more information. \ No newline at end of file diff --git a/pages/topics-and-events/faq.mdx b/pages/topics-and-events/faq.mdx index 5d4821afbd..ea1e4b2f60 100644 --- a/pages/topics-and-events/faq.mdx +++ b/pages/topics-and-events/faq.mdx @@ -2,21 +2,25 @@ title: Topics and Events FAQ description: Discover Scaleway Topics and Events, and get answers to common questions about the different protocols available, compatibility with various services, and billing. dates: - validation: 2025-04-10 + validation: 2025-09-24 productIcon: SnsProductIcon --- -## What is Topics and Events? +## Overview + +### What is Topics and Events? Scaleway Topics and Events is a product for creating managed messaging topics, using an in-house implementation of AWS SNS protocol. Previously, it was part of the Messaging and Queuing product. -## What is the relationship between Scaleway Topics and Events, and AWS SNS? +### What is the relationship between Scaleway Topics and Events, and AWS SNS? **S**imple **N**otification **S**ervice, or SNS, is AWS's [publish/subscribe](/topics-and-events/concepts/#publishsubscribe) notification service for the mass delivery of messages. SNS acts as a single message bus that can be sent to a variety of devices and platforms through a single code interface. It is also possible to adapt message formats to the particular needs of each platform. Scaleway has developed its own service based on AWS SNS protocol. Scaleway Topics and Events does not have any dependencies on the AWS SNS infrastructure or offering, we use our own stack which is fully self-hosted and developed in-house. -## Which subscriber types are supported by Scaleway Topics and Events? +## Offering and availability + +### Which subscriber types are supported by Scaleway Topics and Events? The following subscriber types are supported: @@ -24,12 +28,16 @@ The following subscriber types are supported: - Serverless Functions and Containers - Scaleway Queues -## Does Topics and Events support all AWS SNS features? - -For full details on supported and unsupported AWS SNS features, see our [dedicated documentation page](/topics-and-events/reference-content/topics-and-events-support/). +## Pricing and billing -## How is Topics and Events billed? +### How is Topics and Events billed? Billing is based on [topic volume](/topics-and-events/concepts/#topic-volume) (the total sum of each message's size going out from the topic to the subscriptions). -For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/). \ No newline at end of file +For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/). + +## Compatibility and integration + +### Does Topics and Events support all AWS SNS features? + +For full details on supported and unsupported AWS SNS features, see our [dedicated documentation page](/topics-and-events/reference-content/topics-and-events-support/). \ No newline at end of file diff --git a/pages/transactional-email/faq.mdx b/pages/transactional-email/faq.mdx index 3349769c34..4bdbc81b26 100644 --- a/pages/transactional-email/faq.mdx +++ b/pages/transactional-email/faq.mdx @@ -2,104 +2,120 @@ title: Transactional Email FAQ description: Discover Scaleway's Transactional Email dates: - validation: 2025-04-08 + validation: 2025-09-24 productIcon: TransactionalEmailProductIcon --- -## What is Transactional Email? +## Overview + +### What is Transactional Email? Scaleway's Transactional Email service is a fully managed solution dedicated to sending transactional emails. With Transactional Email, you can send your emails via the API or SMTP, add and verify a sending domain, configure SPF and DKIM authentication, and monitor emails via the [Scaleway console](https://console.scaleway.com/). -## What are transactional emails? +### What are transactional emails? A transactional email is a type of automated, non-promotional email triggered by interactions with a website or an application, e.g. account creation, password modification, new order, payment status, etc. Unlike marketing emails, transactional emails are usually expected by customers and thus, have a much higher open rate than marketing emails. -## Can I use your platform to send my marketing emails? +### What is the difference between a dedicated IP and a shared IP? +A dedicated IP is used exclusively by a single user, allowing for better control over sending reputation. A shared IP is shared among multiple users, which can impact deliverability based on the practices of other senders. + +### What are the main benefits of the Scale plan? +The Scale plan provides advanced control over email deliverability through a dedicated IP, detailed performance tracking, and advanced webhook management. It is ideal for businesses with high email-sending volume requirements. + +### Can I use your platform to send marketing emails? Scaleway's Transactional Email platform is dedicated to sending transactional emails only. You cannot use Transactional Email to send marketing emails. [Read our anti-spam policy](https://tem.s3.fr-par.scw.cloud/antispam_policy.pdf) for more information. -## How can I configure DNS records to send emails? +## Pricing and billing -You need to [add SPF and DKIM records](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) to be able to send emails. Find out [how to set up your DNS records for other DNS providers](/tutorials/set-up-spf-dkim-for-dns-providers/). +### How is Scaleway's Transactional Email service billed? -## How do I know if my domain is valid for sending emails? +At the end of the month, you are billed for the number of emails you sent. +If the number of emails you have sent exceeds the number of emails included in your offer, you will be billed for the excess emails. For example, if you use the free tier of 300 emails per month, and you end up sending 305 emails, you will only be billed for five emails out of the 305 you have sent. +Check out our [dedicated page](https://www.scaleway.com/en/pricing/?tags=managedservices-transactionalemail-transactionalemail) for more information about Transactional Email's pricing. -After configuring your SPF and DKIM records, you must launch a verification of the domain either via [the console](https://console.scaleway.com/transactional-email/domains) in the **DNS verification** tab, or the [API](https://www.scaleway.com/en/developers/api/transactional-email/#path-domains-display-spf-and-dkim-records-status-and-potential-errors). You will then receive an email informing you whether your domain was validated or if there are errors to fix so it can be validated. +## Specifications + +### Does a dedicated IP include both IPv4 and IPv6? +Yes, each dedicated IP provided with the Scale plan includes both an IPv4 and an IPv6 address. This ensures better compatibility with different email providers and optimizes the deliverability of sent emails. -## Do I have to set up an MX record for better email deliverability? +Refer to the [Understanding managed dedicated IPs](/transactional-email/reference-content/tem-dedicated-ip) documentation page for more information. + +### Do I have to set up an MX record for better email deliverability? Setting up an [MX record](/transactional-email/concepts#mx-record) is highly recommended to ensure your email deliverability. Find out [how to add an MX record to your domain](/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-your-own-mx-record). You can also [use Scaleway's blackhole MX](/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-scaleways-mx-record) if you do not have your own MX. -## What happens to automatically configured DNS records when I delete a domain in the Transactional Email service? +## Quotas and limitations -When a domain is removed from Scalway's Transactional Email platform, [autoconfigured DNS records](/transactional-email/how-to/autoconfigure-domain/) are not automatically deleted in the Domains & DNS section. You must manually delete or modify these records if you no longer use the domain to send emails. Verifying the associated DNS records is recommended to ensure they are correctly configured or removed. +### What are the limitations and restrictions when using Transactional Email? -## What is the impact on the Transactional Email service if a DNS zone is deleted in Scaleway Domains & DNS? +Find out about [limits and quotas](/transactional-email/reference-content/tem-capabilities-and-limits/) available for Transactional Email. If you want to increase your quota beyond the values shown on this page, [contact our Support team](https://console.scaleway.com/support/create). -If a DNS zone is deleted while [autoconfig is enabled](/transactional-email/how-to/autoconfigure-domain/), the DNS records will be added to the parent zone. This ensures that the domain remains validated on the Transactional Email platform, allowing continued service use without interruption. +### Can I use both a dedicated IP and a shared IP on the same Project? +No, a Project using a dedicated IP cannot send emails via a shared IP. If you want to use a shared IP, you must create a separate Project. -## What are the limitations and restrictions when using Transactional Email? +Refer to the [Understanding managed dedicated IPs](/transactional-email/reference-content/tem-dedicated-ip) documentation page for more information. -Find out about [limits and quotas](/transactional-email/reference-content/tem-capabilities-and-limits/) available for Transactional Email. If you want to increase your quota beyond the values shown on this page, [contact our Support team](https://console.scaleway.com/support/create). +## Access and security -## How is Scaleway's Transactional Email service billed? +### Can I authorize sending emails from specific IP addresses? -At the end of the month, you are billed for the number of emails you sent. -If the number of emails you have sent exceeds the number of emails included in your offer, you will be billed for the excess emails. For example, if you use the free tier of 300 emails per month, and you end up sending 305 emails, you will only be billed for five emails out of the 305 you have sent. -Check out our [dedicated page](https://www.scaleway.com/en/pricing/?tags=managedservices-transactionalemail-transactionalemail) for more information about Transactional Email's pricing. +Yes. You can authorize sending emails from a specific IP address by [configuring conditions in IAM policies](/iam/reference-content/understanding-policy-conditions/). + +You can add a condition like the following to allow an IP address: -## Can I unblock an address that was automatically added to a TEM blocklist before the blockage period ends? +``` +request_ip == "198.51.100.0" +``` + +### Can I unblock an address that was automatically added to a TEM blocklist before the blockage period ends? Yes, you can manually unblock any address, even if it is still under the temporary block period. You can unblock up to five addresses every 24 hours. -## What happens if an address on a TEM blocklist becomes valid again? +### What happens if an address on a TEM blocklist becomes valid again? You can manually unblock the address. Before doing so, ensure that the initial cause of the bounce has been resolved to prevent further issues. -## Can I remove addresses from the blocklist? -Yes, all blocked addresses can be unblocked via the interface. If you manually added an address, you have full control over when and if it is removed from the blocklist. - -## What are the main benefits of the Scale plan? -The Scale plan provides advanced control over email deliverability through a dedicated IP, detailed performance tracking, and advanced webhook management. It is ideal for businesses with high email-sending volume requirements. +### What happens to automatically configured DNS records when I delete a domain in the Transactional Email service? -## What is the difference between a dedicated IP and a shared IP? -A dedicated IP is used exclusively by a single user, allowing for better control over sending reputation. A shared IP is shared among multiple users, which can impact deliverability based on the practices of other senders. +When a domain is removed from Scaleway's Transactional Email platform, [autoconfigured DNS records](/transactional-email/how-to/autoconfigure-domain/) are not automatically deleted in the Domains & DNS section. You must manually delete or modify these records if you no longer use the domain to send emails. Verifying the associated DNS records is recommended to ensure they are correctly configured or removed. -## What happens if my dedicated IP is blacklisted? -TEM can assist in identifying the problem and recommending corrective actions, but the final resolution depends on your sending practices. Therefore, it is essential to follow [best practices for deliverability](/transactional-email/reference-content/understanding-tem-reputation-score/#best-practices-for-domain-reputation-and-deliverability) to avoid this type of situation. +## Usage and management -## Can I use both a dedicated IP and a shared IP on the same project? -No, a project using a dedicated IP cannot send emails via a shared IP. If you want to use a shared IP, you must create a separate project. +### How can I configure DNS records to send emails? -Refer to the [Understanding managed dedicated IPs](/transactional-email/reference-content/tem-dedicated-ip) documentation page for more information. +You need to [add SPF and DKIM records](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) to be able to send emails. Find out [how to set up your DNS records for other DNS providers](/tutorials/set-up-spf-dkim-for-dns-providers/). -## Does a dedicated IP include both IPv4 and IPv6? -Yes, each dedicated IP provided with the Scale plan includes both an IPv4 and an IPv6 address. This ensures better compatibility with different email providers and optimizes the deliverability of sent emails. +### How do I know if my domain is valid for sending emails? -Refer to the [Understanding managed dedicated IPs](/transactional-email/reference-content/tem-dedicated-ip) documentation page for more information. +After configuring your SPF and DKIM records, you must launch a verification of the domain either via [the console](https://console.scaleway.com/transactional-email/domains) in the **DNS verification** tab, or the [API](https://www.scaleway.com/en/developers/api/transactional-email/#path-domains-display-spf-and-dkim-records-status-and-potential-errors). You will then receive an email informing you whether your domain was validated or if there are errors to fix so it can be validated. -## Can I add a new dedicated IP to my Organization? +### Can I add a new dedicated IP to my Organization? If you want to add a new dedicated IP to your Organization, you must create a new Scaleway Project with the Scale plan or contact support to review your request. Refer to the [Understanding managed dedicated IPs](/transactional-email/reference-content/tem-dedicated-ip) documentation page for more information. -## Does Scaleway have an anti-spam policy? -Yes. You can find Scaleway's official Transactional Email anti-spam policy in the [contracts](https://www.scaleway.com/en/contracts/) section of the Scaleway website. +### Can I remove addresses from the blocklist? +Yes, all blocked addresses can be unblocked via the interface. If you manually added an address, you have full control over when and if it is removed from the blocklist. -## Can I authorize sending emails from specific IP addresses? +### What is the impact on the Transactional Email service if a DNS zone is deleted in Scaleway Domains & DNS? -Yes. You can authorize sending emails from a specific IP address by [configuring conditions in IAM policies](/iam/reference-content/understanding-policy-conditions/). +If a DNS zone is deleted while [autoconfig is enabled](/transactional-email/how-to/autoconfigure-domain/), the DNS records will be added to the parent zone. This ensures that the domain remains validated on the Transactional Email platform, allowing continued service use without interruption. -You can add a condition like the following to allow an IP address: +### Does Scaleway have an anti-spam policy? +Yes. You can find Scaleway's official Transactional Email anti-spam policy in the [contracts](https://www.scaleway.com/en/contracts/) section of the Scaleway website. -``` -request_ip == "198.51.100.0" -``` +## Privacy and security -## Has Scaleway conducted a Transfer Impact Assessment (TIA) under Clause 14 of the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) for Transactional Email? +### Has Scaleway conducted a Transfer Impact Assessment (TIA) under Clause 14 of the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) for Transactional Email? For our Transactional Email service, no personal data is transferred outside the EU, so a TIA was not required. All data is hosted and processed entirely within the European Union. -## Does Scaleway engage any non-EU sub-processors for the processing of Transactional Emails? -No. The entire Transactional Email (TEM) technical stack is fully managed by Scaleway, within the EU. Across all our services we maintain a default policy of no data transfers outside the EU. In rare, exceptional cases, we may work with U.S. or Canadian partners. Such transfers are always governed by recognized adequacy mechanisms (e.g. the EU–U.S. Data Privacy Framework) and by our Standard Contractual Clauses as set out in Article 11 of our Data Processing Agreement. +### Does Scaleway engage any non-EU sub-processors for the processing of Transactional Emails? +No. The entire Transactional Email (TEM) technical stack is fully managed by Scaleway, within the EU. Across all our services, we maintain a default policy of no data transfers outside the EU. In rare, exceptional cases, we may work with U.S. or Canadian partners. Such transfers are always governed by recognized adequacy mechanisms (e.g. the EU–U.S. Data Privacy Framework) and by our Standard Contractual Clauses as set out in Article 11 of our Data Processing Agreement. Refer to Scaleway's [Sub-processors page](https://www.scaleway.com/en/subprocessorlist/) for a complete list of the companies we work with, the locations where data is processed and the purpose of the collaboration. + +## Support and troubleshooting + +### What happens if my dedicated IP is blacklisted? +TEM can assist in identifying the problem and recommending corrective actions, but the final resolution depends on your sending practices. Therefore, it is essential to follow [best practices for deliverability](/transactional-email/reference-content/understanding-tem-reputation-score/#best-practices-for-domain-reputation-and-deliverability) to avoid this type of situation. \ No newline at end of file diff --git a/pages/vpc/faq.mdx b/pages/vpc/faq.mdx index d93911ea8f..2bf8764780 100644 --- a/pages/vpc/faq.mdx +++ b/pages/vpc/faq.mdx @@ -2,13 +2,13 @@ title: VPC FAQ description: Discover Scaleway VPC and Private Networks. dates: - validation: 2025-05-05 + validation: 2025-09-24 productIcon: VpcProductIcon --- import image from './assets/scaleway-vpc-pn-diag.webp' -## VPC basics +## Overview ### What is the difference between VPC and a Private Network? @@ -20,104 +20,108 @@ A VPC offers layer 3 network isolation. Within each VPC, you can create multiple If you created your Scaleway [Project](/organizations-and-projects/concepts/#project) before 13 May 2025, one **default VPC** was automatically created in it for each region (Paris, Amsterdam and Warsaw). You can now opt to delete these default VPCs, if you wish. -If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for the Project. +If you created your Scaleway Project after 13 May 2025, default VPCs are no longer pre-created for the Project. Find out more in our [dedicated documentation](/vpc/concepts/#default-vpc). -## VPC routing +### What are Private Networks? -### Can I route traffic between different Private Networks on the same VPC? +Layer 2 Private Networks sit inside layer 3 VPCs. Private Networks are a managed cloud service allowing you to create layer 2 ethernet-switched domains. -Yes, [VPC routing](/vpc/concepts#routing) allows you to automize the routing of traffic between resources in different Private Networks within the same VPC. +These domains can also be called virtual LAN (VLAN). They are virtual but completely private local networks that securely connect your Scaleway resources without necessarily exposing them publicly. Scaleway resources including Instances, Elastic Metal servers, Load Balancers, and Databases are all compatible with Private Networks. -### Can I route traffic between different Private Networks in different VPCs or different Scaleway Projects? +### What is IPAM? -This is not currently possible. You may consider using a VPN tunnel to achieve this, for example [IPsec](https://en.wikipedia.org/wiki/IPsec) or [WireGuard](https://en.wikipedia.org/wiki/WireGuard). Scaleway also offers an [OpenVPN InstantApp](/tutorials/openvpn-instant-app/), making it easy to install a VPN directly on an Instance. +**IP** **A**ddress **M**anager (IPAM) is Scaleway’s tool for planning, tracking, and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources, and has a number of associated functionalities to help manage your Scaleway IPs, such as the ability to reserve an IP on a Private Network and attach it to a specific resource. See our [IPAM FAQ](/ipam/faq/) for more details. -### Can I control traffic flow between my VPC's Private Networks? +### How are NACLs different from security groups? -Yes, use the [Network ACL feature](/vpc/reference-content/understanding-nacls/) to filter packets flowing between the different Private Networks of your VPC. By default, all traffic is allowed to pass, until you start to add rules to the VPC's NACL. +[Security groups](/instances/how-to/use-security-groups/) filter **public** traffic on your Instances, whereas NACLs filter traffic to/from Private Networks only. - -NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console. - +## Offering and availability -### Why can I not route traffic to my Managed Database on another Private Network? +### What happened to my classic, mono-AZ Private Network? -Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. +When VPC and regional Private Networks moved from Public Beta to General Availability, all mono-AZ Private Networks were automatically migrated to be regional. [Read the documentation](/vpc/reference-content/vpc-migration/) to find out more about the migration process. -### Are Serverless Functions and Containers compatible with VPC routing? +## Pricing and billing -No, Serverless Functions and Containers are not currently compatible with VPC routing. Functions and Containers attached to a Private Network support egress traffic only, towards other resources on the same Private Network. +### How much does it cost to create a VPC, Private Network, or reserved private IP address? -### How are NACLs different from security groups? +The following resources and features are free of charge: -[Security groups](/instances/how-to/use-security-groups/) filter **public** traffic on your Instances, whereas NACLs filter traffic to/from Private Networks only. +- VPCs and VPC routing +- Private Networks (except for [Elastic Metal servers](https://www.scaleway.com/en/pricing/elastic-metal/) and [Apple silicon](https://www.scaleway.com/en/pricing/apple-silicon/)) +- Reserved private IP addresses on IPAM -## Private Networks +## Specifications -### What are Private Networks? +### Do resources in a Private Network require a public IPv4 address? -Layer 2 Private Networks sit inside layer 3 VPCs. Private Networks are a managed cloud service allowing you to create layer 2 ethernet-switched domains. +No, they do not require a public IPv4 address. -These domains can also be called virtual LAN (VLAN). They are virtual but completely private local networks that securely connect your Scaleway resources without necessarily exposing them publicly. Scaleway resources including Instances, Elastic Metal servers, Load Balancers, and Databases are all compatible with Private Networks. +### Do I have to restart a Scaleway resource after adding Private Networks? -### Can I connect multiple Private Networks to the same Scaleway resource? +No, Private Network interfaces will appear on your resources without any reboot. -Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, you can connect up to 8 Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. For Elastic Metal, some additional configuration is required: check out our documentation on [configuring the network interface](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks). +### Can resources in a Private Network access the internet without a public IPv4 address? -You can configure: -- Up to 8 Private Networks per Scaleway resource -- Up to 255 Private Networks per Organization -- Up to 512 Scaleway resources per Private Network +Yes. You can attach a [Public Gateway](/public-gateways/how-to/create-a-public-gateway/) to your Private Network to provide internet access to your Instances, Elastic Metal servers, and other attached Scaleway resources. -### What happened to my classic, mono-AZ Private Network? +### Do non-IP protocols work over Private Networks? -When VPC and regional Private Networks moved from Public Beta to General Availability, all mono-AZ Private Networks were automatically migrated to be regional. [Read the documentation](/vpc/reference-content/vpc-migration/) to find out more about the migration process. +Technically, any Ethernet payload should work over Private Networks. However, only IPv4 and IPv6 are officially supported. If you have real use cases for other protocols, let us know by reaching us on the [Scaleway Community Slack](https://scaleway-community.slack.com/). -### How much does it cost to create a VPC, Private Network, or reserved private IP address? +## Quotas and limitations -The following resources and features are free of charge: +### Can I connect multiple Private Networks to the same Scaleway resource? -- VPCs and VPC routing -- Private Networks (except for [Elastic Metal servers](https://www.scaleway.com/en/pricing/elastic-metal/) and [Apple silicon](https://www.scaleway.com/en/pricing/apple-silicon/)) -- Reserved private IP addresses on IPAM +Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, you can connect up to 8 Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. For Elastic Metal, some additional configuration is required: check out our documentation on [configuring the network interface](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks). -### Why can I not delete my Private Network even though it is empty? +You can configure: +- Up to 8 Private Networks per Scaleway resource +- Up to 255 Private Networks per Organization +- Up to 512 Scaleway resources per Private Network -You might have a reserved IP address that is blocking the deletion - check out our [troubleshooting page](/vpc/troubleshooting/cant-delete-vpc-pn/). +## Compatibility and integration -### Do I have to restart a Scaleway resource after adding Private Networks? +### Are Serverless Functions and Containers compatible with VPC routing? -No, Private Network interfaces will appear on your resources without any reboot. +No, Serverless Functions and Containers are not currently compatible with VPC routing. Functions and Containers attached to a Private Network support egress traffic only, towards other resources on the same Private Network. ### Do Private Networks support IPv6? -Yes, when you create a Private Network both an IPv4 and an IPv6 CIDR block are defined. The IPv6 CIDR block is defined automatically and "invisibly" by default at the time of creating the Private Network. It cannot be modified either at the time of creation, or afterward. +Yes, when you create a Private Network, both an IPv4 and an IPv6 CIDR block are defined. The IPv6 CIDR block is defined automatically and "invisibly" by default at the time of creating the Private Network. It cannot be modified either at the time of creation, or afterward. It is a `/64 block`, guaranteed to be unique within the VPC and not overlapping with any of your other Private Networks. Resources that support private IPv6 addressing, e.g. Instances, can then acquire an IPv6 address when they join the Private Network. -### Do resources in a Private Network require a public IPv4 address? +### Do Private Networks support IP autoconfiguration? -No, they do not require a public IPv4 address. +Yes, DHCP is an inbuilt function of Private Networks and provides IP autoconfiguration for your attached resources. Alternatively, you can use Scaleway IPAM to [reserve specific IP addresses](/ipam/how-to/reserve-ip/) on a Private Network and use these to attach resources. -### Can resources in a Private Network access the internet without a public IPv4 address? +## Usage and management -Yes. You can attach a [Public Gateway](/public-gateways/how-to/create-a-public-gateway/) to your Private Network to provide internet access to your Instances, Elastic Metal servers, and other attached Scaleway resources. +### Can I route traffic between different Private Networks on the same VPC? -### Do non-IP protocols work over Private Networks? +Yes, [VPC routing](/vpc/concepts#routing) allows you to automize the routing of traffic between resources in different Private Networks within the same VPC. -Technically, any ethernet payload should work over Private Networks. However, only IPv4 and IPv6 are officially supported. If you have real use cases for other protocols, let us know by reaching us on the [Scaleway Community Slack](https://scaleway-community.slack.com/). +### Can I route traffic between different Private Networks in different VPCs or different Scaleway Projects? -### Do Private Networks support IP autoconfiguration? +This is not currently possible. You may consider using a VPN tunnel to achieve this, for example [IPsec](https://en.wikipedia.org/wiki/IPsec) or [WireGuard](https://en.wikipedia.org/wiki/WireGuard). Scaleway also offers an [OpenVPN InstantApp](/tutorials/openvpn-instant-app/), making it easy to install a VPN directly on an Instance. -Yes, DHCP is an inbuilt function of Private Networks and provides IP autoconfiguration for your attached resources. Alternatively, you can use Scaleway IPAM to [reserve specific IP addresses](/ipam/how-to/reserve-ip/) on a Private Network and use these to attach resources. +### Can I control traffic flow between my VPC's Private Networks? -## IPAM and IP addressing +Yes, use the [Network ACL feature](/vpc/reference-content/understanding-nacls/) to filter packets flowing between the different Private Networks of your VPC. By default, all traffic is allowed to pass, until you start to add rules to the VPC's NACL. -### What is IPAM? + +NACLs are currently in Public Beta, and configurable only via the [VPC API](https://www.scaleway.com/en/developers/api/vpc/) and developer tools. This feature will be coming soon to the Scaleway console. + -**IP** **A**ddress **M**anager (IPAM) is Scaleway’s tool for planning, tracking, and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources, and has a number of associated functionalities to help manage your Scaleway IPs, such as the ability to reserve an IP on a Private Network and attach it to a specific resource. See our [IPAM FAQ](/ipam/faq/) for more details. +### How can I attach my VMs on a Proxmox cluster on Elastic Metal to a Private Network? + +For this purpose, use the option of attaching a **custom resource** to a Private Network, specifying its MAC address. Full instructions for attaching custom resources are in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn#how-can-i-manage-ip-addresses-for-my-proxmox-virtual-machines-vms-on-elastic-metal-servers). + +You can also [reserve a private IP address](/ipam/how-to/reserve-ip/) with IPAM, and use this reserved address to attach a custom resource. ### Do resources' IP addresses on a Private Network risk changing when allocated by managed DHCP? @@ -125,8 +129,12 @@ With Private Networks' inbuilt managed DHCP, a private IP is allocated when the Nonetheless, you can also reserve specific IPs from a Private Network's CIDR block, and use these IPs to attach specific resources, if you prefer. See our documentation on [how to reserve IPs](/ipam/how-to/reserve-ip/). -### How can I attach my VMs on a Proxmox cluster on Elastic Metal to a Private Network? +## Support and troubleshooting -For this purpose use the option of attaching a **custom resource** to a Private Network, specifying its MAC address. Full instructions for attaching custom resources are in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn#how-can-i-manage-ip-addresses-for-my-proxmox-virtual-machines-vms-on-elastic-metal-servers). +### Why can I not route traffic to my Managed Database on another Private Network? -You can also [reserve a private IP address](/ipam/how-to/reserve-ip/) with IPAM, and use this reserved address to attach a custom resource. +Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. + +### Why can I not delete my Private Network even though it is empty? + +You might have a reserved IP address that is blocking the deletion - check out our [troubleshooting page](/vpc/troubleshooting/cant-delete-vpc-pn/). \ No newline at end of file diff --git a/pages/webhosting/faq.mdx b/pages/webhosting/faq.mdx index a71e94d602..abd8c722c3 100644 --- a/pages/webhosting/faq.mdx +++ b/pages/webhosting/faq.mdx @@ -2,35 +2,20 @@ title: Web Hosting description: Explore Web Hosting with our comprehensive FAQ covering website management and hosting capabilities. dates: - validation: 2025-07-09 + validation: 2025-09-24 category: managed-services productIcon: WebhostingProductIcon --- import WordpressWBHPlan from '@macros/webhosting/wordpress-plan.mdx' -## Can you create a Web Hosting if you do not have a domain yet? +## Offering and availability -Yes. During the Web Hosting creation process, you are prompted to enter a domain that will be linked to your Web Hosting. This domain will serve as your website's entry point. -You can create your Web Hosting even if you have not registered any domain yet, by selecting **External domain or register later**. - - - However, once you have created your Web Hosting, remember to **register your domain** either at Scaleway or another provider, and **update your domain's DNS records to use Scaleway's configuration** to connect your domain to Web Hosting. - Find out how to register a Scaleway domain in the [dedicated documentation](/domains-and-dns/how-to/register-internal-domain/). - - - -## Can you create a Web Hosting if your domain is registered with a different provider? - -Yes. During the Web Hosting creation process, you are prompted to enter a domain that will be linked to your Web Hosting. This domain will serve as your website's entry point. -You can create your Web Hosting even if you have registered your domain with a different provider, by selecting **External domain or register later**. - - - However, once you have created your Web Hosting, remember to **update your domain's DNS records to use Scaleway's configuration** to connect your domain to Web Hosting. - +### What does the WordPress Web Hosting plan include? + -## What is the difference between cPanel and WordPress admin? +### What is the difference between cPanel and WordPress admin? When creating your Web Hosting, you can choose to manage your website through two different management interfaces: cPanel or WordPress. @@ -50,6 +35,23 @@ When creating your Web Hosting, you can choose to manage your website through tw You can define how your website looks and behaves without needing to code. -## What does the WordPress Web Hosting plan include? +## Specifications - +### Can I create a Web Hosting if I do not have a domain yet? + +Yes. During the Web Hosting creation process, you are prompted to enter a domain that will be linked to your Web Hosting. This domain will serve as your website's entry point. +You can create your Web Hosting even if you have not registered any domain yet, by selecting **External domain or register later**. + + + However, once you have created your Web Hosting, remember to **register your domain** either at Scaleway or another provider, and **update your domain's DNS records to use Scaleway's configuration** to connect your domain to Web Hosting. + Find out how to register a Scaleway domain in the [dedicated documentation](/domains-and-dns/how-to/register-internal-domain/). + + +### Can I create a Web Hosting if my domain is registered with a different provider? + +Yes. During the Web Hosting creation process, you are prompted to enter a domain that will be linked to your Web Hosting. This domain will serve as your website's entry point. +You can create your Web Hosting even if you have registered your domain with a different provider, by selecting **External domain or register later**. + + + However, once you have created your Web Hosting, remember to **update your domain's DNS records to use Scaleway's configuration** to connect your domain to Web Hosting. + \ No newline at end of file