docs(srv): update

Author: SamyOubouaziz

pages/serverless-containers/how-to/create-auth-token-from-console.mdx

@@ -1,9 +1,9 @@
 ---
-title: How to create and manage an an authentication token from the console
-description: How to create an auth token from the Scaleway console.
-tags: authentication authentication-token containers auth
+title: How to manage authentication for private containers
+description: This page explains how to manage authentication to call private containers
+tags: authentication authentication-token containers auth iam access api secret key
 dates:
-  validation: 2025-11-18
+  validation: 2025-11-19
   posted: 2022-10-14
 ---
 import Requirements from '@macros/iam/requirements.mdx'
@@ -17,7 +17,9 @@ This page shows you how to create and manage an authentication token from the Sc
 - [Created a containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/)
 - [Deployed a container](/serverless-containers/how-to/deploy-container/)
 
-## Creating authentication tokens from the Scaleway console
+## Managing authentication from the Scaleway console
+
+Serverless containers used to rely on a legacy token-based authentication to call private containers. [Scaleway IAM](/iam/) offers a modern way to access private resources using API keys.
 
 <Tabs id="token-serverless">
   <TabsTab label="Scaleway IAM">
@@ -55,40 +57,52 @@ This page shows you how to create and manage an authentication token from the Sc
   </TabsTab>
 </Tabs>
 
+## Calling private containers
 
-## Using tokens
-
-To use your token, you have to add the generated token to a `X-Auth-Token` header.
+To call a private container, you have to add the **secret key** of the [previously created API key](#managing-authentication-from-the-scaleway-console) to a `X-Auth-Token` header.
 
 A **private** container observes this behavior:
 
 * If a call is made without the `X-Auth-Token` header, the call is rejected (status code `403`)
-* If the `X-Auth-Token` header is provided, the token is validated using a public key attached to the namespace.
+* If the `X-Auth-Token` header is provided, the token is validated using the IAM API public key corresponding to the private key provided.
 
-For example, to execute a private container by providing a token using `curl`, run the following command:
+For example, to execute a private container by providing a secret key using `curl`, run the following command:
 
 ```bash
-curl -H "X-Auth-Token: <YOUR_CONTAINER_TOKEN>" <YOUR_CONTAINER_ENDPOINT>
+curl -H "X-Auth-Token: <API_SECRET_KEY>" <YOUR_CONTAINER_ENDPOINT>
 ```
 
-## Deleting tokens
+## Revoking authentication
 
-Tokens will expire by default on their given expiry date. You can delete them manually if they are no longer needed.
+<Tabs id="revoke-authentication">
+  <TabsTab label="Scaleway IAM">
+    To revoke authentication for your container, you can either:
+    - remove the `ContainersPrivateAccess` permission set from the IAM policy
+    - delete the IAM policy targeting the IAM application bearing the API key
+    - delete the API key of your IAM application
+    - delete the IAM application holding the API key
 
-1. Click **Containers** in the **Serverless** section of the side menu. The Serverless Containers page displays.
+  </TabsTab>
+  <TabsTab label="JWT (legacy)">
+    Tokens will expire by default on their given expiry date. You can delete them manually if they are no longer needed.
 
-2. Click the relevant containers namespace to see a list of containers in this namespace.
+    1. Click **Containers** in the **Serverless** section of the side menu. The Serverless Containers page displays.
 
-3. Click the name of the relevant container in the **Containers** tab. The container's details display.
+    2. Click the relevant containers namespace to see a list of containers in this namespace.
 
-4. Click the **Security** tab. A list of settings displays.
+    3. Click the name of the relevant container in the **Containers** tab. The container's details display.
 
-5. Click <Icon name="delete" /> next to the token you want to delete in the **Tokens** panel. A pop-up displays.
+    4. Click the **Security** tab. A list of settings displays.
+
+    5. Click <Icon name="delete" /> next to the token you want to delete in the **Tokens** panel. A pop-up displays.
 
-6. Confirm by clicking **Delete token** to delete the token and to revoke access to the container.
+    6. Confirm by clicking **Delete token** to delete the token and to revoke access to the container.
+
+        <Message type="important">
 
-    <Message type="important">
+          This action is irreversible, and this token will not be able to access your container anymore.
 
-      This action is irreversible, and this token will not be able to access your container anymore.
+        </Message>
+  </TabsTab>
+</Tabs>
 
-    </Message>