AWS Elastic Beanstalk Pricing
Why AWS Elastic Beanstalk?
There is no additional charge for AWS Elastic Beanstalk. You pay for the AWS resources (for example, Amazon EC2 instances or Amazon S3 buckets) you create. You only pay for what you use, as you use it; there are no minimum fees and no upfront commitments.
The cost of running an application on Elastic Beanstalk varies based on several factors, including the deployment mode you choose, the amount of compute needed to handle your traffic, the bandwidth your application consumes, and which database and storage options your application uses. Your principal costs are the compute that runs your application and the load balancing that distributes traffic to it. On the Cluster deployment mode, you also pay the standard charges for the managed Amazon EKS foundation that Elastic Beanstalk runs your application on.
Elastic Beanstalk Cost Details
Compute Type
Both deployment modes run your application on Amazon EC2 compute, billed at standard EC2 rates. You can use On-Demand Instances, Reserved Instances, Savings Plans, or Spot Instances.
Standard. You choose the Amazon EC2 instance type and size for your environment, and Elastic Beanstalk runs your application on dedicated instances: either a single instance, or an Auto Scaling group that scales with your traffic. You pay for the instances your environment runs.
Cluster. You specify the CPU and memory your application needs, and Amazon EKS Auto Mode provisions underlying EC2 instances to match. Because multiple applications can share nodes, a portfolio of applications can use less total compute than running each on its own dedicated instance, typically resulting in savings. Your compute cost tracks the CPU and memory you allocate across your running replicas. Amazon EKS Auto Mode adds a management fee on top of the underlying EC2 instance cost (see Amazon EKS Auto Mode below).
For current rates, see Amazon EC2 Pricing.
Load Balancing
Elastic Beanstalk uses Elastic Load Balancing to distribute incoming traffic to your application. You pay standard Elastic Load Balancing rates: an hourly charge for each load balancer plus a usage-based charge. Base costs are comparable across load balancer types, with Classic Load Balancers priced slightly higher than Application and Network Load Balancers.
Standard. A load balancer is provisioned for load-balanced environments. You can use an Application, Network, or Classic Load Balancer, billed at their standard rates. A single-instance environment has no load balancer and incurs no load balancing charge, since traffic reaches the instance directly.
Cluster. Each environment is fronted by one Application Load Balancer.
For current rates, see Elastic Load Balancing Pricing.
NAT Gateway
If your application runs in private subnets and needs outbound internet access, for example to call external APIs or download updates, a NAT gateway provides that access. You pay standard Amazon VPC NAT gateway rates: an hourly charge for the gateway plus a per-GB data-processing charge.
Standard. By default, environments run in public subnets and do not require a NAT gateway. A NAT gateway applies only if you choose to place your instances in private subnets.
Cluster. By default, Cluster mode places nodes in public subnets (using an internet gateway for outbound access), so no NAT gateway is provisioned by default. A NAT gateway applies only if you supply private subnets that need outbound internet access.
For current rates, see Amazon VPC Pricing.
Observability
Elastic Beanstalk sends metrics and logs to Amazon CloudWatch. You pay standard CloudWatch rates for the metrics, logs, dashboards, and alarms you use.
Standard. Basic instance metrics are available at no additional charge; you pay only for additional CloudWatch usage, such as detailed monitoring, custom metrics, and logs. Monitoring is typically a small part of the bill.
Cluster. Container- and pod-level metrics and logs are collected and sent to CloudWatch. Because these are metered per resource, monitoring cost scales with the number of pods and containers you run and can be more than on Standard. Amazon Managed Service for Prometheus is available as a lower-cost alternative for metrics at scale. You can also route metrics and logs to a supported third-party backend, in which case the third party bills you directly at its own rates and those charges do not appear on your AWS bill.
For current rates, see Amazon CloudWatch Pricing and Amazon Managed Service for Prometheus Pricing.
Cluster Mode-Specific Fees
Cluster mode runs your application on a managed Amazon EKS foundation, which adds two charges that Standard mode does not have.
Amazon EKS cluster fee
Each Amazon EKS cluster has a flat per-cluster hourly fee for the managed Kubernetes control plane. This fee is fixed per cluster and does not scale with instance size, node count, or the number of applications you run. Applications deployed into the same subnet share a cluster, so you generally pay one cluster fee rather than one per application; separate accounts or regions each get their own cluster.
For current rates, see Amazon EKS Pricing.
Amazon EKS Auto Mode
Amazon EKS Auto Mode provisions, scales, and patches the underlying nodes for you. It adds a management fee on top of the Amazon EC2 instance cost. The fee is based on the duration and type of the EC2 instances Auto Mode launches and manages, and like the instances themselves is billed per second with a one-minute minimum.
You can use any Amazon EC2 purchase option for the underlying instances (On-Demand, Reserved Instances, Savings Plans, or Spot). The Amazon EKS Auto Mode fee is charged independently of the purchase option you choose, so discounts on the EC2 instances do not reduce the Auto Mode management fee.
For current rates, see Amazon EKS Pricing (Amazon EKS Auto Mode).
Deploy on AWS with Elastic Beanstalk. Free for 6 Months. No platform fee
How the Free Tier works with Elastic Beanstalk
Free tier offer applies to AWS Elastic Beanstalk Standard Mode only. Offer valid for new AWS accounts during the 6-month AWS Free Tier period.
Estimated monthly resource cost of approximately $12/month for a minimal single-instance Standard deployment (1× t3.micro EC2 instance, 8 GB EBS root volume, public IPv4 address) is offset by the AWS Free Tier credit pool of USD 100–200 during the free period. Additional services used in this configuration including Amazon CloudFront (100 GB transfer + 1M requests/month), Amazon DynamoDB (25 GB storage), and AWS Certificate Manager, are Always Free within their monthly allowances at no charge, independent of the credit pool.
The base USD 100 credit is available to all new AWS accounts. An additional USD 100 credit is available by completing hands-on onboarding activities in the AWS Console. Completing these activities may incur minor charges deducted from your credit pool. The Free plan ends when the credit pool is exhausted or at 6 months, whichever comes first at which point the customer receives alerts as they approach full consumption of free tier or the time limit. They then have 90 days to convert to a paid account while their data is retained.
Elastic Beanstalk itself has no platform fee, no per-seat charge, and no pricing tier. Actual costs depend on the underlying resource and vary by region, instance type, traffic volume, and configuration. Adding a load balancer, managed database, or additional instances will increase monthly costs beyond the base ~$12/month estimate. See full pricing scenarios at [link].
Elastic Beanstalk Cluster Mode is not Free Tier eligible.
AWS Free Tier terms and conditions apply. See aws.amazon.com/free for complete details.
Free Tier Examples
-
Example 1: The free starter
This is the recommended minimal EB Standard deployment: a single-instance environment on a t3.micro, with managed HTTPS and a CDN via CloudFront (both Always Free), a serverless data store, and object storage. Depending on the application, a single t3.micro can handle roughly 25 requests per second.
What it runs well: prototypes, static websites, MVPs, personal projects, and low-traffic production apps that need proper HTTPS but not high availability or horizontal scaling.
Monthly cost breakdown (approximate, us-east-1)
Component Free-tier treatment Monthly cost 1 × t3.micro instance Credit-covered (billed at full rate) ~$7.50 8 GB gp3 root volume Credit-covered ~$0.64 Public IPv4 address Credit-covered ~$3.60 CloudFront (HTTPS + CDN + WAF + DNS + edge TLS) Always Free (Free plan: 100 GB + 1M requests) $0 ACM certificate (custom domain, on CloudFront) Always Free $0 DynamoDB (data) Always Free (within 25 GB / 25 WCU + 25 RCU) $0 CloudWatch (basic metrics) Free-vended $0 Data transfer out (< 100 GB) Always Free $0 S3 (small object storage) Credit-covered (minimal) ~$0–1 Total ~$12/month -
Example 2: Production facing web app
This is the shape for a public, production-facing web app that needs managed HTTPS and can scale across instances. It adds a load balancer in front of the app, with a free ACM certificate for HTTPS and (optionally) CloudFront as a CDN.
What it runs well: small business sites and any user-facing app.
Monthly cost breakdown (approximate, us-east-1)
Component Free-tier treatment Monthly cost 1 × t3.micro instance* Credit-covered (billed at full rate) ~$7.50 8 GB gp3 root volume* Credit-covered ~$0.64 Public IPv4 address* Credit-covered ~$3.60 Application Load Balancer Credit-covered ~$16–18 + LCU ACM certificate (on the ALB) Always Free $0 DynamoDB (data) Always Free $0 CloudWatch (basic metrics) Free-vended $0 S3 (small object storage) Credit-covered (minimal) ~$0–1 CloudFront (optional CDN) Always Free (Free plan: 100 GB + 1M requests) $0 Total ~$29/month * Scales with autoscaling. Elastic Beanstalk adds or removes whole instances based on load, so these per-instance components (compute, EBS root volume, and public IPv4) multiply with each instance — roughly ~$12.75/month per additional instance.
-
Example 3: Relational app
This is the shape for a public, production-facing web app that needs managed HTTPS and can scale across instances. It adds a load balancer in front of the app, with a free ACM certificate for HTTPS and (optionally) CloudFront as a CDN.
What it runs well: small business sites and any user-facing app.
Monthly cost breakdown (approximate, us-east-1)
Component Free-tier treatment Monthly cost 1 × t3.micro instance* Credit-covered (billed at full rate) ~$7.50 8 GB gp3 root volume* Credit-covered ~$0.64 Public IPv4 address* Credit-covered ~$3.60 Application Load Balancer Credit-covered ~$16–18 + LCU ACM certificate (on the ALB) Always Free $0 DynamoDB (data) Always Free $0 CloudWatch (basic metrics) Free-vended $0 S3 (small object storage) Credit-covered (minimal) ~$0–1 CloudFront (optional CDN) Always Free (Free plan: 100 GB + 1M requests) $0 Total ~$29/month * Scales with autoscaling. Elastic Beanstalk adds or removes whole instances based on load, so these per-instance components (compute, EBS root volume, and public IPv4) multiply with each instance — roughly ~$12.75/month per additional instance.
Cluster Mode Examples
Elastic Beanstalk charges no fee for Cluster mode itself. You pay for the underlying AWS resources it provisions in your account. The examples below trace how these charges add up for two deployment shapes, and how cost per application falls as you consolidate more applications onto one cluster.
The compute lines below apply two factors to the base instance cost: a roughly 23% efficiency gain from bin-packing multiple environments onto shared nodes (the × 0.77 factor), and the ~12% Amazon EKS Auto Mode management premium on the underlying EC2 instances (the × 1.12 factor).
Figures are illustrative, not current prices. They use on-demand pricing in US East (N. Virginia), a t3.medium-class workload per environment, and one cluster. Actual costs vary by Region, instance type, traffic, and configuration. Use the AWS Pricing Calculator for your own estimate.
-
Example 1 — one application, full lifecycle
Best for: an application with a full deployment lifecycle where the non-production environments benefit from sharing compute.
One application with five environments (production plus staging, dev, and QA) sharing a single cluster. Compute bin-packs across the environments onto a shared node pool, though each environment still has its own load balancer.
Component Monthly Cost Compute (5 envs, packed: 5 × $30 × 0.77 × 1.12)
~$129
8 GB gp3 root volume (per node)
~$3
Public IPv4 address (per node)
~$18
Application Load Balancer (1 per environment × 5)
~$90
Amazon EKS cluster fee (flat)
~$72
Container image storage (Amazon ECR)
~$1
Image builds (AWS CodeBuild)
~$2
CloudWatch (metrics and logs)
~$15
Data transfer out
~$2
Total ~$332/month
-
Example 2 — a portfolio of applications
Best for: a growing portfolio of containerized applications consolidated onto shared infrastructure.
Three applications, each with three environments (nine environments total), all consolidated onto one cluster. Compute packs densely across the whole portfolio and the fixed cluster fee is shared across many applications.
Component Monthly Cost Compute (9 envs, packed: 9 × $30 × 0.77 × 1.12)
~$233
8 GB gp3 root volume (per node)
~$6
Public IPv4 address (per node)
~$32
Application Load Balancer (1 per environment × 9)
~$162
Amazon EKS cluster fee (flat)
~$72
Container image storage (Amazon ECR)
~$2
Image builds (AWS CodeBuild)
~$3
CloudWatch (metrics and logs)
~$25
Data transfer out
~$3 Total ~$538/month
AWS service pricing
For more details on AWS service pricing, see the pricing section of relevant AWS service detail pages
Amazon EC2 Pricing
AWS database service pricing
If you want to use an AWS database service with Elastic Beanstalk, see links for pricing
Includes pricing for database instances, backup storage, and data transfer.
Include pricing for data storage, throughput capacity, and data transfer.
Includes pricing for storage, data processing, and data transfer.
