AWS has moved several products into maintenance, preventing new customers from adopting them while keeping service available to existing users. The list includes Amazon Kendra, Amazon Q Business, Cognito Sync, Simple AD and the previous Bedrock Agents generation, now called Bedrock Agents Classic.
The short answer
| Status | Consequence |
|---|---|
| Maintenance | Existing customers continue, but new customers cannot activate the feature. |
| Announced end of support | Migration must be planned before shutdown or loss of support. |
| End of support reached | The service or feature is no longer available under the AWS timeline. |
AWS also lists retirement paths for WorkSpaces PCoIP, WorkSpaces Pool, re:Post Private, SageMaker AI Profiler and other offerings. Dates differ, so each service lifecycle page remains authoritative.
Maintenance is not permanent stability
A maintenance service normally keeps enough operations for current users, but it is no longer a durable architecture choice. New regions, integrations and features may never arrive. A dependency that works today becomes harder to replace as skills and documentation decline.
Existing teams should inventory resources, API versions, volumes, IAM rules and data flows. Add service status to the risk register and assign a migration owner.
Search and assistant workloads
Kendra and Q Business have indexed enterprise content and produced assisted answers. Their maintenance status means alternatives must be compared on search quality, connectors, document ACLs and indexing cost, not merely whether a chatbot exists.
Bedrock Agents Classic creates another challenge: actions, prompts, knowledge bases and observability may not transfer directly to a newer generation. Build an evaluation set before migration to compare responses, permissions and latency.
Backup is not portability
Exporting documents or configuration does not prove they can be restored elsewhere. Document schemas, transformations, identities and network dependencies. Test import into the target before deleting the source.
For directories and workspaces, plan coexistence, DNS cutover, active sessions and rollback. Technical migration needs a user communication and support plan.
A cloud architecture lesson
A managed service reduces daily operations, not lifecycle risk. During design, assess export availability, standards and replacement cost. An abstraction layer is useful only when tested; otherwise it adds code without a real exit.
Subscribe to lifecycle notifications and route deadlines into incident or governance tooling. An email sent to a former administrator is not a process.
Not every AWS announcement requires immediate migration, but the signal is clear. Existing customers should use the maintenance period to prepare a controlled exit before an end date turns planning into an emergency.
Join the discussion
Comments
Loading comments…