AWS App Runner availability change - AWS App Runner<br>View a markdown version of this page

AWS App Runner availability change - AWS App Runner<br>DocumentationApp RunnerDeveloper Guide<br>Migration overviewPrerequisitesBefore you beginMigration walkthroughMigrating source-based deploymentsAdditional resources<br>AWS App Runner is no longer open to new customers. Existing customers can continue to use the service as normal. For more information, see<br>AWS App Runner availability<br>change.<br>AWS App Runner availability change

After careful consideration, we decided to close AWS App Runner to new customers. Existing AWS App Runner<br>customers can continue to use the service as normal, including creating new resources and services. AWS continues to invest<br>in security and availability for AWS App Runner, but we do not plan to introduce new features.<br>We recommend that customers explore Amazon Elastic Container Service (Amazon ECS) Express Mode when migrating from AWS App Runner. Amazon ECS Express Mode preserves<br>App Runner's operating simplicity while providing access to the broader Amazon ECS feature set. With a single API call, you provide<br>a container image and two IAM roles, and Amazon ECS provisions a complete application stack in your AWS account, including an<br>ECS service on Fargate, an Application Load Balancer, auto scaling, and networking. There is no additional charge for using<br>Amazon ECS Express Mode. You pay only for the underlying AWS resources created to run your application.<br>This guide describes how to migrate an existing App Runner service to ECS Express Mode and gradually shift traffic using<br>DNS routing.

Migration overview

This guide uses a blue/green deployment approach with DNS weighted routing to migrate traffic from App Runner to ECS Express<br>Mode. Both services run simultaneously during the migration. You use Amazon Route 53 (or your DNS provider) to gradually shift<br>traffic from the App Runner service to the ECS Express Mode service, starting with a small percentage and increasing over time.<br>This approach minimizes downtime and allows you to roll back by adjusting DNS weights if issues arise.

A typical migration includes the following steps:

Review the configuration of the existing App Runner service

Create an ECS Express Mode service using the same container image

Configure the same custom domain for the ECS Express Mode service, if you use a custom domain

Shift traffic from App Runner to ECS Express Mode using DNS routing

Complete the migration and delete the App Runner service when it is no longer needed

Prerequisites

Before you start, make sure that you have the following:

An AWS account with appropriate AWS Identity and Access Management permissions to create and manage Amazon ECS, AWS App Runner,<br>Amazon Route 53, and Application Load Balancer resources

AWS CLI installed and configured with credentials for your AWS account

A container image stored in Amazon Elastic Container Registry (or another container registry) to deploy to ECS Express Mode

The IAM roles required by ECS Express Mode:<br>ecsTaskExecutionRole for Amazon ECS task execution and<br>ecsInfrastructureRoleForExpressServices for ECS<br>Express Mode infrastructure provisioning

If you want to preserve an existing custom domain during migration, you also need:

A registered domain name that you control, such as app.example.com, using either Amazon Route 53<br>or a third-party domain registrar

An SSL/TLS certificate in AWS Certificate Manager (ACM) that matches your custom domain. Request a public ACM certificate<br>in the same AWS Region where you're deploying your resources. Both App Runner and Amazon ECS Express Mode require an ACM<br>certificate to enable HTTPS access with custom domains.

Before you begin

Container image requirement — ECS Express Mode deploys a container image.<br>If your App Runner service is deployed from source code, first add a build step that creates a container image and pushes it<br>to a registry such as Amazon Elastic Container Registry. Then deploy that image to ECS Express Mode. See Migrating source-based deployments for details on migrating source-based deployments.

Domain behavior — If your App Runner service already uses a custom domain, such<br>as app.example.com, you can reuse that same hostname during migration and gradually shift traffic between<br>App Runner and ECS Express Mode by updating DNS.

If your App Runner service uses only the default App Runner service URL, the ECS Express Mode service will have a different<br>endpoint. In this case there is no shared hostname that can be used for gradual traffic shifting. You should create and<br>validate the ECS Express Mode service and then update clients or DNS to use the new endpoint.

Migration walkthrough

The following diagram shows how the migration works using Route 53 to shift DNS records between your App Runner service<br>and your ECS Express Mode service.

Step 1: Review the existing App Runner configuration

In the App Runner console, review your existing service and...