I think the only thing "new" here is aws-cli hitting version 1.0.0. It's been the recommended aws command line tool for quite a while now. I've personally used it for the last 6 months.
The New AWS Command-Line Interface
31–40 of 71 posts
Re: The New AWS Command-Line Interface
#32FWIW, I've been using the aws command-line tool by Tim Kay for over 6 years. It's only Perl and cURL. A single self-contained script with no other dependencies. It's been rock solid in production that whole time: http://timkay.com/aws/ The syntax looks quite the same, but Amazon's awscli Python installer has loads of dependencies. I'll have to see if it's worth switching. Anyone already know if Amazon's new CLI thing…
> The syntax looks quite the same, but Amazon's awscli Python installer has loads of dependencies. I'll have to see if it's worth switching. Why are the dependencies a problem? By combining a handful of smaller, focused modules that each do something well, you can end up with something better than if you were to re-invent the wheel for every need. AWS and the Python dev team are doing a heck of a job on botocore, and…
The issue is that they can't release them all compiled into one thing. Instead the dependencies have to pollute the rest of the operating system. This is one of those things that Java got right and virtually everything else except npm (local node_modules) got wrong out of the gate.
I'd love to have a simple way to package python apps that depend on other python and native libraries without having to install things separately.
Re: The New AWS Command-Line Interface
#33As a semi-technical small business user of AWS I really wonder why so few resources seem to be put to the AWS GUI. For example, why is autoscaling not part of the GUI/AWS console? It's one of the most basic functions and it beggars belief that in this day and age it is done through the command line only. I'd rather not have to pay extra for Ylastic or some other hack when I'm sure Amazon can throw together even the most basic UI in a few weeks.
Re: The New AWS Command-Line Interface
#34Earlier quoted context omitted.
actually, ec2-api-tools has been provided for years: http://aws.amazon.com/developertools/351 - I just didn't like the command interface provided by them. Haven't had time to check out the new CLI yet but it looks much better at quick glance.
Unfortunately it doesn't support tab-completion... which would be nice given that there's oodles of ec2 commands.
The new AWS CLI supports tab completion. You need to configure it using the info found at http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-get...
Re: The New AWS Command-Line Interface
#35FWIW, I've been using the aws command-line tool by Tim Kay for over 6 years. It's only Perl and cURL. A single self-contained script with no other dependencies. It's been rock solid in production that whole time: http://timkay.com/aws/ The syntax looks quite the same, but Amazon's awscli Python installer has loads of dependencies. I'll have to see if it's worth switching. Anyone already know if Amazon's new CLI thing…
> The syntax looks quite the same, but Amazon's awscli Python installer has loads of dependencies. I'll have to see if it's worth switching. Why are the dependencies a problem? By combining a handful of smaller, focused modules that each do something well, you can end up with something better than if you were to re-invent the wheel for every need. AWS and the Python dev team are doing a heck of a job on botocore, and…
I just like knowing what's on my system.
`pip install awscli` just installed 26 other modules besides awscli. Now I feel a little obliged to go check out those 26, as well, to see what they are.
I agree about not re-inventing the wheel. But the amount of stuff installed is definitely a considering factor when choosing between two seemingly identical scripts.
Re: The New AWS Command-Line Interface
#36The new CLI looks like a massive improvement over the old one, but ironically I will probably still prefer boto + ipython because of the very robust autocompletion.
I wonder if the fish shell could autocomplete the commands; it has a feature to generate autocompleation settings from man pages.
Re: The New AWS Command-Line Interface
#37Long-time user of boto[1] here. It has been the go to library to hook your python code into AWS and has a fairly active following on github[2].
One API point that I've found lacking in boto is a "sync" command for S3. Take a source directory and a target bucket and push up the differences ala rsync, that's the dream. Boto gives you a the ability to push/get S3 resources, but I've had to write my own sync logic.
So, the first thing I went digging into is the S3 interface of the new CLI, and to my surprise, they've put a direct sync command on the interface[3], huzzah! Their implementation is a little wacky though. Instead of using some computed hashes, they are relying on a combination of file modtimes and filesize. Weird.
Anyways, glad to see AWS is investing in a consistent interface to make managing their services easier.
[1] http://boto.readthedocs.org/en/latest/index.html
[2] https://github.com/boto/boto
[3] http://docs.aws.amazon.com/cli/latest/reference/s3/sync.html...
Re: The New AWS Command-Line Interface
#38This latest release marks a milestone in the transition from the old Java based tools, to the new Python ones. Mitch Garnaat[1] who built and maintained boto over the years was picked up by Amazon last year and since has been building out botocore[2] - which the aws-cli[3] tools use under the hood. [1] https://github.com/garnaat [2] https://github.com/boto/botocore [3] https://github.com/aws/aws-cli
Thank you for this no-nonsense layout of the situation. =) Can you elaborate more on how this FOSS Github-er was picked up by Amazon? It sounds like a story that many here would like to replicate!
I'm afraid I don't actually know anything more than the intertubes can tell you :)
I noticed it had happened sometime last year, and thought I'd share what little I know.
Re: The New AWS Command-Line Interface
#39As a semi-technical small business user of AWS I really wonder why so few resources seem to be put to the AWS GUI. For example, why is autoscaling not part of the GUI/AWS console? It's one of the most basic functions and it beggars belief that in this day and age it is done through the command line only. I'd rather not have to pay extra for Ylastic or some other hack when I'm sure Amazon can throw together even the m…
[deleted]
Re: The New AWS Command-Line Interface
#40Long-time user of boto[1] here. It has been the go to library to hook your python code into AWS and has a fairly active following on github[2]. One API point that I've found lacking in boto is a "sync" command for S3. Take a source directory and a target bucket and push up the differences ala rsync, that's the dream. Boto gives you a the ability to push/get S3 resources, but I've had to write my own sync logic. So, t…
Good to hear this feedback. I work for AWS; I will pass this to the team.
Feel free to shoot me an email: simone attt amazon do0tcom if you have more comments.
Thanks!