[Deadline July 30, 2026] Several AWS Services Stop Accepting New Customers — The Full List and What to Check Now
- 18 hours ago
- 5 min read
On June 30, 2026, AWS announced availability changes across a number of services. Services moving to maintenance can no longer be used by new customers from July 30, 2026. Well-known services such as Amazon Kendra and Amazon Q Business are on the list, so companies that were still evaluating them are affected. Here we organise the services concerned and what you should check now.
Key points
・Maintenance means new sign-ups stop from July 30, 2026. Existing customers can carry on using the service, and AWS operations and support continue
・Sunset means the service is planned for end of provision. This one does require a migration plan
・Some services already reached end of support on June 30, 2026
・Major generative-AI-adjacent services — Kendra, Q Business, the older Bedrock Agents — are on the list
1. "Maintenance" and "sunset" mean different things
The announcement splits into three categories. Mixing them up leads to panicking when there's no need to, so let's sort them out first.
Maintenance (new sign-ups stop)
From July 30, 2026, new customers can no longer use the service. However, existing customers can continue as before, and AWS operations and support continue. In other words: if you're already using it, it isn't about to stop.
Sunset (end of provision planned)
This indicates the service itself is scheduled to be discontinued in future. Here, even existing users need to plan a move to an alternative.
End of support
Already concluded. Some services ended on June 30, 2026.
The thing to hold on to is that maintenance is not an immediate shutdown. This isn't a story about your production environment stopping tomorrow. That said, new features become unlikely, so it's a reasonable input for a medium-term migration decision.
2. Services moving to maintenance (no new use from July 30, 2026)
The services concerned are as follows.
Generative AI and search
・Amazon Bedrock Agents (the November 2023 release, renamed Amazon Bedrock Agents Classic)
・Amazon Kendra
・Amazon Q Business
Authentication and directory
・Amazon Cognito Sync
・AWS Directory Service – Simple AD
Management and governance
・AWS Management Console – myApplications
・AWS Resource Groups – Group Lifecycle Events
・AWS Service Catalog – Application Registry
・AWS Systems Manager – Application Manager
Others
・AWS Mainframe Modernization – Self-Managed Experience
・AWS IoT Device Defender – Detect (this one from August 31, 2026)
Amazon SageMaker AI features
・A2I / Clarify / Debugger / GeoSpatial / Ground Truth / Mechanical Turk / Model Monitor / Role Manager / Studio Lab
For SageMaker AI these are feature-level designations. SageMaker AI as a whole is not going away — worth not misreading.
3. Services moving to sunset (end of provision planned)
・Amazon WorkSpaces – PCoIP / Pool
・AWS Managed Services (AMS) Advanced
・AWS re:Post Private
・Amazon SageMaker AI – Profiler
If you use anything in this category, it's safer to start looking at alternatives early. Amazon WorkSpaces PCoIP in particular has a large impact for companies running virtual desktops in day-to-day operations.
4. Already end of support (June 30, 2026)
・Amazon Chime SDK – Carrier Voice Focus
・Amazon SageMaker AI – Ground Truth Plus
5. Who is actually affected
Sorting out who genuinely needs to act on this announcement:
1. Companies that were about to adopt one of these: after July 30 you can't start using it. Projects at PoC or evaluation stage need to either get started before the deadline or switch plans to an alternative.
2. Companies using a sunset-category service: you need a migration plan. WorkSpaces PCoIP and AMS Advanced in particular are often embedded in business infrastructure, so start early.
3. Companies using a maintenance-category service: no immediate action needed, but be aware that further feature expansion is unlikely.
Put the other way round: if you're simply running a maintenance-category service in an existing production environment, there's nothing you must do today. Starting with a calm inventory is the right move.
6. How to check whether this affects you
To judge whether it applies to you, looking at actual usage is the reliable route. Three approaches, easiest first.
Step 1: Check usage by service in Cost Explorer
In Cost Explorer in the AWS Management Console, group by "Service" and display roughly the last six months. If none of the listed services appear, you can conclude you aren't using them in any billable way. This is the easiest method and works even for non-engineers.
Step 2: Check for resources with the AWS CLI
If you're an engineer, checking directly whether resources exist is more certain. Kendra indices and Simple AD directories, for example, can be checked with commands like these.
# List Kendra indices
aws kendra list-indices --region ap-northeast-1
# List Directory Service directories (check for Type = SimpleAD)
aws ds describe-directories --region ap-northeast-1 \
--query 'DirectoryDescriptions[].[Name,Type,DirectoryId]' --output table
# List Bedrock Agents (Classic)
aws bedrock-agent list-agents --region ap-northeast-1If you use several regions, you need to run these per region. Rather than checking only Tokyo and relaxing, it's worth also checking regions you once touched for testing.
Step 3: Inventory resources across the board with AWS Config
If AWS Config is enabled in your environment, advanced queries let you take an inventory across resource types. If you run multiple accounts, a Config aggregator lets you check them together.
7. How to think about alternatives
AWS hasn't officially said "migrate to this," so treat the following as general direction only. When you actually select something, always confirm the functional requirements against the latest official documentation.
・Amazon Kendra (internal document search) → a RAG setup with Amazon Bedrock Knowledge Bases is the realistic option
・Amazon Q Business → building your own on a Bedrock-based agent foundation (AgentCore and similar), or evaluating third-party SaaS
・Amazon Bedrock Agents Classic → the current Bedrock Agents / AgentCore
・AWS Directory Service – Simple AD → migrating to AWS Managed Microsoft AD is the baseline
・Amazon WorkSpaces – PCoIP → switching to another WorkSpaces protocol
Worth noting: the main value of Kendra and Q Business was that they were complete as managed services. Replacing them with Bedrock Knowledge Bases may cover the functionality, but it moves build and operations effort upward. Compare including that labour.
Summary
To restate the points:
1. Maintenance means new sign-ups stop from July 30, 2026; existing use continues
2. Sunset-category services (WorkSpaces PCoIP / Pool, AMS Advanced, re:Post Private, SageMaker AI Profiler) need a migration plan
3. Start by taking an inventory of your own usage in Cost Explorer
AWS turns services over quickly, and announcements like this will keep coming. We went through the end of Amazon Linux 2 support for Cloud9 ourselves, and with deadline-driven announcements it comes down to noticing early and planning without panic. Getting into the habit of a periodic inventory makes these moments considerably lighter.
If you need help reviewing your AWS setup or drawing up a migration plan, feel free to contact Robin Planning LLC. We support you from a practical standpoint, based on having handled Lambda, RDS and Cloud9 migrations for our own systems.
References