Update — March 31, 2026: The End of Service (EOS) date for shared Key Management Service (KMS) has been extended to December 30, 2026, 00:00:00 (UTC+8) in response to customer feedback. Migration remains required.
Alibaba Cloud has extended the final EOS date for shared KMS to give you more time to complete your migration. The Alibaba Cloud Product Management Committee reviewed customer feedback and moved the deadline to December 30, 2026, 00:00:00 (UTC+8).
Service timeline
| Milestone | Date |
|---|---|
| EOS announced | See [Announcement] EOFS and EOS for the shared KMS |
| EOS date extended | March 31, 2026 |
| Final EOS deadline | December 30, 2026, 00:00:00 (UTC+8) |
Determine your next step
Haven't started migration — Start planning now. December 30, 2026 is the hard cutoff. Follow the migration guide to plan and complete your move to a KMS instance.
Migration in progress — Continue as planned. The extended deadline gives you more time, but complete migration before December 30, 2026 to avoid service disruption.
Already migrated — No action required. This announcement does not affect you.
Why migrate to a KMS instance
Migrating to a KMS instance gives you:
Dedicated resources — Resource isolation eliminates the performance interference common in shared environments.
Fine-grained access control — KMS instances support both identity-based policies and resource-based policies for more precise permission management.
Higher SLA — KMS instances offer a 99.95% service level agreement (SLA) and 99.9999% data availability, backed by comprehensive redundancy and fault tolerance mechanisms.
Resources
Original announcement: [Announcement] EOFS and EOS for the shared KMS
Migration guide: Migrate resources from KMS 1.0 to a KMS 3.0 instance
Support: If you encounter issues during migration, contact Alibaba Cloud support for assistance.