2026-10-07
Organisations Renamed to Tenants
Organisations are now called Tenants, which reduces confusion and keeps the naming consistent. Permissions, roles and hierarchy remain unchanged.
The rename also changes the Portal URLs.
Previously, Tenant pages used URLs such as https://cloud.switch.ch/organisations/.../projects.
They now use https://cloud.switch.ch/tenants/.../projects.
Update any bookmarks or links that use the old URLs.
Second Compute Region (Release Candidate)
We have given a small group of selected users access to a release candidate of the second Compute region. This limited rollout lets us measure the impact and prevent issues before we release the region to everyone.
New API Endpoints
This release adds API endpoints for updating Project details, managing Shared Application Credentials and S3 access keys, and listing S3 endpoints.
Project Details
Project details such as name, description and the customer billing reference can now be read and updated through the API. Previously, the API did not support updating them. The reference field has also been renamed to customer billing reference to make its purpose clearer.
Shared Application Credentials
Shared Application Credentials can now be managed through the API, which makes it possible to automate credential workflows that previously required manual interaction with the Portal.
The API now supports:
- Listing all credentials of a Compute Service Instance.
- Retrieving a single credential by name.
- Creating a credential.
- Deleting a credential by name.
When you create a credential, the API returns the secret immediately and shows it only once.
S3 Access Keys
The API now supports:
- Listing all access keys of an S3 Service Instance.
- Retrieving a single access key.
- Creating a new access key.
- Deleting an access key.
When you create an access key, the response contains both the access key ID and the secret key. If the S3 Service Instance has only one active endpoint, the API selects it automatically. Otherwise, the request must specify the endpoint explicitly.
S3 Endpoints
The API now also lists all S3 endpoints available for an S3 Service Instance. This makes it possible to discover the available endpoints when automating S3 access key creation.
Multiple Tenants per Contract
Tenant Owners can now request additional Tenants under the contract they already signed with Switch. To request one, fill out the request form available in the Tenant switcher of the Portal. We review each request in consultation with your contract owners and notify you whether we can approve the additional Tenant.
S3 Accounts Migration
To prepare the platform for future IAM features and better identity management, we changed the S3 Service Instance architecture.
Previously, a single user on Ceph represented each S3 Service Instance. This approach worked for basic access key management but limited permission models and auditability, because all actions were attributed to that single user.
Now, an S3 account represents each S3 Service Instance, along with an initial S3 user that has full S3, IAM and SNS permissions for that account. The Portal provisions this user when you create the Service Instance, and the Portal-managed access keys belong to it. The IDs of the account and the initial user are available in the Details tab of the Service Instance.
Buckets created within the Service Instance are now owned by the account, and quotas are now managed at the account level. These changes enable better identity management immediately, because you can grant individual permissions to additional users of the account. They also prepare the platform for upcoming IAM features such as STS.
All existing S3 Service Instances have been migrated. Each received a new S3 account, the user that previously represented the Service Instance became the initial user of the account, and ownership of all existing buckets moved to the account.
To learn more about S3 accounts, STS and S3 IAM concepts, see the Switch Cloud S3 documentation.
Removal of + from Project Names
Project names can no longer contain +, because S3 account naming requirements do not allow it.
We have replaced the character in the names of all affected Projects and their Service Instances with a suitable
alternative, depending on the context.
Enhancements and Bug Fixes
- Enhancement - Seed and Datacenter shown in Kubernetes clusters: The Kubernetes Clusters tab now shows the Seed and Datacenter of each cluster. This makes it easier to identify where a cluster runs, especially as the platform prepares for additional regions.
- Bug Fix - Partner Service link visible to Project users: The link to Partner Services is now visible and accessible only to Tenant Owners. Previously, users who were only Project Members could also see it.
- Bug Fix - Error when sorting S3 access keys by endpoint: Fixed an error that occurred when sorting access keys by endpoint in the S3 Access Keys view.
- Bug Fix - Compute server list limited to 1000 servers: Fixed an issue where the Compute servers list showed a maximum of 1000 servers, even if more existed. All existing servers are now displayed.