HomeServerlessMessaging and QueuingHow to
Migrate to the new Messaging and Queuing
Jump toUpdate content

How to migrate to the new Messaging and Queuing version

Reviewed on 03 October 2023Published on 03 October 2023

This page shows how to migrate to the new version of Scaleway Messaging and Queuing that was recently released. The migration process depends on the messaging protocols you use. If you were not using Scaleway Messaging and Queuing before 17 October 2023, this document does not concern you.

For an in-depth explanation of the migration process, billing and General Availability, see our dedicated reference documentation.

Security & Identity (IAM):

You may need certain IAM permissions to carry out some actions described on this page. This means:

  • you are the Owner of the Scaleway Organization in which the actions will be carried out, or
  • you are an IAM user of the Organization, with a policy granting you the necessary permission sets
Requirements:
  • You have an account and are logged into the Scaleway console
  • You were using Scaleway Messaging and Queuing before 17 October 2023

NATS

NATS namespaces and credentials created with Scaleway Messaging and Queuing before October 17 2023 have been automatically migrated to the new version.

  1. Log in to the Scaleway console and click Messaging in the side menu, then click NATS. You see that your NATS namespaces have now become NATS accounts. The credentials of your namespaces are now credentials of your NATS accounts.

  2. Update your endpoints in your code and applications. The endpoint of your Scaleway Messaging and Queuing NATS service has changed. The new endpoint is displayed in the console.

Important:

You must update the endpoint in any code or applications using these endpoints. After 30 days, the old endpoints will no longer be supported.


If you use the API to manage your resources, you should use the new v1beta1 version of the Messaging and Queuing NATS API going forward. This is available on the Scaleway developers website.

Note:

If you are a Serverless Functions/Containers user, and have created NATS triggers with the v1alpha1 version of the Messaging and Queuing API, you must recreate these triggers.

SQS

SQS namespaces, credentials and queues created with Scaleway Messaging and Queuing before October 17 2023 are not automatically migrated. You must carry out the following steps to migrate, essentially recreating your resources in the new version and updating your code and applications accordingly.

  1. Log in to the Scaleway console and click Messaging in the side menu.

  2. Activate the SQS protocol.

    You see that your previous namespaces and queues are not present in the console. This is because the console now uses the new version of Messaging and Queuing, and you must recreate your SQS resources.

  3. Create new credentials for your SQS service.

  4. Create new queues for your SQS service.

  5. Update your endpoints in your code and applications. The endpoint of your Scaleway Messaging and Queuing SQS service has changed. The new endpoint is displayed in the console.

Important:

You must update the endpoint in any code or applications using these endpoints. After 30 days, the old endpoints will no longer be supported.


If you use the API to manage your resources, you should use the new v1beta1 version of the Messaging and Queuing SQS API going forward. This is available on the Scaleway developers website. Note that your previous resources (SQS namespaces, queues etc) still exist on the old v1alpha1 version of the API, which you can also access, but after 30 days these resources will be deleted.

Tip:

For an in-depth explanation of why namespaces are now deprecated, how the migration process works, and other details, see our dedicated reference documentation.

Note:

If you are a Serverless Functions/Containers user, and have created SQS triggers with the v1alpha1 version of the Messaging and Queuing API, you must recreate these triggers.

SNS

SNS namespaces and credentials created with Scaleway Messaging and Queuing before October 17 2023 are not automatically migrated. You must carry out the following steps to migrate, essentially recreating your resources in the new version and updating your code and applications accordingly.

  1. Log in to the Scaleway console and click Messaging in the side menu.

  2. Activate the SNS protocol.

    You see that your previous namespaces and credentials are not present in the console. This is because the console now uses the new version of Messaging and Queuing, and you must recreate your SNS resources.

  3. Create new credentials for your SNS service.

  4. Update your endpoints in your code and applications. The endpoint of your Scaleway Messaging and Queuing SNS service has changed. The new endpoint is displayed in the console.

Important:

You must update the endpoint in any code or applications using these endpoints. After 30 days, the old endpoints will no longer be supported.


If you use the API to manage your resources, you should use the new v1beta1 version of the Messaging and Queuing SQS API going forward. This is available on the Scaleway developers website. Note that your previous resources (SNS namespaces, credentials etc.) still exist on the old v1alpha1 version of the API, which you can also access, but after 30 days these resources will be deleted.

Tip:

For an in-depth explanation of why namespaces are now deprecated, how the migration process works, and other details, see our dedicated reference documentation.