Overview
You are charged for the compute and memory resources used by your application. In addition, if you automate your deployments, you will pay a set monthly fee for each application that covers all automated deployments for that month. If you opt to deploy from source code, you will pay a build fee for the amount of time it takes App Runner to build a container from your source code.
Provisioned container instances
$0.007 / GB-hour*
When your application is deployed, you pay for the memory provisioned in each container instance. Keeping your container instance's memory provisioned when your application is idle ensures it can deliver consistently low millisecond latency
* The pricing of $0.007 / GB-hour is applicable for the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), and Europe (Ireland). For the Asia Pacific (Tokyo) Region, pricing is $0.009 / GB-hour.
Active container instances
$0.064 / vCPU-hour*
$0.007 / GB-hour*
When your application is processing requests, you switch from provisioned container instances to active container instances that consume both memory and compute resources. You pay for the compute and any additional memory consumed in excess of the memory allocated by your provisioned container instances. App Runner automatically scales the number of active container instances up and down to meet the processing requirements of your application. You can set a maximum limit on the number of active container instances your application uses so that costs do not exceed your budget. When your active container instances are idle, App Runner scales back to your provisioned container instances (the default is 1 provisioned container instance).
All container instance processing is billed per second, rounded up to the next nearest second. There is a one minute minimum charge for vCPU resources every time a provisioned container instance starts processing requests.
* The pricing of $0.007 / GB-hour and $0.064 / vCPU-hour is applicable for the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), and Europe (Ireland). For the Asia Pacific (Tokyo) Region, pricing is $0.009 / GB-hour and $0.081 / vCPU-hour.
Supported configurations
|
CPU
|
Memory values
|
|---|---|
|
0.25 vCPU
|
1 GB
|
|
0.25 vCPU
|
1 GB
|
|
0.5 vCPU
|
1 GB
|
|
1 vCPU
|
4GB
|
|
1 vCPU
|
4GB
|
|
1 vCPU
|
4GB
|
|
2 vCPU
|
6 GB
|
|
2 vCPU
|
6 GB
|
|
4 vCPU
|
12 GB
|
|
4 vCPU
|
12 GB
|
|
4 vCPU
|
12 GB
|
How pricing works
With App Runner, you deploy and run your applications in container instances, which consume compute and memory resources. When you create an application in AWS App Runner, you configure the amount of memory and vCPU required for your application to run. You also select concurrency, a scaling metric that represents the maximum number of simultaneous requests that can be processed by an active container instance. When your application is idle, you pay per GB of memory for provisioned container instances which keep your application warm and eliminate cold starts. When requests come in, your application responds in milliseconds, and you pay for the vCPU and memory consumed by your active container instances as your application is processing requests. You are only billed while your application is running, and App Runner makes it easy to pause and resume your application through the console, CLI, or API to help manage your costs. App Runner scales your active container instances up and down automatically to meet the processing demands of your application, and you pay only for the vCPU and memory used.
Add-ons
Automatic deployments
You can choose to opt-in to automatic deployments, a feature that builds a container image following changes in a source code deployment branch and subsequently triggers a deployment.
Build fee
You will pay a build fee for the amount of time it takes App Runner to build your application from your source code. You pay this build fee only for the first deployment of your application or when there is a change made to the source code.
Using other AWS services & transferring data
You may incur additional charges if your application uses other AWS services or transfers data. For example, if your application uses Amazon CloudWatch logs for application logging, you will be billed for CloudWatch usage.
Quick pricing examples
Example cost breakdown
Application configuration
- Container instance size: 1 vCPU & 2 GB
- Concurrency: 80 requests/active container instance
- Provisioned container instance count: 1 (default minimum)
Traffic
You are testing your application and your App Runner service sees traffic of 2 requests per second for 2 hours each day. App Runner scales the service to only 1 active container instance to process incoming requests and provisions the container instance's memory for 2 hours each day. You pause the service for the remaining 22 hours of the day to save costs.
Daily compute resources used to process requests
$0.13
2 hrs × 1 active container instance × [(1 vCPU × $0.064 vCPU-hour) + (2 GB × $0.007 GB-hour)] - 2 hrs x 1 provisioned container instance x (2 GB × $0.007 GB-hour) = $0.13
Daily provisioned container instance fee
$0.03
2 hrs × 1 provisioned container instance × (2 GB × $0.007 GB-hour) = $0.03
Total daily cost
$0.16
Total compute resources ($0.13) + provisioned container instance ($0.03) = $0.16
Total monthly cost
$4.80
Total daily cost ($0.16) × 30 days = $4.80
Application configuration
- Container instance size: 1 vCPU & 2 GB
- Concurrency: 80 requests/active container instance
- Provisioned container instance count: 1 (default minimum)
Traffic
You are running a lightweight latency sensitive API and your application sees sporadic requests of around 80 requests/second for 8 hours each day. App Runner scales the service to only 1 container to process incoming requests and provisions the container instance's memory for 24 hours each day.
Daily compute resources used to process requests
$0.51
8 hrs × 1 active container instance × [(1 vCPU × $0.064 vCPU-hour) + (2 GB × $0.007 GB-hour)] - 8 hrs x 1 provisioned container instance x (2 GB × $0.007 GB-hour) = $0.51
Daily provisioned container instance fee
$0.34
24 hrs × 1 provisioned container instance × (2 GB × $0.007 GB-hour) = $0.34
Total daily cost
$0.85
Total compute resources ($0.51) + provisioned container instance ($0.34) = $0.85
Total monthly cost
$25.50
Total daily cost ($0.85) × 30 days = $25.50
Application configuration
- Container instance size: 1 vCPU & 2 GB
- Concurrency: 80 requests/active container instance
- Provisioned container instance count: 1 (default minimum)
Traffic
Your are running a web application that is busy through the day and sees a varying request pattern with a peak of 800 requests/second for 3 hours. For 12 non-peak hours, the application sees a demand of 60 requests/second. App Runner scales the application up to 10 active container instances for peak hours, scales down to 1 active container instance for non-peak hours, and provisions memory for 24 hours each day.
Daily compute resources used to process requests
Peak hours: $2.30
For 3 peak hours, your application needs 10 active container instances to serve 800 requests/second as each instance has been configured to process 80 concurrent requests.
10 active container instances × 3 hrs × [(1 vCPU × $0.064 vCPU-hour) + (2 GB x $0.007 GB-hour)] - 1 provisioned container instance x 3 hrs x (2 GB x $0.007 GB-hour) = $2.30
Non-peak hours: $0.77
For 12 non-peak hours, your application needs 1 active container instance to serve 60 requests/second as each active container instance can process 80 requests/second
12 hrs × 1 active container instance × [(1 vCPU × $0.064 vCPU-hour) + (2 GB x $0.007 GB-hour)] - 12 hrs × 1 provisioned container instance x (2 GB x $0.007 GB-hour) = $0.77
Daily provisioned container instance fee
$0.34
24 hrs × 1 provisioned container instance × (2 GB × $0.007 GB-hour) = $0.34
Total daily cost
$3.40
Peak hour compute resources ($1.92) + Non-peak hour compute resources ($0.77) + provisioned container instance ($0.71) = $3.40
Total monthly cost
$102
Total daily cost ($3.40) x 30 days = $102