ChatGPT解决这个技术问题 Extra ChatGPT

Difference between Amazon EC2 and AWS Elastic Beanstalk [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. We don’t allow questions about professional server or networking-related infrastructure administration on Stack Overflow. You can edit the question so it’s on-topic for Stack Overflow. Closed 3 months ago. Improve this question

What is the difference between EC2 and Beanstalk? I want to know regarding SaaS, PaaS and IaaS.

To deploy a web application in Wordpress I need a scalable hosting service. If there anything better than my purpose, please let me know as well.

FYI - I want to host and deploy multiple Wordpress and Drupal sites.

I do not want to give more time for the server and focus on development. But the cloud hosting needs to be auto scalable.

I don't see how this is an opinion based question. There are definite differences between EC2 and ELB. They must have been designed to fill different niches or else why would AWS have them both? I think there is a place on this site for comparing and contrasting the two technologies. This shouldnt have been closed.
"What's the difference between EC2 and Elastic Beanstalk" is definitely not an option-based question or answer.
The bots running stack exchange need upgrades. This is not a coke-or-pepsi opinion question.
@Ahmmad Ismail I guess a better title could have helped, like "Difference between EC2 and EB" rather than "EC2 vs EB". Anyway, asking for differences between two solutions is clearly not "opinion biased".
@Balmipour Excellent suggestion. And clearly not opinion based.

N
Nam G VU

First off, EC2 and Elastic Compute Cloud are the same thing.

Next, AWS encompasses the range of Web Services that includes EC2 and Elastic Beanstalk. It also includes many others such as S3, RDS, DynamoDB, and all the others.

EC2

EC2 is Amazon's service that allows you to create a server (AWS calls these instances) in the AWS cloud. You pay by the hour and only what you use. You can do whatever you want with this instance as well as launch n number of instances.

Elastic Beanstalk

Elastic Beanstalk is one layer of abstraction away from the EC2 layer. Elastic Beanstalk will setup an "environment" for you that can contain a number of EC2 instances, an optional database, as well as a few other AWS components such as a Elastic Load Balancer, Auto-Scaling Group, Security Group. Then Elastic Beanstalk will manage these items for you whenever you want to update your software running in AWS. Elastic Beanstalk doesn't add any cost on top of these resources that it creates for you. If you have 10 hours of EC2 usage, then all you pay is 10 compute hours.

Running Wordpress

For running Wordpress, it is whatever you are most comfortable with. You could run it straight on a single EC2 instance, you could use a solution from the AWS Marketplace, or you could use Elastic Beanstalk.

What to pick?

In the case that you want to reduce system operations and just focus on the website, then Elastic Beanstalk would be the best choice for that. Elastic Beanstalk supports a PHP stack (as well as others). You can keep your site in version control and easily deploy to your environment whenever you make changes. It will also setup an Autoscaling group which can spawn up more EC2 instances if traffic is growing.

Here's the first result off of Google when searching for "elastic beanstalk wordpress": https://www.otreva.com/blog/deploying-wordpress-amazon-web-services-aws-ec2-rds-via-elasticbeanstalk/


Just to be clear, you mean you want to spend more time on development rather than configuring servers and everything like that?
It's a common pattern these days for companies to build Docker images of their applications and deploy those to a container management tool (Kubernetes, Mesos, Docker Swarm) running on a pool of EC2 instances. EC2 Container Service is Amazon's managed replacement for running your own Mesos cluster. It's a good solution if you're running multiple applications, and simplifies management and billing. If you're running a single application, unless you just like the Dockerized model, Beanstalk is a better option.
@JoshDavis To clarify your point at "Elastic Beanstalk doesn't add any cost on top of these resources that it creates for you", I would like to quote this "In fact, you aren't charged for Beanstalk itself--you are charged for the AWS resources you're using, such as S3, SNS, and EC2." from serverfault.com/a/401465/41015
Its a sad when the Amazon themselves cant explain their own products clearly. But it's true, they can't.
@Ephra dude, they leave EC2 because not everybody wants a preconfigured server, some enterprises prefer configure the servers themselves, due to security, automation reasons etc.
H
Harsha Reddy

EC2

Elastic Beanstalk


O
Osemenkhian Godstime

For a High level overview, EC2 Is an IaaS compute service; meaning the compute resources are generally managed by the cloud engineer that provisioned them

While Elastic Beanstalk is PaaS where you don't have to border too much about resource management. You just specify what you want and aws handles the task, by automation. For example provisioning a LAMP stack


EC2 is not infrastructure as code. It is "compute infrastructure on demand" which can be provisioned by IaC (like Terraform) but which can also be created manually (like through the AWS web interface)
Oh it should be my keyboard changing my words. I meant iaas infrastructure as a service