As by previous Release Notes for EVS called “EVS Common I/O reaches end-of-life on 01.01.2026” this change will affect also RDS instance deployments.
From July 1st, 2025, onwards it will no longer be possible to create new Relational Database Instances using Common I/O disks, as it will reach their end-of-sales on this date and will no longer be marketed/available.
What does this mean for my current running/deployed RDS instances with Common I/O storage?
- Existing instances with Common I/O will remain untouched and will be supported until they are changed into a higher class like Ultra High I/O (also known as Cloud SSD) or some cases into Extreme SSD storage class. A new feature in Relational Database Service called “Change Storage Type” will be introduced in Q3/2025.
- There is only one exception where Common I/O deployment will continue working:
If an existing/running instances where a node of type Primary/StandBy/Cluster/Read Replica in that RDS instance created with Common I/O stops working or get crashed for unknown reasons, then a new restored node of the same type (Primary / StandBy / Cluster/Read Replica) with exact same specifications including Common I/O will be redeployed.
Important note:
The EOS and EOL planning from EVS Common I/O reaches end-of-life on 01.01.2026 will affect all Open Telekom Cloud services that offers Common I/O as storage type.
Please also keep in mind that Common I/O will reach EOL ONLY for Relational Database Service on March 1st, 2026. In the meaning that it will be shut down and will stop working.
More detailed information can be found in this community blog RDS Roadmap for Common I/O End of Sales(July 1st 2025) and End of Life (March 1st 2026) for EU-DE
We will appreciate your comments and of course your like in the Open Telekom Cloud Community Blog.
Further information can be found in Relational Database Service (RDS) area of the Help Centers.