NavigationContentFooter
Jump toSuggest an edit

How to secure a container

Reviewed on 08 February 2024Published on 01 February 2023

This page explains how to secure your container.

Security & Identity (IAM)

To perform certain actions described below, you must either be the Owner of the Organization in which the actions will be performed or an IAM user with the necessary permissions.

Requirements
  • You have an account and are logged into the Scaleway console
  • You have created a containers namespace
  • You have deployed a container
  • You have created an authentication token for your container

Use secrets to store access keys and sensitive information

Instead of using environment variables (which are stored in clear text) for your containers, use secrets. These are pieces of information that can be used via environment variables, but are encrypted in storage.

Configure secrets from the Scaleway console

  1. Click Containers in the Serverless section of the side menu. The containers page displays.
  2. Click the relevant container namespace.
  3. Click the name of the container for which you want to define secrets.
  4. Click the Deployment tab.
  5. Scroll to the Secrets section of the page and click Add secret. Enter the key and value for your secret. Repeat for additional secrets.
    Important

    Be careful when you type your secrets. You will not be able to read the value in the console once submitted.

  6. Click Deploy container to submit your secrets and redeploy your container.

Configure secrets using the Serverless framework

Add secret to your container’s description (more information in the plugin documentation). We recommend using them with global environment variables or a .env file stored independently (and kept secret).

secret:
secret_1: ${env:SCW_SECRET_KEY}
Important

We strongly suggest that you do not commit this in a Version Control System (VCS), and do not share your Project ID or access key. This helps to ensure the security of your configuration file, which may contain sensitive data.

Configure secrets using Terraform

Add the following resource description in Terraform:

secret_environment_variables = { "key" = "secret" }

Restrict access to your containers

You can set Serverless containers as private if you want, to protect them from unwanted or unauthorized calls. Unauthenticated calls will be rejected, and your container will not be triggered. This feature is handy if an event triggers your container (CRON, and soon SQS or NATS trigger) or if you put them behind an API gateway or a proxy server (see examples in serverless-examples).

Restrict access from the Scaleway console

  1. Click Containers in the Serverless section of the side menu. The containers page displays.
  2. Click the relevant container namespace.
  3. Click the name of the container for which you want to define secrets.
  4. Click the Security tab.
  5. Set the Privacy Policy of the container to Private.
  6. If required, create an access token for your container.

Your container is now private, and requires an X-Auth-Token header to be called:

curl -H "X-Auth-Token: <YOUR_CONTAINER_TOKEN>" <YOUR_CONTAINER_ENDPOINT>

Restrict access using the Serverless framework

Set privacy: private in your container’s description.

Your container is now private, and requires an X-Auth-Token header to be called:

curl -H "X-Auth-Token: <YOUR_CONTAINER_TOKEN>" <YOUR_CONTAINER_ENDPOINT>

Refer to the How to create an authentication token documentation for more information.

Restrict access using Terraform

Set privacy = "private" in your Terraform resource description.

You can generate access credentials to inject in other applications, such as containers and functions, directly from Terraform using the container_token resource

Set up alerts in Observability Cockpit (upcoming feature)

Using Scaleway Observability Cockpit, a managed Grafana solution to which all your containers are connected, you can:

  • Monitor your containers using the default dashboard or create custom ones.
  • Set up notifications to be alerted in case of unexpected behavior.
See also
How to create and manage an authentication token from the consoleHow to add a trigger to a container
Cloud Products & Resources
  • Scaleway Console
  • Compute
  • Storage
  • Network
  • IoT
  • AI
Dedicated Products & Resources
  • Dedibox Console
  • Dedibox Servers
  • Network
  • Web Hosting
Scaleway
  • Scaleway.com
  • Blog
  • Careers
  • Scaleway Learning
Follow us
FacebookTwitterSlackInstagramLinkedin
ContractsLegal NoticePrivacy PolicyCookie PolicyDocumentation license
© 1999-2024 – Scaleway SAS