The short version

App Runner converts source code or a container image into an automatically built, deployed, load-balanced, TLS-enabled, and scalable web service. However, AWS has closed the service to new customers; existing customers can continue using it, while new designs should evaluate the recommended ECS Express Mode path and broader container options.

Lifecycle state dominates the App Runner decision in 2026. Existing customers can operate and migrate deliberately, but a new architecture should not depend on access it cannot obtain or a feature roadmap that AWS says will not expand. The useful lesson is App Runner’s operating model: a compact source-to-service contract. Preserve that simplicity when selecting or building the successor.

The practical decision is not whether AWS App Runner is powerful. It is whether its operating model fits the system and the team. It is best suited to existing App Runner customers operating straightforward HTTP services from GitHub, Bitbucket, or ECR who need continuity while planning a measured migration, especially when current scaling, networking, observability, and deployment capabilities still meet requirements. It is usually a poor fit for new AWS customers, greenfield strategic platforms, workloads needing new feature investment, non-HTTP processing models, unusual networking or runtime control, and any design whose business horizon exceeds the organization’s willingness to carry a service already closed to new adoption. That boundary should be written into the architecture decision so later growth does not turn an intentional choice into accidental lock-in.

Build the right mental model

An App Runner service points to a source-code repository or an ECR image. For source deployments, managed runtimes and an App Runner configuration describe build and start commands. For image deployments, the container is ready to run. App Runner builds when needed, creates a service endpoint with TLS, runs instances, load balances requests, performs health checks, scales according to concurrency, streams logs and metrics, and can automatically deploy source changes. Connections and VPC connectors bridge repository access, private egress, or private endpoints according to the architecture.

The abstraction combines several layers that would otherwise be designed separately: build, artifact handoff, service compute, ingress, certificate, scaling, health, and deployment. Automatic deployments are convenient but should be constrained by branch, testing, and release policy. Instance configuration defines CPU, memory, port, environment, secrets, and runtime role. Autoscaling configuration sets minimum and maximum size and concurrency behavior. Observability integrations expose service logs, deployment logs, metrics, and tracing. The service remains optimized for stateless web applications rather than general container scheduling.

Separate the control plane from the data plane in both design and incident response. The control plane creates configuration and desired state; the data plane carries production work. A deployment API succeeding does not prove that traffic, jobs, or events are healthy. Conversely, a transient control-plane problem should not automatically stop already-running work. Document which APIs are needed during steady state, which are needed only for change, and which dependencies sit on the critical request path.

Make ownership boundaries visible. Identity, network reachability, encryption keys, artifacts, telemetry, quotas, and billing dimensions frequently belong to different teams. A service can be technically managed while the surrounding system remains unmanaged. Name an owner for the application, the platform configuration, the data, the recovery procedure, and the cost model. That simple map prevents the most common failure mode in cloud programs: assuming an abstraction transferred a responsibility that it only moved.

Where it earns its keep

The strongest AWS App Runner architectures begin with a workload whose constraints align with the service. The following patterns are starting points, not product marketing categories. Each still needs an explicit data model, failure model, and ownership model.

Do not choose a cloud service from the deployment demo alone. A demo proves that the happy path exists; an architecture decision must explain day-two change, degraded dependencies, recovery, security evidence, and cost under real load. For AWS App Runner, those questions reveal whether the service removes undifferentiated work or merely postpones it.

• Existing stateless web services: Current customers can continue operating services whose HTTP, scaling, and network needs fit while a successor is prepared.
• Migration reference workload: A representative App Runner service is an excellent test for a new source-to-service platform contract and operating model.
• Portfolio discovery: The service inventory can reveal shared build, identity, secret, domain, and observability capabilities the replacement must centralize.

Architecture moves that age well

A useful reference architecture is a set of constraints with reasons, not a diagram crowded with service icons. Start with the moves below, assign an owner to each, and encode the ones that can be enforced. Exceptions should include an expiration date and a test that proves why the normal path does not work.

Start capacity work with a workload model rather than a product limit table. Capture arrival rate, concurrency, duration, payload size, state size, latency objective, recovery objective, and acceptable interruption. Measure percentiles and saturation, not just averages. Then test the model with production-like traffic and failure injection. Service quotas are guardrails and ceilings; they are not a substitute for understanding how a dependency behaves as demand approaches its own boundary.

• Inventory every service and export its complete runtime, network, identity, scaling, and release contract.
• Containerize source-based services into portable artifacts before changing the traffic plane.
• Build the successor as a paved road, then migrate low-risk and representative workloads first.
• Use gradual traffic shift and independent rollback; do not combine platform and application rewrites by default.

Scaling and performance

App Runner maintains provisioned instances for low latency and adds active instances as request concurrency rises, within configured limits. Tune concurrency from measured application behavior; a high setting can increase latency or exhaust per-process resources before scaling reacts, while a low setting creates more active instances and cost. Keep sessions and files external, use bounded connection pools, and protect downstream databases and APIs. Migration sizing should capture actual request concurrency, CPU and memory, scale-out timing, minimum capacity, startup time, and health behavior so the successor does not regress silently.

Start capacity work with a workload model rather than a product limit table. Capture arrival rate, concurrency, duration, payload size, state size, latency objective, recovery objective, and acceptable interruption. Measure percentiles and saturation, not just averages. Then test the model with production-like traffic and failure injection. Service quotas are guardrails and ceilings; they are not a substitute for understanding how a dependency behaves as demand approaches its own boundary.

Performance tuning must preserve correctness. Optimize the slowest meaningful business path, verify the change against a representative distribution, and watch for work displaced into queues, retries, caches, or operators. With AWS App Runner, a lower service-level latency can still create a worse system if downstream saturation, recovery backlog, or cost per completed transaction rises. Keep load-test artifacts and capacity assumptions versioned beside the architecture.

Security and governance

Narrow the instance role, protect repository connections, store secrets through supported managed references, and govern who can change source, configuration, autoscaling, or deployment. Use private egress only when the VPC dependencies justify its routing and cost, and review whether inbound service exposure meets policy. Pin container images by release practice, scan them, and keep runtimes supported. During migration, avoid temporarily widening IAM or network boundaries simply to make two platforms work; design parallel identities and traffic controls explicitly.

Use least privilege as an engineering process, not a one-time IAM document. Begin with separate human, deployment, and runtime identities. Observe required actions, narrow resources and conditions, and add explicit organization guardrails for high-impact operations. Encrypt data in transit and at rest, but also design key ownership, rotation, deletion protection, and break-glass access. Centralize audit records in an account and storage boundary that a compromised workload cannot rewrite.

Threat-model AWS App Runner across four surfaces: the management API, the workload’s runtime identity, the network and event inputs that reach it, and the software or configuration artifact that is deployed. Add the data stores and observability pipeline as separate trust boundaries. Preventive controls reduce the reachable state space; detective controls shorten time to evidence; recovery controls make destructive events survivable. A mature design has all three and tests them independently.

Governance should make the secure path faster. Provide approved modules, narrowly scoped roles, standard encryption and logging defaults, ownership tags, and automated evidence. Block dangerous configurations at the organization or pipeline boundary when the intent is unambiguous. Leave application teams enough room to tune the workload without letting every team invent identity, ingress, logging, and incident access from scratch.

Reliability and recovery

Existing services still need normal production engineering: health endpoints that reflect readiness, controlled promotion, downstream timeouts, safe retries, external state, and tested rollback. Automatic deployment from a branch can couple every merge to production; use a release branch or manual promotion when risk requires it. Capture a recoverable service specification and container artifact outside App Runner. Build and test the successor before urgency, then shift traffic gradually with independent rollback. The service closure is not an immediate outage, but it is a planning signal.

Define failure in business terms before selecting a recovery mechanism. Availability, durability, recovery time, and recovery point are different objectives. Multi-zone placement improves some infrastructure failures but does not repair corrupt deployments or deleted data. Backups address some data events but do not guarantee a runnable application. Use layered controls: health-based replacement, redundancy, deployment rollback, data protection, quota monitoring, and a rehearsed regional or organizational recovery path where the business requires one.

Write failure-mode tests for AWS App Runner before the first serious incident. Include unavailable capacity, throttled control APIs, expired credentials, bad configuration, dependency timeout, partial deployment, telemetry loss, and operator error. Test what happens to in-flight work, how the system detects the condition, who is paged, and how replay or rollback avoids duplicate effects. Recovery time measured in a game day is more credible than recovery time copied from a diagram.

Keep the recovery path simpler than the primary path. If restoration depends on the same identity, network, artifact repository, region, or specialist that the incident removed, it is not independent. Store runbooks where responders can reach them, pre-authorize narrowly scoped emergency actions, and verify backups by restoring into an isolated environment. Record the achieved recovery point and time so business owners can compare evidence with policy.

Cost and capacity economics

App Runner cost includes provisioned and active compute, build activity, logs, data transfer, and VPC-related network resources. Minimum provisioned capacity creates an idle baseline, while active duration rises with traffic and concurrency settings. Compare existing cost with ECS Express Mode, ordinary ECS on Fargate, Lambda plus an HTTP front door, Elastic Beanstalk, and third-party platforms using measured traffic. Include migration engineering and operational difference, not just compute rates. A cheaper successor that recreates a platform team may not be cheaper overall.

Evaluate unit economics at the level customers consume: cost per request, job, simulation, tenant, build, or environment. Tagging helps allocation, but architecture determines most spend. Include idle baseline, burst premium, storage growth, log retention, data transfer, support, licenses, and operator time. Rate discounts should follow rightsizing and workload-shape work. A commitment applied to the wrong baseline converts an optimization opportunity into a contract.

Create a cost model for AWS App Runner with a low, expected, and stress scenario. Tie every variable to a measurable workload characteristic and identify which team can influence it. Alarm on anomalous unit cost as well as total spend; total spend naturally rises with successful products, while unit cost exposes architectural drift. Review unused capacity and retained artifacts on a schedule, and give every long-lived resource an owner and lifecycle policy.

Optimization should preserve reliability margins. Removing all idle capacity, shortening every retention period, or consolidating every boundary may lower a spreadsheet while increasing incident probability and recovery time. Price the resilience requirement explicitly. Then apply the least risky lever first: eliminate waste, rightsize, improve utilization, reduce unnecessary transfer, select the correct purchasing model, and only then make longer commitments.

Operating it in production

For existing customers, freeze undocumented console state by exporting service, scaling, connection, network, identity, environment, secret, health, and observability configuration into an owned specification. Inventory every App Runner service, repository, domain, VPC connector, role, secret, dependency, and traffic profile. Patch runtimes and images, keep current alarms, and define migration priority from business criticality and platform mismatch. Establish a successor golden path and migrate a representative low-risk service first to validate deployment, traffic shift, rollback, and operator training.

Treat configuration as versioned product code. Changes should pass static checks, policy checks, integration tests, and an environment that resembles production. Promote the same artifact; do not rebuild it differently at every stage. Prefer gradual exposure, observable health gates, and automated rollback for reversible changes. For irreversible data or identity changes, use expansion-and-contraction patterns and explicit checkpoints. Record who changed what, why, and which measured signal declared the change safe.

Build one operational view that links AWS App Runner health to customer outcomes. Infrastructure metrics explain resources, application metrics explain behavior, traces explain selected paths, and logs provide detailed evidence. None is sufficient alone. Define symptom-based alerts around availability, latency, backlog, freshness, correctness, and saturation; route them to an accountable team; and attach the first diagnostic action. Remove alerts that never change a decision.

Run a monthly service review until the platform is boring. Examine incidents, near misses, failed changes, quota headroom, runtime or image lifecycle, cost per unit, access exceptions, recovery evidence, and support announcements. Convert repeated manual actions into automation only after the team understands the decision being automated. Good operations reduce surprise without hiding state from the people accountable for it.

Failure patterns to avoid

Most expensive mistakes are reasonable shortcuts that survived beyond their original context. Treat these risks as design-review prompts. Ask which control detects each condition, how quickly the team can recover, and whether the workload can be moved or reshaped before the risk becomes a constraint.

A risk register is useful only when it changes action. Give each item an owner, leading indicator, mitigation, and review date. If a risk is accepted, record the business reason. If it is mitigated, test the mitigation. If it is transferred to a managed service, verify the exact responsibility that moved instead of assuming the service name moved all of it.

• Greenfield dependency on a closed service creates an immediate access and roadmap mismatch.
• Automatic branch deployment may hide the release controls a successor must reproduce.
• Migration cost is underestimated when teams compare only active container rates.
• Waiting for a final deadline can force a correlated, untested portfolio migration.

Alternatives and the decision

AWS recommends Amazon ECS Express Mode as a migration direction that preserves a compact deployment experience while provisioning an ECS service on Fargate, load balancing, scaling, and networking in the customer account. Standard ECS offers more control and an established ecosystem. Elastic Beanstalk fits supported application platforms over EC2. Lambda fits bounded event and request handlers. The best successor should be judged by the full App Runner contract—build through operations—not by container execution alone.

Do not select App Runner for a new architecture. Existing customers should not panic or perform a risky big-bang exit; AWS states they can continue using the service and create resources. Instead, stop increasing strategic dependence, inventory usage, preserve artifacts and configuration, select a successor, and migrate by business priority. Carry forward the service’s most important benefit: a small application contract and a platform-owned path from code to a healthy endpoint.

Use a short proof of architecture when uncertainty is material. Test the hardest requirement, the most important failure mode, and the expected cost driver—not another hello-world deployment. Compare AWS App Runner with the strongest alternative using the same workload and evidence. Record the decision, rejected options, assumptions, migration trigger, and date for review. Architecture remains healthy when a future team can understand both why the choice was correct and which changed fact would make it wrong.

A pragmatic 90-day adoption plan

Days 1–15: define the workload and responsibility map. Capture traffic or job shape, data sensitivity, availability and recovery objectives, latency, unit economics, dependencies, regional constraints, and team ownership. Build a thin threat model and request quota changes early. Select one representative path for the proof, not the easiest path. Establish a clean account, identity, network, artifact, encryption, and logging baseline before application convenience creates permanent exceptions.

Days 16–35: implement a production-shaped walking skeleton on AWS App Runner. Provision it from code, deploy an immutable artifact, integrate one real dependency, emit structured telemetry, and prove that a new team member can reproduce the environment. Exercise duplicate work, bad input, dependency timeout, and lost capacity. Measure cold and warm behavior where relevant, saturation, recovery backlog, and cost per successful business unit.

Days 36–60: harden delivery and recovery. Add policy checks, staged promotion, rollback or replacement, least-privilege runtime identity, secret rotation, data protection, retention, and symptom-based alerts. Restore from backup or recreate from artifacts in an isolated environment. Run a game day that includes an operator mistake and a compromised credential. Convert the findings into platform defaults and owned backlog items rather than a slide deck.

Days 61–90: place controlled production load on the service, review evidence with security, finance, and operations, and compare observed behavior with the original decision. Publish a paved-road module, dashboard, runbook, and exception process. Set capacity and cost review thresholds. Finally, write the exit criteria: the scale, feature, compliance need, economics, or organizational change that would trigger a move away from AWS App Runner. A reversible decision is easier to make well.