Elastic Beanstalk

Question 1

the purpose of Elastic Beanstalk

Answer 1

is to set developers free from creating and configuring aws resources and purely allow them to focus on application development.

Question 2

Elastic Beanstalk components

Answer 2

Application – collections of components like the environments, versions, and configurations;
Application version;
Environment;
Environment configuration setting and parameters that define the env and resources;
configuration template.

Question 3

Architectural concepts

Answer 3

Web server environment and worker environment
at any given point of time, each environment can support either of the environment tier. any given point of time, Elastic Beanstalk can handle only one auto scaling group.

Question 4

WEB SERVER ENVIRONMENT TIER

Answer 4

key component in an application. resources includes ELB, Auto Scaling group, one or more EC2 instance. Environment has a CNAME and an alias in the amazon Route 53 pointing to the ELB.

Question 5

Host Manager

Answer 5

aggregating events and metrics for retrieval using web console, API, or CLI;
Deploying the application;
Monitoring the application log files for critical errors;
Monitoring the application server;
Generating instance level events;
Patching instance components;
Rotating applications log files and publishing them to the S3 bucket.

Question 6

Worker environment tiers

Answer 6

includes Auto Scaling group, one or more EC2 instance, and an IAM role.

Question 7

Supported Platforms

Answer 7

Language: Java, .Net, PHP, Node.js, Python, Ruby, Go
Webservers; Containers: Apache, IIS, Java SE, Nginx, Passenger, Puma, Tomcat, Docker
Deployment Platforms: Git, IDEs(Eclipse, Visual Studio), Manual upload(WAR, ZIP)

Question 8

When to use?

Answer 8

1. spend minimal time learning and setting up infrastructure;
2. quick prototyping and testing;
3. increase developer productivity.
4. maintain some flexibility and control over the resources used to power your application.

Question 9

when not to use?

Answer 9

1. need complete control of resource configuration
2. existing applications can be difficult to fit in the Elastic Beanstalk “model”
3. installing dependencies in different than simplu using “apt-get” and can complicate things if you have a lot of dependencies.

Question 10

Can I have multiple versions of my application running at the same time?

Answer 10

Yes. AWS Elastic Beanstalk is designed to support multiple running environments, such as one for integration testing, one for pre-production, and one for production.

Question 11

How many applications can I run with AWS Elastic Beanstalk?

Answer 11

You can create up to 75 applications and 1,000 application versions. By default, you can run up to 200 environments across all of your applications. If you are also using AWS outside of AWS Elastic Beanstalk, you may not be able to create 10 environments since other limits may be hit sooner. For example, the default AWS account limits allow you to launch up to 20 EC2 instances and create up to 10 elastic load balancers. If you need more resources, complete the AWS Elastic Beanstalk request form, and your request will be promptly evaluated.