命令"aws elasticbeanstalk"和"eb"有什么区别? [英] What is the difference between the commands `aws elasticbeanstalk` and `eb`?
问题描述
这两个命令aws elasticbeanstalk和eb似乎是执行相同操作的替代方法.它们的语法似乎有些不同，例如aws elasticbeanstalk create-environment但eb create.
The two commands aws elasticbeanstalk and eb appear to be alternative ways of doing the same things. They appear to have slightly different syntax, for example aws elasticbeanstalk create-environment but eb create.
但是，帮助页面(aws elasticbeanstalk create-environment help和eb create --help)的输出足够远，以至于它们似乎是分开开发的.
And yet the output of the help pages (aws elasticbeanstalk create-environment help and eb create --help) are sufficiently far that they seem to be developed separately.
aws elasticbeanstalk和eb使用brew install awscli和(在venv内部)pip install awsebcli安装在macOS上时，有什么区别?
What is the difference between aws elasticbeanstalk and eb when they are installed on macOS using brew install awscli and (inside a venv) pip install awsebcli?
推荐答案
但是，帮助页面的输出(aws elasticbeanstalk创建环境帮助和eb create --help)足够远，以至于它们似乎是分开开发的.
And yet the output of the help pages (aws elasticbeanstalk create-environment help and eb create --help) are sufficiently far that they seem to be developed separately.
您是正确的，它们完全不同，但是它们都是CLI. aws本质上与AWS开发工具包更具可比性.也就是说，如果我没记错的话，那么每个Beanstalk AWS开发工具包操作都会有一个AWS CLI命令，而每个eb命令都是多个AWS开发工具包命令的组合.
You are correct, they are completely different, but they are both CLIs. aws is essentially more comparable to the AWS SDKs. i.e. if I am not wrong, for every Beanstalk AWS SDK operation there is an AWS CLI command, whereas every eb command is a combination of multiple AWS SDK commands.
aws elasticbeanstalk命令来自AWSCLI，而eb来自EBCLI/AWSEBCLI.
The aws elasticbeanstalk command comes from the AWSCLI, whereas eb comes from the EBCLI/AWSEBCLI.
eb create是相当繁重的命令.它为您创建一个应用程序版本，将其存储在S3位置，执行必要的权限检查，实现与CodeCommit和CodeBuild的集成，允许指定配置模板名称作为您的环境的基础，支持在VPC内部创建环境等. ，然后创建一个环境.从这个意义上讲，它等同于浏览器中Beanstalk控制台的CLI.
eb create is quite a heavy command. It creates an application version for you, stores it at an S3 location, performs necessary permissions checking, enables integration with CodeCommit and CodeBuild, allows specifying configuration template names to base your environment on, supports creation of environments inside VPCs, etc, among other things, and then, of course, creates an environment. In this sense, it is the CLI equivalent of the Beanstalk console in the browser.
aws elasticbeanstalk create-environment仅创建环境.您必须先将应用程序版本上载到S3，然后才能执行命令.
aws elasticbeanstalk create-environment, however, merely creates an environment. You need to have had uploaded your app version to S3 prior to executing the command.
- In general,
eboperations are usually what you need, but theawsoperations have their time and place too. eboperations are tied to specific applications and require the directory in which they are being executed to beeb init-ed, whereasawsoperations are standalone operations that can be executed from any computer from any directory.
...使用brew install awscli和(在venv内)pip install awsebcli安装在macOS上吗?
... installed on macOS using brew install awscli and (inside a venv) pip install awsebcli?
关于 安装的两个命令-brew install ...版本可能并不总是安装eb的最新版本.从今天开始，它看起来像 homebrew 指向的是EBCLI的较旧版本.
As for what the two commands install is concerned -- the brew install ... version might not always install the latest version of eb. As of today, it looks like the homebrew is pointing to a fairly old version of the EBCLI.
我假设您的问题是关于virtualenvs中的brew install awsebcli vs pip install awsebcli.本质上，应该使用brew install ...方法使MacOS用户可以更轻松地轻松安装eb.恕我直言，这是不理想的，因为它会污染系统/库名称空间-就我个人而言，我想将我的软件包分隔开，而virtualenv为我提供了此功能.
I assume your question is about brew install awsebcli vs pip install awsebcli inside virtualenvs. Essentially, the brew install ... method is supposed to make it easier for MacOS users to install eb easily. This is not ideal, IMHO, because it pollutes the system/Library namespace -- personally, I'd like to keep my packages compartmentalized for which virtualenv provides me the ability.
这篇关于命令"aws elasticbeanstalk"和"eb"有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
