intro: Elastic Beanstalk is one of AWS’s easiest ways to deploy applications because it automatically handles provisioning, load balancing, scaling, and monitoring for you. You focus on your code — AWS handles the infrastructure.
According to AWS documentation, Elastic Beanstalk lets you deploy, monitor, and scale web applications with minimal setup.
Key Uses
Deploying web applications easily
You upload your code, and Elastic Beanstalk automatically handles provisioning EC2 instances, load balancers, scaling groups, and monitoring.
Automating infrastructure setup
It configures compute, load balancing, auto‑scaling, and health checks for you, reducing operational complexity.
Running apps in multiple languages:
Supports Go, Java, .NET, Node.js, PHP, Python, and Ruby out of the box.
Processing background tasks
It offers worker environments for processing SQS messages—useful for asynchronous or long‑running jobs.
Handling scaling automatically
It dynamically scales your environment based on demand, so your app can grow without manual intervention.
Note: In Azure, the closest equivalent to AWS Elastic Beanstalk is Azure App Service.
*1. Open the AWS Elastic Beanstalk Console
*
Sign in to the AWS Management Console
Search for Elastic Beanstalk
Click Create Application
*2. Create an Application
*
- Application Name
3. Choose a Platform
Elastic Beanstalk supports multiple platforms, including:
Node.js, Python, Java, .NET, PHP, Go, Docker
4. Upload Your Application Code
You have two options:
Option A: Use a Sample Application
Great for testing.
Elastic Beanstalk will deploy a pre‑built demo app.
Option B: Upload Your Code
Upload a .zip file containing your application source bundle.
5. Configure Your Environment
Elastic Beanstalk environments are collections of AWS resources (EC2, load balancers, scaling groups) that run your app
Service role: click on create role
A service role is an IAM role that Elastic Beanstalk itself assumes so it can manage your environment on your behalf. Think of it as the permissions Elastic Beanstalk needs to do its job. the service role is required so Elastic Beanstalk can: Create and manage AWS resources (like EC2 instances, load balancers, Auto Scaling groups), Monitor environment health, Write logs and metrics to CloudWatch, Access S3 buckets for application versions, Perform updates and deployments, Interact with other AWS services securely and automatically. Elastic Beanstalk cannot perform these actions unless it has a service role with the correct IAM managed policies attached.
Without a service role: Your environment cannot be created,
Elastic Beanstalk cannot provision or update resources, Health monitoring and logging will fail, Deployments may not work.
It’s essentially the “administrator badge” Elastic Beanstalk uses to operate your environment safely and automatically.
Go back to the Configure service access page and click on the refresh button and the role will automatically appear
Creating an EC2 instance profile: click on create
An EC2 instance profile is simply the identity your EC2 instance uses to access AWS services securely without storing credentials on the server. An EC2 instance profile gives your EC2 instance the permissions it needs to interact with other AWS services. It is the bridge between the EC2 instance and an IAM role.
Depending on the permissions in the attached IAM role, the instance can: Read/write objects in S3, Send logs to CloudWatch Logs, Pull secrets from Systems Manager Parameter Store, Access DynamoDB tables, Use X-Ray for tracing, Register with Elastic Load Balancing, Communicate with Elastic Beanstalk during deployments.
Note: Service Role → Permissions for Elastic Beanstalk itself.
Instance Profile → Permissions for the EC2 instance running your app.
- EC2 key pair - optional: open a AWS in a new tab and type key pair in the search bar. An EC2 key pair is used to securely connect to your EC2 instance. It acts as your login credential for the server.
Go back and select the key just created
Select default VPC
Enable Public IP address and select on subnet and click on next
select everything as default
Leave as default and select next
On Monitoring, Health reporting choose Enhanced and select and CloudWatch Custom Metrics and CloudWatch Custom Metrics - Environment then scroll down and click next
- Wait for Environment Health = “OK”
Once the environment is ready, you’ll see:
Health: OK
A green checkmark
A link to your running application
Click the link to open your deployed app in the browser.
Top comments (0)