Cloud Migration Process: AWS EKS and App Runner to AWS ECS Express
Updated: Aug 11, 2026
Copy for LLM
Move your infrastructure to AWS ECS Express for two reasons:
- AWS has ended support for Amazon Linux 2 (AL2), which blocks EKS version upgrades — EKS instances are capped at Kubernetes 1.33. AWS standard support for 1.33 ended on July 29, 2026, so these clusters are already running out of support and cost 6 times as much.
- AWS has deprecated the App Runner service. ECS Express is the replacement and has long-term support from the AWS team.
Note: Meta is directly driving the migration for some EKS and App Runner instances. If Meta migrates your instance, you may need to set up your first-party domain again once the migration completes. For instructions, see Custom Domain Setup.
Migrating to a new cloud environment using AWS ECS Express involves three steps:
- Create an AWS ECS Express cluster.
- Migrate pixel, tenant, and user configuration to the ECS Express cluster.
- Manually set up the domain for the cluster and the advertiser domain. A fallback domain handles event routing during the switch, so no events are lost during domain migration.
Step 1: Create an Instance Using AWS ECS Express
To migrate your infrastructure, first deploy a new stack supported by ECS Express in your AWS account. Use the CloudFormation template for your product:
- Conversions API Gateway:
https://conversions-api-gateway-release-production.s3.amazonaws.com/gateway-2.7.0.ecs.yaml - Signals Gateway:
https://signals-gateway-release-production.s3.us-west-2.amazonaws.com/gateway-2.7.0.ecs_sgw.yaml
Then configure scaling by following Auto-scaling limits.
Step 2: Initiate Migration
Once your new instance is successfully deployed, you will be able to log in to a newly created Conversions API Gateway and will see a prompt asking you to start the migration. Click the Migrate button to begin.
If you don’t see the prompt upon login, navigate to Settings > Migrations and backups in the left-hand menu.
Click on Start migration.
Step 3: Follow the Instructions in the Migration Tool
This will open the first step in the migration process. Enter the URL, admin login ID, and admin password for the AWS EKS or App Runner instance you wish to migrate (the origin account) and click Continue.
Your migration will automatically start in the background and you can leave the screen.
Go to the Settings > Migrations and backups page to track the migration status.
Once your migration is completed, set up a custom domain for data routing as described in Step 4. You can then delete the previous setup.
Step 4: Domain Setup
There are two options for setting up a domain on ECS Express: Cloudflare and AWS Certificate Manager. How your domain is managed dictates which SSL solution to use:
- Cloudflare: Preferred if the domain is currently managed by Cloudflare. See Domain setup by Cloudflare.
- AWS Certificate Manager (ACM): Used otherwise. See Domain setup by ACM.
Note: ACM supports up to 22 tenant domains by default. To expand this to 97, request an increase to the AWS certificates per load balancer quota, from 25 to 100.