Release Notes 26.05
This document describes announcements, discontinuations, and corrections in the scope of ix.Cloud services.
Announcements
Managed noSQL-Instance MongoDB
As of now, the Enterprise Edition (EE) is additionally available in the portal. Customers can now select and use it. The Enterprise Edition forms the basis for advanced features and capabilities that will be implemented and provided in the future.
The following database technologies are available to customers for this service:
| Database Technology | Community | Enterprise |
|---|---|---|
| MongoDB 7 as Managed Service | ■ | - |
| MongoDB 8.0 as Managed Service | ■ | ■ |
| MongoDB 8.2 as Managed Service | ■ | ■ |
For external end customers, only the Enterprise Edition (EE) is available. Due to a license change by the manufacturer (SSPL), we are no longer able to provide the Community Edition (CE) to external customers.
mongo/LICENSE-Community.txt at master · mongodb/mongo · GitHub
File Storage Service
Add-on Option: File Storage Backup Plus
Data Backup Plus
The "File Storage Backup Plus" option extends the existing data backup with advanced security features to protect against malicious, unintended, or erroneous interventions. The service is available as an add-on to existing backup profiles (40d, 200d, 400d) and is activated exclusively on snapshots at the "remote" location.
Tamperproof Snapshots
Snapshots at the remote location are locked with tamperproof protection for a maximum of 100 days, regardless of the backup retention defined in the backup profile. During this lock period, neither the deletion of individual snapshots nor the deletion of the associated volume, even by administrators, is possible.
Multi-Admin Verification
Additionally, the multi-admin verification function is activated. Critical actions such as the deletion of volumes and snapshots after the tamperproof period expires or changes to security-relevant configurations require approval from a second administrator and occur within a clear process plan and within a limited time period.
Object Storage (Feature included in base scope)
Bucket Policies (Access Control Policies)
Optionally, individual bucket policies can be defined per vault to control access to individual buckets or object areas in a targeted manner. Bucket policies enable granular access control based on user or service identities, permitted actions (e.g., read, write, delete), and optional restrictions on network or IP ranges. Furthermore, public access to buckets can be explicitly allowed or prohibited. The configuration and adjustment of bucket policies is the responsibility of the customer.
Discontinuations
Unofficial Firewall Service Endpoints
The following unofficial firewall API endpoints are being discontinued and marked as "deprecated". As of now, these endpoints return empty values.
-
Get firewall policies of a package
/resources/ix.network/v1/subscriptions/{subscriptionId}/firewallpolicypackages/{packageName}/policies -
Get firewall policy packages
/resources/ix.network/v1/subscriptions/{subscriptionId}/firewallpolicypackages -
Get firewall network address entry details
/resources/ix.network/v1/subscriptions/{subscriptionId}/firewallobjectdetails/{entryName}
Accordingly, the corresponding menu item (Networking -> Firewall Policies -> click on Policy (Package Name)) will be removed from the portal.
Managed noSQL-Instance MongoDB
Due to a license change by the manufacturer (SSPL), the Community Edition (CE) for external customers is being discontinued. As of now, the Community Edition is no longer available to external customers. We recommend migrating to the Enterprise Edition (EE) as the successor.
We ask affected customers to plan the migration in time and are happy to assist with any questions.
Corrections
Storage Profile
In the Compute Service under Storage Profile, an error was found in the documentation text. Instead of "SGRS" (synchronous geo-redundant storage), it should be "SZRS" (synchronous zone-redundant storage). This has been corrected.
Change Log
Textual changes in the service catalog are described per release in the change log.
The goal is to provide a transparent and traceable medium for content changes.
| New | Old | Where |
|---|---|---|
|
|
In Managed noSQL-Instance at MongoDB |