# AWS Elastic Beanstalk

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk

> AWS Elastic Beanstalk is a cloud deployment service that automates the process of deploying applications in the AWS cloud, allowing developers to upload their code and have the service automatically handle the deployment details such as resource provisioning, load balancing, auto-scaling, and monitoring.

Practice exams covering AWS Elastic Beanstalk: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional).

## 10 key features of AWS Elastic Beanstalk

AWS Elastic Beanstalk is a managed service that provides automated deployment and scaling for web applications and services, integrating with various AWS services for monitoring, load balancing, and auto-scaling, while handling environment configuration and management.

1. **Easy Deployment**: AWS Elastic Beanstalk allows developers to easily deploy and manage applications in the cloud without worrying about the infrastructure that runs those applications. Users simply upload their code, and Elastic Beanstalk automatically handles the deployment, from capacity provisioning, load balancing, auto-scaling to application health monitoring.
2. **Developer Productivity**: It boosts developer productivity by simplifying the process of deploying and managing applications. Developers can focus on writing code, not managing the infrastructure.
3. **Auto-Scaling**: Elastic Beanstalk can automatically scale your application up and down based on your application's specific need using easily adjustable auto-scaling settings.
4. **Integrated with AWS Services**: Elastic Beanstalk is integrated with Amazon Web Services, giving users access to services like Amazon RDS, Amazon S3, Amazon CloudWatch, Amazon DynamoDB, and Elastic Load Balancing.
5. **Language and Platform Flexibility**: Supports a wide range of programming languages and developer tools such as Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker, giving developers the flexibility to use the languages and platforms they know and love.
6. **Environment Management**: Provides easy tools to manage environment configurations and deploy version histories, enabling simple rollbacks to previous versions and fast configuration changes.
7. **Application Health Monitoring**: Offers detailed application health monitoring and alerts, allowing users to detect and fix issues quickly. This ensures high availability and performance of applications.
8. **Security**: Integrates with AWS Identity and Access Management (IAM), allowing users to set up permissions and securely access other AWS resources from their applications.
9. **Managed OpenTelemetry Integration**: Cluster Mode provides managed OpenTelemetry integration.
10. **AI-Powered Environment Analysis**: AI-powered environment analysis sends environment events and logs to Amazon Bedrock for processing. Processing occurs in your account for Standard environments and in the Elastic Beanstalk service account for Cluster environments.

## Where AWS Elastic Beanstalk is used

AWS Elastic Beanstalk is efficiently used for deploying and managing applications in the cloud without worrying about the infrastructure, ideal for developers wanting quick deployments, seamless environment updates, and application scaling.

1. **Rapid Deployment of Web Applications**: AWS Elastic Beanstalk enables developers to quickly deploy and manage web applications and services without worrying about the infrastructure. By uploading their code, Elastic Beanstalk automatically handles the deployment, from capacity provisioning, load balancing, and auto-scaling to application health monitoring. This use case is ideal for developers who want to deploy their applications swiftly without delving into the complexities of infrastructure management.
2. **Environment Management for Microservices**: Elastic Beanstalk facilitates the management of environments for microservices architecture. Developers can easily deploy each microservice as a separate application in its own environment, allowing for independent scaling, updates, and management. This approach simplifies the complexities associated with microservices architecture, making it accessible for teams to efficiently manage and evolve their microservice-based applications.
3. **Automated Application Scaling**: Elastic Beanstalk supports automatic scaling of applications based on predefined rules or real-time demand. This use case is critical for applications that experience variable workloads, ensuring that they maintain optimal performance during peak times while reducing costs during periods of low demand. Elastic Beanstalk's auto-scaling feature evaluates the load and automatically adjusts the number of instances, keeping the application stable and responsive without manual intervention.
4. **Seamless Integration with AWS Services**: Elastic Beanstalk offers seamless integration with other AWS services, such as Amazon RDS for database services, Amazon S3 for storage, and Amazon CloudWatch for monitoring and logging. This integration enables developers to enhance their applications with powerful AWS services easily, without complex configuration, fostering an environment where developers can focus on adding value through their application's functionality rather than its infrastructure.
5. **DevOps Automation**: AWS Elastic Beanstalk supports DevOps practices by automating the deployment process, facilitating continuous integration and continuous deployment (CI/CD) workflows. Through integration with AWS CodeBuild, AWS CodePipeline, and other CI/CD tools, Elastic Beanstalk simplifies the end-to-end development and deployment process, making it easier for development teams to release new features and updates efficiently, with minimized risk and enhanced productivity.

## How AWS Elastic Beanstalk is priced

AWS Elastic Beanstalk itself does not charge an additional fee but you pay for the AWS resources (e.g., EC2 instances, S3 storage) provisioned to run your applications.

- **No Additional Charge for Elastic Beanstalk**: AWS Elastic Beanstalk itself does not incur any direct charges. Users only pay for the AWS resources (e.g., EC2 instances, S3 storage, RDS database instances) they provision to run their applications. Elastic Beanstalk efficiently manages these resources.
- **On-Demand Instances**: Users pay for EC2 instances by the hour without any long-term commitments or upfront payments. Pricing varies based on the instance type used, region, and operating system.
- **Reserved Instances**: To save on long-term costs, users can reserve instances for a 1 or 3-year term with All Upfront, Partial Upfront, or No Upfront payment options and discounted rates compared with equivalent On-Demand usage.
- **Spot Instances**: Users can access unused EC2 capacity at potentially lower rates without bidding. Spot instance pricing varies and instances can be terminated by AWS with very short notice if demand increases.
- **Additional AWS Resources**: Other resources such as S3 for storage, RDS for databases, and any other used AWS services are billed according to their respective pricing models. Always consider these costs when estimating the total price of using Elastic Beanstalk.
- **Savings Plans**: Savings Plans are an available purchase option for the underlying EC2 compute in both Standard and Cluster deployment modes.
- **Amazon EKS Cluster Fee**: Cluster Mode incurs a flat hourly fee per Amazon EKS cluster for its managed Kubernetes control plane, independent of instance size, node count, or application count. Applications deployed into the same subnet share a cluster.
- **Amazon EKS Auto Mode Management Fee**: Amazon EKS Auto Mode adds a management fee on top of the underlying EC2 instance cost, based on instance type and duration and billed per second with a one-minute minimum. EC2 purchase-option discounts do not reduce this management fee.
- **AWS Free Tier**: The Free Tier offer applies only to Standard Mode for new AWS accounts during their six-month AWS Free Tier period. The USD 100–200 credit pool can offset the estimated resource cost of a minimal single-instance Standard deployment.
- **AI Analysis Model Invocations**: AI analysis in Standard environments invokes Amazon Bedrock in your account and incurs standard Bedrock model-invocation charges. In Cluster environments, Elastic Beanstalk invokes Bedrock in its service account, and you are not charged for model invocations.

## Services AWS Elastic Beanstalk works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Provides scalable computing capacity in the cloud for running applications.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Used to store application versions, log files, and other assets.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Offers managed relational database services for easy setup and scaling.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Enables deployment of applications in a secure, isolated cloud environment.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: Elastic Beanstalk environments can serve as origins for CloudFront distributions. CloudFront can cache application content at edge locations while forwarding dynamic requests to the environment.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Elastic Beanstalk publishes environment and application health metrics to CloudWatch and can stream instance logs and enhanced health logs to CloudWatch Logs. Environments also use CloudWatch alarms to trigger scaling based on configured metrics.
- **[Amazon CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-codeguru)**: Java applications on Elastic Beanstalk can use the CodeGuru Profiler agent to collect runtime profiles. These profiles help identify expensive methods and performance bottlenecks in applications running on environment instances.
- **[Amazon Corretto](https://blowstack.com/tools/cloud-services-hub/amazon-corretto)**: Elastic Beanstalk provides Java SE and Tomcat platform branches that use Amazon Corretto. These platforms supply the Java runtime for deployed applications, with runtime updates delivered through Elastic Beanstalk platform releases.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: Elastic Beanstalk configuration files can provision DynamoDB tables alongside an environment. Worker environments also use a DynamoDB table to coordinate leader election for periodic tasks.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: Elastic Beanstalk creates and manages an Auto Scaling group for an EC2-based environment. The group replaces unhealthy instances and adjusts capacity according to the environment's scaling settings.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: Elastic Beanstalk environment instances use EBS root volumes, with environment settings controlling properties such as volume type, size, IOPS, and throughput. Additional EBS volumes can be configured through instance block device mappings.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: Elastic Beanstalk Docker environments can pull application images from private ECR repositories. The environment's instance role supplies the permissions needed to authenticate and download the images during deployment.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: Elastic Beanstalk's ECS-managed Docker platform uses ECS to run and coordinate multiple containers on environment instances. A Dockerrun.aws.json file defines the containers, ports, volumes, and other task settings.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: Elastic Beanstalk supports configuration files that create or mount an EFS file system on environment instances. This provides shared, persistent files that remain available as instances are replaced or the environment scales.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Elastic Beanstalk Cluster mode runs applications on EKS and manages deployment, load balancing, health monitoring, and scaling. Multiple Elastic Beanstalk environments can share an EKS cluster.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: Elastic Beanstalk configuration files can provision an ElastiCache cluster with an environment and configure the security groups needed to reach it. Applications can use the cache for shared session storage or frequently accessed data.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Elastic Beanstalk sends deployment, environment status, and health events to EventBridge. Rules can match these events to trigger notifications or automated responses to deployment failures and health changes.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Elastic Beanstalk environments can be addressed through custom domains using Route 53 records. For supported environment endpoints, an alias record can route a domain directly to the environment.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: Elastic Beanstalk can publish environment notifications to an SNS topic configured in the environment's notification settings. Subscribers can receive messages about operational events such as environment creation and deployment failures.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: Elastic Beanstalk worker environments use SQS queues to receive background jobs. A daemon on each worker instance reads messages and delivers their contents to the application through local HTTP requests.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: Elastic Beanstalk load balancer listeners can use ACM certificates to terminate HTTPS connections. The certificate is selected through the environment's listener configuration to secure traffic to the application.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: CloudFormation provides resource types for Elastic Beanstalk applications, application versions, environments, and configuration templates. Elastic Beanstalk also uses CloudFormation stacks to provision and manage environment resources.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records Elastic Beanstalk API activity, including environment creation, configuration changes, and application version operations. These records provide an audit trail of who changed an environment and when.
- **[AWS CodeCommit](https://blowstack.com/tools/cloud-services-hub/aws-codecommit)**: Elastic Beanstalk's EB CLI has built-in CodeCommit integration for associating an application with a repository and branch. Deployments can use the committed source from that repository rather than packaging the local working directory.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: Elastic Beanstalk is a supported deployment action provider in CodePipeline. A pipeline can deliver an application artifact to a selected Elastic Beanstalk application and environment whenever a new release passes earlier stages.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records supported Elastic Beanstalk resources and their configuration changes. Managed rules can check environment settings such as enhanced health reporting, managed platform updates, and log streaming.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Elastic Beanstalk uses IAM service roles to manage environment resources and instance profiles to grant permissions to applications and agents on EC2 instances. IAM policies also control who can create environments, deploy application versions, and change configuration.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: When Elastic Beanstalk retrieves environment variable values from secrets or parameters encrypted with customer managed KMS keys, its instance role needs permission to decrypt them. KMS key policies and IAM permissions therefore control whether those protected values can be loaded during deployment.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Elastic Beanstalk supports interface VPC endpoints for its service API and enhanced health service. These endpoints let clients and environment instances communicate with those services privately without an internet gateway or NAT device.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: Elastic Beanstalk resources support tags that can be used with Resource Groups and Tag Editor to organize and find applications and environments. Tag-based groups can collect related Elastic Beanstalk resources with the other resources belonging to an application.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Elastic Beanstalk can retrieve Secrets Manager values and expose them as application environment variables using its environment secrets configuration. This avoids placing plaintext credentials in application source bundles or ordinary environment configuration.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub includes controls that evaluate Elastic Beanstalk environment settings, including enhanced health reporting, managed platform updates, and CloudWatch Logs streaming. Failed checks produce findings that identify environments needing configuration changes.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Elastic Beanstalk assumes IAM service roles through STS to obtain temporary credentials for managing environment resources. This allows it to perform authorized deployment and health-management operations without long-lived access keys.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: Elastic Beanstalk applications can receive Shield Advanced protection through their supported environment load balancers. Registering those load balancers as protected resources adds advanced DDoS protection to the application's public entry point.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Step Functions can invoke Elastic Beanstalk API actions through AWS SDK service integrations. A workflow can update an environment, poll its status, and branch into recovery steps if a deployment does not complete successfully.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Elastic Beanstalk can retrieve Systems Manager Parameter Store values for application environment variables, including encrypted parameters when the required permissions are granted. Systems Manager also provides an automation runbook for troubleshooting Elastic Beanstalk environment problems.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: An Elastic Beanstalk environment using an Application Load Balancer can be protected by associating an AWS WAF web ACL with that load balancer. WAF then filters incoming application requests using rules such as rate limits and managed protections against common web attacks.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: Elastic Beanstalk provides a configuration option to run the X-Ray daemon on supported environment platforms. Instrumented applications send trace data to the daemon so requests and downstream calls can be analyzed in X-Ray.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: Elastic Beanstalk creates and configures a load balancer for load-balanced environments, or can use a shared Application Load Balancer. Listener, health check, routing, and connection settings determine how traffic reaches application instances.

## What is AWS Elastic Beanstalk

AWS Elastic Beanstalk is a high-level service provided by Amazon Web Services (AWS) that offers cloud deployment and management solutions, allowing developers to easily deploy and manage applications in the AWS cloud without worrying about the infrastructure that runs those applications. It is particularly well-suited for developers who want to deploy their applications quickly without dealing with the complexity of the AWS infrastructure services directly.

The service automates the details of capacity provisioning, load balancing, scaling, and application health monitoring, essentially providing a smoother path from code to a fully functioning application on the web. When a developer deploys an application using Elastic Beanstalk, the service automatically handles the deployment, from capacity provisioning, load balancing, auto-scaling to application health monitoring.

At its core, Elastic Beanstalk relies on familiar AWS services such as Amazon EC2 for virtual computing environments, Amazon S3 for storage, Amazon Simple Notification Service for notifications, and Amazon CloudWatch for monitoring. However, it abstracts these services to a level that makes it easier for users to deploy applications without needing to become experts in AWS infrastructure. The process begins when developers upload their application code to Elastic Beanstalk using the AWS Management Console, a Command Line Interface (CLI), or a Visual Studio or Eclipse plugin. Elastic Beanstalk then automatically handles the deployment, from the execution of the code, application server configuration, database provisioning if needed, and so forth.

Elastic Beanstalk offers two deployment modes: Standard on EC2 for single applications and Windows/.NET Framework workloads, and Cluster, powered by Amazon EKS, for multiple applications that share infrastructure.

The default environment quota is 200 per account per Region across all applications, not per application. This quota is adjustable.

The service not only deploys the application, but it also automatically manages the application's lifecycle, including updates, monitoring, logging, and scaling. Elastic Beanstalk supports a wide range of developer platforms, including Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker, among others. This flexibility means that most applications can be easily adapted to run on the service.

The default application-version quota is 1,000 per account per Region across all applications, not per application. This quota is adjustable.

Additionally, Elastic Beanstalk provides developers with the tools to customize the AWS resources powering their application. While the service simplifies the deployment process, it does not limit developers' control over the AWS resources. If needed, developers can still access the underlying resources and configure them according to their application's specific requirements.

One of the key advantages of using Elastic Beanstalk is its emphasis on scalability. The service can automatically scale an application up or down based on policies defined by the developer. For instance, if the application requires more computing resources to handle increased load, Elastic Beanstalk can automatically spawn additional Amazon EC2 instances to meet the demand. Similarly, the service can scale down resources during periods of low traffic, helping to optimize costs. Moreover, the health monitoring features of Elastic Beanstalk ensure that developers are always aware of their application's performance and can react swiftly to any issues that may arise.

In summary, AWS Elastic Beanstalk offers a convenient and efficient way for developers to deploy and manage applications on the AWS cloud. By abstracting much of the complexity of AWS infrastructure services, it allows developers to focus on coding and innovation rather than infrastructure management. At the same time, it provides the flexibility and control needed for complex applications, making it a versatile tool for startups, enterprises, and every developer in between.

## Concepts related to AWS Elastic Beanstalk

- [Rolling Deployment](https://blowstack.com/tools/cloud-concepts-hub/rolling-deployment): Rolling deployment updates an application in successive batches while keeping part of the existing deployment available to serve traffic.
- [Compute](https://blowstack.com/tools/cloud-concepts-hub/compute): Compute is the processing capacity used to execute software, perform calculations, and run applications.
- [All-at-Once Deployment](https://blowstack.com/tools/cloud-concepts-hub/all-at-once-deployment): All-at-once deployment releases a new application version to the entire targeted environment in a single deployment batch rather than through staged updates.
- [Environment Isolation](https://blowstack.com/tools/cloud-concepts-hub/environment-isolation): Environment isolation separates development, testing, staging, and production resources so that activity in one environment does not unintentionally affect another.
- [Monolithic Architecture](https://blowstack.com/tools/cloud-concepts-hub/monolithic-architecture): Monolithic architecture organizes an application's core functionality into a single deployable unit whose components are released together.

## AWS Elastic Beanstalk exam questions

Real practice exam questions on AWS Elastic Beanstalk, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A development team is moving an existing Java web application to AWS. The team wants to upload its application package and have AWS automatically provision virtual servers, configure load balancing, scale capacity, and monitor application health. Developers must retain access to the underlying servers for troubleshooting. Which AWS service meets these requirements with the LEAST infrastructure configuration effort?

**Correct answer:** AWS Elastic Beanstalk

**Explanation:** Elastic Beanstalk accepts application code and manages provisioning, load balancing, automatic scaling, and application health monitoring. Developers retain access to the underlying instances when needed.

### Question 2 (DVA-C02)

**Question:**

A company deploys a web application through a CI/CD pipeline to a load-balanced AWS Elastic Beanstalk environment. Application bundles include installation scripts for native dependencies. Previous deployments updated existing instances in batches, and failed installations left some instances with partially updated dependencies.

For future releases, the developer must configure application deployments so that dependency installation occurs only on newly provisioned instances. The current instances must continue serving traffic without modification until the replacement fleet passes health checks. If deployment fails, Elastic Beanstalk must discard the replacement instances and leave the current fleet running. The company has sufficient quota for temporary additional capacity and wants to retain a single Elastic Beanstalk environment.

Which deployment configuration meets these requirements?

**Correct answer:** Set DeploymentPolicy to Immutable.

**Explanation:** An immutable application deployment launches replacement instances in a temporary Auto Scaling group and deploys the new version to them without updating the original instances. After the replacement instances pass health checks, Elastic Beanstalk completes the transition and terminates the old instances. If deployment fails, it terminates the replacement instances and preserves the original fleet.

### Question 3 (DOP-C02)

**Question:**

A company deploys a stateless API to an AWS Elastic Beanstalk environment containing 12 EC2 instances behind an Application Load Balancer. The CI/CD pipeline updates three existing instances at a time and waits for the batch to become healthy before continuing. The environment cannot provision additional instances, and at least nine instances must remain available during recovery.

A deployment fails after some batches have completed. The deployment is no longer running, and the environment now contains instances running two different application versions. Engineers determine that the new version has an application defect. The previous version's deployment bundle is still available in Elastic Beanstalk. Neither the platform configuration nor the database schema changed, and both versions are compatible with the current database.

Which recovery action should a DevOps engineer take to restore the previous version throughout the environment while meeting the capacity requirements?

**Correct answer:** Deploy the previous application version to the existing environment, retaining the deployment policy and batch size of three instances.

**Explanation:** A failed rolling deployment can leave instances running different application versions. Redeploying the previous version updates the fleet in successive batches. Retaining the three-instance batch size leaves nine instances available while each batch is updated and requires no additional instances. The unchanged platform and compatible database allow the previous application version to run correctly.

## Practice AWS Elastic Beanstalk in a full exam

Questions on AWS Elastic Beanstalk in each practice exam, with every answer option and an explanation for each:

- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 11 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 5 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 3 questions

## Learn AWS Elastic Beanstalk in lessons

4 short lessons on AWS Elastic Beanstalk in 2 certification courses.

- CLF-C02: AWS CloudFormation vs AWS Elastic Beanstalk (Premium), https://app.blowstack.com/lessons/aws-cloudformation-vs-aws-elastic-beanstalk-clf-c02
- DOP-C02: AWS Elastic Beanstalk: application deployment strategies (Premium), https://app.blowstack.com/lessons/aws-elastic-beanstalk-application-deployment-strategies-dop-c02
- CLF-C02: AWS Elastic Beanstalk: deploying code to managed environments (Premium), https://app.blowstack.com/lessons/aws-elastic-beanstalk-deploying-code-to-managed-environments-clf-c02
- DOP-C02: AWS Elastic Beanstalk vs AWS CodeDeploy: deployment responsibility (Premium), https://app.blowstack.com/lessons/aws-elastic-beanstalk-vs-aws-codedeploy-deployment-responsibility-dop-c02
