AWS Elastic Beanstalk

AWS Elastic Beanstalk can be used to quickly deploy and manage applications in the AWS Cloud.

Developers upload applications and Elastic Beanstalk handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.

AWS Elastic Beanstalk leverages Elastic Load Balancing and Auto Scaling to automatically scale your application in and out based on your application’s specific needs.

In addition, multiple availability zones give you an option to improve application reliability and availability by running in more than one zone.

Considered a Platform as a Service (PaaS) solution.

Supports Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker web applications.

Supports the following languages and development stacks:

  • Apache Tomcat for Java applications.
  • Apache HTTP Server for PHP applications.
  • Apache HTTP Server for Python applications.
  • Nginx or Apache HTTP Server for Node.js applications.
  • Passenger or Puma for Ruby applications.
  • Microsoft IIS 7.5, 8.0, and 8.5 for .NET applications.
  • Java SE.
  • Docker.
  • Go.

Integrates with VPC.

Integrates with IAM.

Can provision most database instances.

Allows full control of the underlying resources.

Stores your application files and, optionally, server log files in Amazon S3.

Application data can also be stored on S3.

Multiple environments are supported to enable versioning.

Changes from Git repositories are replicated.

Linux and Windows 2008 R2 AMI support.

Code is deployed using a WAR file or Git repository.

Use the AWS toolkit for Visual Studio and the AWS toolkit for Eclipse to deploy Elastic Beanstalk.

Fault tolerance within a single region.

By default applications are publicly accessible.

Provides integration with CloudWatch.

Can adjust application server settings.

Can access logs without logging into application servers.

Can use CloudFormation to deploy Elastic Beanstalk.

There is no additional charge for Elastic Beanstalk – you pay only for the AWS resources needed to store and run your applications.

Ready to test yourself? Click here to check out the free sample practice questions for AWS Compute

Also in AWS Compute

References

https://aws.amazon.com/elasticbeanstalk/details/

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html

https://aws.amazon.com/elasticbeanstalk/faqs/

https://aws.amazon.com/elasticbeanstalk/developer-resources/

https://aws.amazon.com/elasticbeanstalk/pricing/

4 thoughts on “AWS Elastic Beanstalk”

  1. Your team has a tomcat-based Java application you need to deploy into development, test
    and production environments. After some research, you opt to use Elastic Beanstalk due to
    its tight integration with your developer tools and RDS due to its ease of management.
    Your QA team lead points out that you need to roll a sanitized set of production data into
    your environment on a nightly basis. Similarly, other software teams in your org want
    access to that same restored data via their EC2 instances in your VPC .The optimal setup
    for persistence and security that meets the above requirements would be the following.
    A. Create your RDS instance as part of your Elastic Beanstalk definition and alter its
    security group to allow access to it from hosts in your application subnets.
    B. Create your RDS instance separately and add its IP address to your application’s
    DB connection strings in your code Alter its security group to allow access to it from hosts
    within your VPC’s IP address block.
    C. Create your RDS instance separately and pass its DNS name to your app’s DB
    connection string as an environment variable. Create a security group for client machines
    and add it as a valid source for DB traffic to the security group of the RDS instance itself.
    Amazon AWS-Solution-Architect-Associate : Practice Exam
    Leaders in it certification 48
    D. Create your RDS instance separately and pass its DNS name to your’s DB connection
    string as an environment variable Alter its security group to allow access to It from hosts In
    your application subnets.

  2. ratnapriya.rai@gmail.com

    I always get into doubt for Elastic beanstalk. I chose #5 as well. Is there some trick to get this right in first attempt?

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to Top