Home Account & security

Account & security

By D
• 5 articles

API access and Application Credentials

Anything you do in the console you can also do from scripts, Terraform or the command line. Those tools sign in with an Application Credential, not your password: an ID and a secret that stand in for your login, can be limited and given an end date, and can be deleted without touching your account. Create one 1. In the console, open your account menu at the top right, choose User Center, then Application Credentials. 2. Click Create Application Credentials and fill in: - Name: a clear label, for example terraform-ci. - Expires At (optional): the date it stops working. - Roles (optional): leave empty to give it the same access you have, or tick only the roles it needs. - Restriction: leave Unrestricted off. Only a tool that must create other credentials needs it. - Description (optional). 3. Confirm. Your browser downloads a file named after the credential, for example terraform-ci.json, with its id and secret. The secret is in that file only and cannot be shown again, so keep the file safe. Use it Standard command-line and Terraform tools that speak the Gewape Cloud API read the credential from a file named clouds.yaml. Save this as clouds.yaml in the folder you run your tools from, with the id and secret from the downloaded file: clouds: gewape: auth_type: v3applicationcredential auth: auth_url: "https://api.nbo.gewapecloud.com:5000/v3" application_credential_id: "<id>" application_credential_secret: "<secret>" region_name: "RegionOne" interface: public To check that it works, install the command-line tool and list your servers: pip install python-openstackclient openstack --os-cloud gewape server list Terraform, SDKs and the sign-in address and region name for each region are in the developer documentation at developers.gewape.cloud. Keep it safe Treat the secret like a password: store it in a secrets manager, never commit it to code, and replace it from time to time. If one ever leaks, delete it under Application Credentials and create a new one.

Last updated on Nov 02, 2026

Create and switch projects

A project is a separate space for your servers, storage, networks and keys. Nothing in one project can see or touch another unless you allow it. Most people start with one project and that is all they need. Create more when you want to: - keep production and test apart, so a mistake in test can never touch live data - give each service its own keys with only the access it needs - separate teams or clients inside your company Every project you create belongs to your account. There is still one wallet and one invoice, and each charge shows which project it came from. Who can create projects - An owner of your main project (the project you got when your account was opened). - Your account must be verified and activated. - You can have up to 10 projects. Need more? Use the chat on this page. Team members with member or reader access can use the projects they are added to, but cannot create new ones. Create a project 1. Sign in to the console and make sure you are in your main project. Its name shows on your invoices. 2. Click the account icon at the top right and choose Projects. 3. Click Create project. 4. Project name: type a short name such as prod-data or test. Use 2 to 32 lowercase letters, numbers and hyphens. The full name becomes your main project's name, a hyphen and what you typed, for example acme-prod-data. 5. Set up networking in: tick the regions where you will run servers in this project (Kigali is ticked by default). We set up a private network and a secure default firewall there for you. Object Storage works in every project without this. 6. Click Create project. When it says the project is ready, click Switch to it, or Stay here to switch later. You become the owner of the new project. Switch between projects 1. Click the account icon at the top right and choose Projects. 2. Click Switch next to the project you want. The console reloads inside it. Once you have more than one project, the name of the project you are in also shows at the top of the console. Click it to open Projects. Anything you create, including servers, containers, Application Credentials and S3 keys, belongs to the project you are in at that moment. Switch first, then create. Choose who can use each project Only you are in a new project at first. To add people: 1. Open Projects and click Access next to the project. 2. For each person in your team, choose No access, Viewer (can look), Engineer (can create and change resources) or Administrator (can also manage the project). 3. To add someone who is not in your team yet, enter their email under Add a person or a service login to this project only, choose their access and click Add. They get an email to set up their Gewape ID and can use that project only, not your main project. Changes apply the next time that person signs in. Someone new gets their access a few minutes after their first sign-in. Lowering access deletes keys. Moving someone to Viewer or No access deletes the Application Credentials and S3 keys they created in that project, and any server using them stops working. The console asks you to confirm first. Moving between Engineer and Administrator keeps them. Your own access as the account owner is never changed from here. Service logins for servers A server's S3 key or API credentials should not depend on one person. Add a shared team mailbox (for example api-prod@yourcompany.com) to the server's project as Engineer. Sign in as it, create an Application Credential with no expiry date, and create the server's keys with it. You can leave the roles unselected: the credential gets the roles the service login holds in that project. The keys then keep working when people join or leave your team. Billing - All projects are paid from the wallet of your main project. Top-ups, invoices and the Wallet page always show that one wallet, whichever project you are in. - Each charge on your invoice is labelled with the project it came from, for example [acme-prod-data] Object storage. - If the wallet runs out, servers in all your projects are stopped together and start again together after a top-up. Good to know - Projects are created from the main project. If you are in another project, the Projects window tells you to switch to your main project first. - Keys belong to the login that created them, and keys created with an Application Credential stop working when it expires. See Keep production and test apart, with least-privilege keys. - Your main project's team (who can use the main project, and who sees billing) is managed in User Center > Team & Access. If something does not work - No Create project button: you are not an owner of the main project, you are in another project, or you have reached 10 projects. The Projects window says which. - "The name is already taken": pick a different name. - Your account must be activated: finish account verification first, or contact us through the chat. - No Access button: open Projects from your main project. Access is managed from there. - Someone cannot see a project you gave them: they need to sign out and sign in again. Need a hand? Use the chat on this page.

Last updated on Nov 12, 2026