|
| 1 | +--- |
| 2 | +meta: |
| 3 | + title: Connecting Scaleway Queues to the AWS-CLI |
| 4 | + description: This page explains how to connect Scaleway Queues to the AWS-CLI |
| 5 | +content: |
| 6 | + h1: Connecting Scaleway Queues to the AWS-CLI |
| 7 | + paragraph: This page explains how to connect Scaleway Queues to the AWS-CLI |
| 8 | +tags: messaging queues sqs aws-cli cli aws sdk python boto |
| 9 | +categories: |
| 10 | + - serverless |
| 11 | +dates: |
| 12 | + validation: 2025-04-02 |
| 13 | + posted: 2025-04-02 |
| 14 | +--- |
| 15 | + |
| 16 | +The AWS-CLI is an open-source tool built on top of the AWS SDK for Python (Boto) that provides commands for interacting with AWS services. With minimal configuration, you can start using the AWS-CLI with Scaleway Queues. This allows you to create, list and manage your queues, send messages and much more, all from your command line. |
| 17 | + |
| 18 | +This guide shows you how to install the AWS-CLI and configure it to connect to Scaleway Queues. |
| 19 | + |
| 20 | +<Macro id="requirements" /> |
| 21 | + |
| 22 | +- A Scaleway account logged into the [console](https://console.scaleway.com) |
| 23 | +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization |
| 24 | +- Valid [credentials](/queues/how-to/create-credentials/) for Scaleway Queues |
| 25 | +<Message type="note"> |
| 26 | + This page assumes you will use the AWS-CLI v1. |
| 27 | +</Message> |
| 28 | + |
| 29 | +## How to install the AWS-CLI |
| 30 | + |
| 31 | +To interact with Scaleway Queues, both `aws-cli` and `awscli-plugin-endpoint` need to be installed. The `awscli-plugin-endpoint` is a useful plugin to help people more easily access third-party providers such as Scaleway. |
| 32 | + |
| 33 | +Install both `aws-cli` and `awscli-plugin` using `pip`. |
| 34 | + |
| 35 | +``` |
| 36 | +pip3 install awscli |
| 37 | +pip3 install awscli-plugin-endpoint |
| 38 | +``` |
| 39 | + |
| 40 | +## How to configure the AWS-CLI |
| 41 | + |
| 42 | +Now you have installed the AWS-CLI, you need to configure it for use with Scaleway Queues. |
| 43 | + |
| 44 | +1. Create a file named `~/.aws/config` by running the following command: |
| 45 | + ``` |
| 46 | + aws configure set plugins.endpoint awscli_plugin_endpoint |
| 47 | + ``` |
| 48 | + |
| 49 | + <Message type="tip"> |
| 50 | + With the most recent versions of awscli (1.29.0 or 2.13.0), the use of a plugin is not necessary. If you are using one of those versions and wish to skip this step, you can do so. Note that this will also affect your configuration file in the next step. |
| 51 | + </Message> |
| 52 | + |
| 53 | +2. Open the `~/.aws/config` file you just created in a text editor and edit it as follows (the Queues (SQS) endpoint URL can be found in the console on the **Settings** page of the Queues product) |
| 54 | + ``` |
| 55 | + [plugins] |
| 56 | + endpoint = awscli_plugin_endpoint |
| 57 | + [profile sns] |
| 58 | + region = fr-par |
| 59 | + [profile sqs] |
| 60 | + region = fr-par |
| 61 | + sqs = |
| 62 | + endpoint_url = https://sqs.mnq.fr-par.scaleway.com |
| 63 | + ``` |
| 64 | + |
| 65 | + Optionally, you can also configure additional profiles by adding new blocks under `[sqs]`. For example, you can add a profile for `[sns]` if you are also using Scaleway Topics and Events, or another profile, `[profile aws]`, to connect to the AWS SQS/SNS service if you want: |
| 66 | + |
| 67 | + ``` |
| 68 | + [plugins] |
| 69 | + endpoint = awscli_plugin_endpoint |
| 70 | + [profile sns] |
| 71 | + region = fr-par |
| 72 | + sns = |
| 73 | + endpoint_url = https://sns.mnq.fr-par.scaleway.com |
| 74 | + [profile sqs] |
| 75 | + region = fr-par |
| 76 | + sqs = |
| 77 | + endpoint_url = https://sqs.mnq.fr-par.scaleway.com |
| 78 | + [profile aws] |
| 79 | + region=eu-west-3 |
| 80 | + output=json |
| 81 | + ``` |
| 82 | + |
| 83 | + <Message type="important"> |
| 84 | + If you are using the AWS-CLI v2, you must include the path to the plugin in your configuration file. Add `cli_legacy_plugin_path = <path-to-plugin>` to the `[plugins]` section, replacing `<path-to-plugin>` with the corresponding path. |
| 85 | + </Message> |
| 86 | + |
| 87 | + <Message type="tip"> |
| 88 | + If you are using aws 1.29.0 or 2.13.0 without the plugin, your configuration file should be as follows: |
| 89 | + ``` |
| 90 | + [profile sqs] |
| 91 | + region = fr-par |
| 92 | + endpoint_url = https://sqs.mnq.fr-par.scaleway.com |
| 93 | + ``` |
| 94 | + </Message> |
| 95 | + |
| 96 | + |
| 97 | +3. Generate a credentials file using the following command: |
| 98 | + ``` |
| 99 | + aws configure |
| 100 | + ``` |
| 101 | + |
| 102 | +4. Open the `~/.aws/credentials` file you just created, and add the access key and secret key you saved when you generated your [credentials](/queues/how-to/create-credentials/): |
| 103 | + ``` |
| 104 | + [queues] |
| 105 | + aws_access_key_id=<ACCESS_KEY_FOR_SQS> |
| 106 | + aws_secret_access_key=<SECRET_KEY_FOR_SQS> |
| 107 | + ``` |
| 108 | + |
| 109 | + If you have other profiles, you can add a block to indicate their credentials too: |
| 110 | + ``` |
| 111 | + [topics_events] |
| 112 | + aws_access_key_id=<ACCESS_KEY_FOR_SNS> |
| 113 | + aws_secret_access_key=<SECRET_KEY_FOR_SNS> |
| 114 | +
|
| 115 | + [aws] |
| 116 | + aws_access_key_id=<ACCESS_KEY> |
| 117 | + aws_secret_access_key=<SECRET_KEY> |
| 118 | + ``` |
| 119 | + |
| 120 | +5. Test that everything is set up correctly with the following command: |
| 121 | + ``` |
| 122 | + aws queues list-queues |
| 123 | + ``` |
| 124 | + |
| 125 | + Use the `--profile` option if you want to test it using a different profile. |
| 126 | + |
| 127 | +<Message type="tip"> |
| 128 | + Check out our dedicated documentation to find more common commands for getting started with the AWS CLI. The [Queues guide](/queues/api-cli/sqs-sns-aws-cli/#getting-started-with-scaleway-queues) walks you through creating and listing queues, sending messages to queues, and more. |
| 129 | +</Message> |
0 commit comments