AWSCLI和AWSEBCLI有什么区别? [英] What is the difference between AWSCLI and AWSEBCLI?
问题描述
"AWS命令行界面"和"AWS Elastic Beanstalk命令行界面"之间有什么区别?
What is the difference between "AWS Command Line Interface" and "AWS Elastic Beanstalk Command Line Interface"?
我是否都需要通过AWS Elastic Beanstalk部署Django项目?
Do I need both to deploy a Django project through AWS Elastic Beanstalk?
谢谢！
推荐答案
您应该从EBCLI开始，然后在EBCLI不足的地方介入AWSCLI.
You should start with the EBCLI and then involve the AWSCLI where the EBCLI falls short.
AWSCLI(aws)允许您从许多不同的服务中运行命令，而EBCLI(eb)特定于Elastic Beanstalk. EBCLI使许多繁琐的任务变得更容易，因为它比AWS CLI的动手次数少.我观察到，对于我的大多数任务，EBCLI足够了.否则，我将使用AWS CLI和AWS开发工具包.
The AWSCLI (aws) allows you to run commands from a bunch of different services, whereas, the EBCLI (eb) is specific to Elastic Beanstalk. The EBCLI makes a lot of tedious tasks easier because it is less hands on than the AWS CLI. I have observed, for most of my tasks, the EBCLI is sufficient; I use the AWS CLI and the AWS SDKs otherwise.
考虑部署Django应用.
Consider deploying your Django app.
-
您可以通过执行
eb init开始，该操作将带您进入交互式菜单集，从中可以选择区域和解决方案堆栈(Python).
You could start off by performing
eb init, which would take you through an interactive set of menus, from which you would choose your region, and solution stack (Python).
接下来，您将执行eb create，这将创建一个应用程序版本，并随后为您创建一个Elastic Beanstalk环境.
Next, you would perform eb create, which creates an application version and subsequently an Elastic Beanstalk environment for you.
以上两个EBCLI步骤转换为六个或更多AWSCLI步骤.此外，EBCLI对您隐藏的许多流程都涉及多个AWS服务，这使得通过AWS CLI复制EBCLI的任务变得更加繁琐且容易出错.
The above two EBCLI steps translate to half a dozen or more AWSCLI steps. Furthermore, a lot of the processes that the EBCLI hides from you involve multiple AWS services, which can make the task of replicating the EBCLI through the AWS CLI all the more tedious and error-prone.
这篇关于AWSCLI和AWSEBCLI有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
