Accounts
The Accounts page helps you view and manage accounts in the console.
What are Accounts?
Accounts are your registered cloud provider credentials. Each account represents access to one provider (e.g. Akamai, DigitalOcean, AWS) with a specific authentication method (API key or OAuth). The console uses these accounts to list and manage resources on your behalf.
Customize account display
By default an account is referred by its unique ID assigned by the provider, which may be long and not informative. It is recommended to assign an alias to each of the accounts added. Use the Alias attribute to choose a shorter name for your account.
Also, you can pick a color for each of your accounts to visually group resources.
Aliases and color settings are used for display purposes only, and stored in the browser’s local storage.
View Accounts
The Accounts table lists all registered accounts, with their attributes displayed in table columns. Use pagination controls at the bottom of the page to navigate between pages if there are too many accounts to display.
When table data is being updated, table rows are displayed in italic, and table controls become inactive. It may take time to load the next portion of data.
To refresh the table, use the Reload 🔄 button.
Attributes
The following Account attributes are available:
- ID — Provider-specific identifier
- Provider — Cloud provider (e.g. Akamai)
- Auth region — Region associated with the account
- Auth type — Authentication mechanism
- Auth access level — Authentication role (e.g. readwrite, readonly)
- Alias — User-assigned account name
- Background — Style associated with the account resources
Which columns appear by default can vary; use the Layout button in the toolbar to show or hide columns.
An account works in one region, chosen when it is added and changeable from the Accounts menu in the toolbar. Every page which creates a resource starts in that region, so the region is already chosen when the page opens.
Adding an account
To add a new account, click Add in the toolbar. You will be taken to the Add Account page to register credentials with a cloud provider.
Service credentials
Some provider services do not accept the account’s main credentials. DigitalOcean Spaces (object storage), for example, needs its own access key, with Full Access. For such providers, the account’s details page has a Service credentials card listing the keys the provider needs and whether each is attached. Providers that need no extra keys do not show the card.
- Attach (or Replace) — enter the key’s access key ID and secret. The key is sealed into the account’s encrypted auth cookie, like the main credentials; it is not stored by kopernik.us.
- After a key is attached, the console checks it with a quick read the provider has to authorize with that key (for object storage, listing buckets in the account’s region) and shows the outcome: accepted; valid but lacking a permission kopernik.us needs (e.g. a DigitalOcean key with limited rather than Full Access); or rejected, when the key or secret is wrong. Use the check button to check an attached key again. The check needs a region to be chosen for the account.
- Detach — removes the key. Operations that need it are refused until a key is attached again.
- When an operation is refused because an attached key lacks a permission, the error names the account and offers Go to account, which opens that account’s details page to replace the key.
Sign out from a managed account
To sign out from an account, check the account’s selection box and click the Sign Out ➡️ button. This removes your provider’s authentication cookie from your browser and records a revocation on the server, so any tokens previously issued for that account can no longer be used. No cloud resources are deleted when you sign out.