AWS retires two services

Amazon Web Services is closing one service to new customers this month and setting a hard shutdown date for another next year. (aws.amazon.com) Amazon Web Services said AWS App Runner will stop accepting new customers on April 30, 2026. Existing App Runner customers can keep running services and creating new resources, but Amazon Web Services said it does not plan to add new features. (aws.amazon.com) Amazon Web Services also said support for Amazon Relational Database Service Custom for Oracle ends on March 31, 2027. After that date, customers will no longer be able to access the console or resources for that product, including database instances, snapshots, and custom engine versions. (aws.amazon.com) AWS App Runner is a managed container service that lets developers deploy web applications from source code or container images without setting up servers themselves. Amazon Web Services is steering customers that leave App Runner toward Amazon Elastic Container Service Express Mode. (aws.amazon.com, aws.amazon.com) Amazon Relational Database Service Custom for Oracle is the version of Amazon’s managed Oracle database offering that gives customers operating-system and database-environment control. Amazon Web Services said customers using that service should begin moving workloads to Amazon Elastic Compute Cloud, and said the change does not affect Amazon Relational Database Service for Oracle or Amazon Relational Database Service Custom for Microsoft SQL Server. (aws.amazon.com, aws.amazon.com) The notices amount to two different kinds of retirement. App Runner is being frozen for newcomers while current users stay on the platform, while Relational Database Service Custom for Oracle has a published end date that removes access entirely in less than a year. (aws.amazon.com, aws.amazon.com) For engineering teams, the timelines are short and concrete. A company that wants to adopt App Runner for a new project has until April 30, 2026 to become a customer, while a company already on Relational Database Service Custom for Oracle has until March 31, 2027 to complete a migration. (aws.amazon.com, aws.amazon.com) Amazon Web Services has not paired these notices with a public promise of new App Runner features or a direct in-place successor for Relational Database Service Custom for Oracle. The practical message in the documentation is to plan around Amazon Elastic Container Service for container apps and Amazon Elastic Compute Cloud for Oracle workloads that needed deep system access. (aws.amazon.com, aws.amazon.com) The next dates on the calendar are April 30, 2026 for new App Runner sign-ups and March 31, 2027 for the end of Relational Database Service Custom for Oracle. Those two deadlines now set the migration schedule for affected Amazon Web Services customers. (aws.amazon.com, aws.amazon.com)