You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/object-storage/faq.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ content:
6
6
h1: Object Storage FAQ
7
7
tags: storage cdn object-storage
8
8
dates:
9
-
validation: 2024-09-23
9
+
validation: 2025-04-02
10
10
category: storage
11
11
productIcon: ObjectStorageProductIcon
12
12
---
@@ -181,7 +181,7 @@ This means that you can transfer objects from Standard class to One Zone - IA an
181
181
182
182
## Do the new storage classes impact Scaleway Glacier?
183
183
184
-
No, the rules for using Glacier class remain the same and your data is still hosted in DC4. Refer to our[Cold storage FAQ](/object-storage/faq/#cold-storage) for more information on Scaleway Glacier.
184
+
No, the rules for using Glacier class remain the same and your data is still hosted in DC4. Refer to the[Cold storage section](#cold-storage) for more information on Scaleway Glacier.
185
185
186
186
## Can I migrate my existing data to the new Multi-AZ Standard class?
Copy file name to clipboardExpand all lines: pages/serverless-containers/faq.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ meta:
5
5
content:
6
6
h1: Serverless Containers FAQ
7
7
dates:
8
-
validation: 2024-09-24
8
+
validation: 2025-04-02
9
9
category: serverless
10
10
productIcon: ContainersProductIcon
11
11
---
@@ -20,6 +20,8 @@ Serverless computing is a cloud execution model where the cloud provider dynamic
20
20
21
21
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.
22
22
23
+
Refer to the [dedicated documentation](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on the differences between Containers, Functions and Jobs.
24
+
23
25
### Can I run any application on Serverless Containers?
24
26
25
27
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.
@@ -101,16 +103,15 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource
101
103
102
104
### Can I upgrade Serverless Container resources (vCPU and RAM) at any time?
103
105
104
-
Yes, Serverless Containers resources can be changed at any time without causing downtime - see the previous question for full details.
106
+
Yes, Serverless Containers resources can be changed at any time without causing downtime.
105
107
106
108
### How does scaling work in these serverless services?
107
109
108
110
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.
109
111
110
112
### Can updates of Serverless Containers cause downtime?
111
113
112
-
No, deploying a new version of your Serverless Container generates a **rolling update**. This means that a new version of the service is gradually
113
-
rolled out to your users without downtime. Here is how it works:
114
+
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:
114
115
115
116
* 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.
116
117
* Once the new version is successfully running, we gradually shift all traffic to it, ensuring zero downtime.
@@ -218,15 +219,14 @@ No, you cannot use your own TLS certificates. Scaleway uses Let's Encrypt to gen
218
219
219
220
### Can I connect to my container using SSH?
220
221
221
-
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.
222
+
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.
222
223
223
224
For monitoring and debugging purposes, you can inspect your container, and interact with it using [Scaleway Cockpit](/serverless-containers/how-to/monitor-container/).
224
225
225
226
### How can I attach Block Storage to a Serverless Container?
226
227
227
228
Scaleway Serverless Containers do not currently support attaching Block Storage. These containers are designed to be
228
-
stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
229
-
solutions like Scaleway Object Storage.
229
+
stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage.
230
230
231
231
### How can I store data in my Serverless resource?
0 commit comments