|
| 1 | +--- |
| 2 | +meta: |
| 3 | + title: I cannot use Scaleway resources |
| 4 | + description: Fix issues encountered while interacting with Scaleway resources and products using the console or API. |
| 5 | +content: |
| 6 | + h1: I cannot use Scaleway resources |
| 7 | + paragraph: Fix issues encountered while interacting with Scaleway resources and products using the console or API. |
| 8 | +tags: api 403 error unable connection fail product resource api cli developer tools |
| 9 | +dates: |
| 10 | + validation: 2025-01-30 |
| 11 | + posted: 2025-01-30 |
| 12 | +categories: |
| 13 | + - iam |
| 14 | +--- |
| 15 | + |
| 16 | +<Macro id="requirements" /> |
| 17 | + |
| 18 | +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization |
| 19 | + |
| 20 | +## Problem |
| 21 | + |
| 22 | +When interacting with Scaleway resources using the Scaleway console, API, CLI, or any other developer tools, you encounter one of the following issues: |
| 23 | + |
| 24 | +- a message saying **Insufficient permissions** displays |
| 25 | +- a message saying **Access Denied** displays |
| 26 | +- a `403` error displays |
| 27 | +- No output displays when interacting with Scaleway products using a command-line tool, and no changes appear in the Scaleway console |
| 28 | + |
| 29 | +## Cause |
| 30 | + |
| 31 | +You (or the IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#application)) may not have the correct appropriate [IAM permissions](/iam/how-to/view-permission-sets/) to perform the desired actions. |
| 32 | + |
| 33 | +## Solution |
| 34 | + |
| 35 | +1. Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys). |
| 36 | + |
| 37 | +2. Make sure that the bearer of the API key (IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#application)) has the appropriate [IAM permissions](/iam/how-to/view-permission-sets/) to perform the desired actions. |
| 38 | + |
| 39 | +3. If you **do not** have [Owner](/iam/concepts/#owner) status for the organization in which you are trying to perform actions, contact the IAM manager or owner of this organization. |
| 40 | + |
| 41 | +4. If your are using a command-line tool to interact with Scaleway resources, make sure that there is no environment variable overriding your API key. Refer to the [documentation on environment variables priority](/scaleway-cli/reference-content/environment-variables/#environment-variables-priority) for more information. |
| 42 | + |
| 43 | +<Message type="note"> |
| 44 | +If you encounter issues while using Object Storage, refer to the [dedicated troubleshooting page](/object-storage/troubleshooting/api-key-does-not-work/). |
| 45 | +</Message> |
| 46 | + |
| 47 | +## Going further |
| 48 | + |
| 49 | +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: |
| 50 | + - Organization ID |
| 51 | + - Project ID |
| 52 | + - Resource type and ID |
| 53 | + - Request type (PUT, GET, etc.) |
| 54 | + - HTTP status code |
| 55 | + - Date and time (timestamp) |
| 56 | + - User-agent (SDK, client, console, etc.) |
| 57 | + - Transaction ID (if possible) |
| 58 | + - Log / trace of the error (if possible) |
0 commit comments