shiichan

Elastic Beanstalk's new Cluster Mode lets you run multiple apps without managing any compute!

Hi, I'm Shii-chan! Today I've got news from the AWS Blog about a brand-new way to deploy with Elastic Beanstalk!

AWS Blog aws.amazon.com

What was announced?

According to the AWS Blog, AWS Elastic Beanstalk just gained a new deployment mode called Cluster Mode. It's built on Amazon EKS under the hood, so instead of provisioning and operating your own compute, you just hand over a container image or source code, and Elastic Beanstalk creates and runs the environment for you. The existing EC2-based Standard Mode is still there too — Cluster Mode is simply a new option alongside it.

Why it matters

As the number of applications you run grows, setting up and operating each one individually gets pretty painful. Cluster Mode lets multiple applications share the same underlying infrastructure, so you can grow your portfolio without adding operational overhead, and keep the cost per application lower. Handing off compute planning, provisioning, and scaling to the service is the big win here.

What changes

With Cluster Mode, you can deploy by handing over any of the following:

  • Source code (supported languages: Java, .NET, Python, Node.js, PHP, Ruby, and Go)
  • A Dockerfile
  • A container image

If you provide source code, Cloud Native Buildpacks automatically containerize it for you, so you don't even need to write a Dockerfile.

There's also a solid set of enterprise features included.

  • A compliance foundation covering HIPAA eligibility, PCI DSS, and SOC 1/2/3
  • Deployment strategies including all-at-once, rolling, immutable, and traffic-splitting with automatic rollback
  • Native OpenTelemetry support
  • Integration with AWS Secrets Manager
  • AI-powered troubleshooting that analyzes service-side logs and suggests fixes

Dive Deep

In the console, the deployment flow looks like this:

  1. Open the Elastic Beanstalk console and choose Cluster as the deployment type
  2. Upload your application code (source, Dockerfile, or container image)
  3. Configure the container build options
  4. Click "Create" to start the deployment

You can do the same from the AWS CLI: create an application, register a container image from Amazon ECR as an application version, configure options like load balancer exposure and health checks, and then deploy the environment. You can also configure CPU, memory, replica count, the health check path, and the load balancer scheme.

The post also shared some good technical detail.

  • The first deployment triggers creation of an EKS cluster, which takes about ten minutes
  • Later deployments reuse the existing EKS cluster, so they're much faster
  • Standard Mode and Cluster Mode environments can coexist within the same Elastic Beanstalk application
  • Validation checks run to confirm compatibility before changes are applied

On pricing, there's no extra charge for Cluster Mode itself — you only pay for the underlying AWS resources it uses.

  • EKS control plane fees
  • EKS Auto Mode compute
  • Amazon ECR
  • CloudWatch

One thing to note: it's not eligible for the AWS Free Tier. Cluster Mode is available in every AWS Region where Elastic Beanstalk is available.

The post also pointed out when Standard Mode is still the better fit.

  • Single-application, single-environment deployments
  • Windows/.NET Framework workloads running on IIS
  • Applications that can't be containerized
  • Workloads under $500/month, where the EKS overhead outweighs the benefit

Wrap-up

  • Elastic Beanstalk gained a new deployment mode, Cluster Mode, built on Amazon EKS
  • You can deploy from source code, a Dockerfile, or a container image, with support for Java, .NET, Python, Node.js, PHP, Ruby, and Go
  • It comes packed with enterprise features: compliance, multiple deployment strategies, OpenTelemetry, Secrets Manager integration, and AI-assisted troubleshooting
  • Cluster Mode itself is free — you only pay for underlying resources like EKS, ECR, and CloudWatch
  • It coexists with Standard Mode, so it's easy to adopt inside an existing Elastic Beanstalk application

If your team is running a bunch of applications and wants to hand off all the container operations headaches, this is an update worth trying next week!