Microsoft Azure → Amazon Web Services
AWS equivalent of Azure Container Apps
The closest AWS equivalents of Azure Container Apps are Amazon ECS, AWS Fargate, Amazon ECS Express Mode, AWS App Runner and AWS Lambda Web Functions.
About Azure Container Apps
| Provider | Microsoft Azure |
|---|---|
| Status | Generally available |
| What it is | Serverless container platform built on Kubernetes (KEDA, Envoy, Dapr) without exposing the Kubernetes API. Includes apps, jobs, revisions and traffic splitting, scale to zero, Consumption and Dedicated workload profiles, and serverless GPUs. |
| Documentation | learn.microsoft.com |
| Pricing | Official pricing page |
AWS mappings (4)
| Capability | AWS equivalent | Match |
|---|---|---|
| Provider-native container orchestrator | Amazon ECS | Partial match |
| Serverless container compute | AWS Fargate | Partial match |
| Simplest way to run a containerized web app | Amazon ECS Express Mode, AWS App Runner Maintenance | Partial match |
| Serverless hosting for port-listening web apps | AWS Lambda Web Functions | Partial match |
Container platforms & registries(3)
Provider-native container orchestrator Partial match
Amazon ECS maps most closely to Azure Container Apps. Both hide Kubernetes and run services with scaling, revisions, and load balancing. ECS gives more infrastructure control (EC2 capacity, task placement, managed instances), while Container Apps is more opinionated and serverless-first.
- Abstraction. ECS uses task definitions, services, and clusters on Fargate, ECS Managed Instances, or EC2. Container Apps uses apps, revisions, jobs, and environments on Consumption or Dedicated workload profiles. It's built on Kubernetes, KEDA, Envoy, and Dapr, but you can't reach the Kubernetes API.
- Scaling. ECS uses Application Auto Scaling (target tracking, step) and capacity providers. Container Apps scales on HTTP, TCP, or any KEDA scaler, including scale to zero.
- Service-to-service traffic. ECS uses Service Connect or Cloud Map. Container Apps has built-in DNS discovery, Dapr service invocation, and an Envoy-based ingress with traffic splitting across revisions.
Serverless container compute Partial match
AWS Fargate maps to Azure Container Instances (single container groups and AKS virtual nodes) and to Azure Container Apps' Consumption profile. Fargate is a compute engine for ECS and EKS, while ACI is a standalone service.
- Fargate isn't used on its own. It's the capacity behind ECS tasks or EKS pods (selected through Fargate profiles). ACI can be called directly (container groups) or used as AKS virtual nodes. Virtual Nodes v2 is in preview.
- OS and options. Fargate on ECS supports Linux (x86 and Arm) and Windows Server. ACI supports Linux and Windows, plus confidential containers, Spot containers, NGroups, and standby pools.
- Fargate Spot gives interruptible capacity at a discount for ECS. ACI has Spot containers.
Simplest way to run a containerized web app Partial match
On AWS this is now Amazon ECS Express Mode, since App Runner is closed to new customers. On Azure, the equivalent is Azure Container Apps (or App Service for containers).
- App Runner (source code or image to URL) entered maintenance on Mar 31, 2026. Existing customers can still create services, but no new features are coming. AWS publishes a blue/green migration path to ECS Express Mode.
- ECS Express Mode creates visible resources in your account (ECS service on Fargate, ALB with TLS, auto scaling, networking) from one API call. Container Apps is a managed environment where you deploy with az containerapp up or from source.
- Scale to zero. Container Apps can scale to zero. ECS Express Mode services run at least one Fargate task, so check the minimum task count.
Serverless functions(1)
Serverless hosting for port-listening web apps Partial match
AWS Lambda Web Functions (launched Oct 2026) map partly to Azure Container Apps and Azure App Service. Azure has no function-branded equivalent; the nearest serverless option is Container Apps with scale to zero.
- Lambda Web Functions run Node.js 24 apps on Arm64 (at launch), deployed as .zip. Each environment serves multiple concurrent requests, billed on active CPU and memory, with built-in multi-Region latency routing.
- Container Apps runs any container image with HTTP scaling and scale to zero. App Service runs code or containers on always-on plan instances. Multi-region needs Front Door on Azure.
- Azure Functions custom handlers can wrap a web server, but they still use the Functions host and trigger model.