The New AWS Command-Line Interface
aws.typepad.com
The New AWS Command-Line Interface
1–10 of 71 posts
Re: The New AWS Command-Line Interface
#2Well done!
Re: The New AWS Command-Line Interface
#3FWIW, 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:
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 has any big advantages over Tim Kay's Perl aws?
Re: The New AWS Command-Line Interface
#4FWIW, 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…
Thanks for sharing, I'd never heard of this tool.
Indeed, an official supported friendly and easy-to-use CLI interface is long overdue.
Re: The New AWS Command-Line Interface
#5FWIW, 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…
Thanks for sharing, I'd never heard of this tool. Indeed, an official supported friendly and easy-to-use CLI interface is long overdue.
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.
Re: The New AWS Command-Line Interface
#6This 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
Re: The New AWS Command-Line Interface
#7About time.
More startups should realize that they could increase developer adoption of their products if also published shell script interfaces to their product. In fact, your startup should really start off as command line accessible and add the gui after.
Re: The New AWS Command-Line Interface
#8About time. More startups should realize that they could increase developer adoption of their products if also published shell script interfaces to their product. In fact, your startup should really start off as command line accessible and add the gui after.
"start off as command line accessible and add the gui after"
As much as I'd love this to be true, it is so wrong unless you are targeting other very technical users.
Most people I know (ie, potential customers) think anything in the command line is old/impossible to use/nerdy.
Re: The New AWS Command-Line Interface
#9Whilst this is a much better solution that the existing slow tools Amazon provided, I don't understand why this is being reported as if command-line tools for AWS are a new thing.
Command-line tools used to be your only option for managing AWS and Amazon always create their API and shell tools before the Console.
Re: The New AWS Command-Line Interface
#10About time. More startups should realize that they could increase developer adoption of their products if also published shell script interfaces to their product. In fact, your startup should really start off as command line accessible and add the gui after.
There have been CLI tools for some parts of AWS since the beginning. This release replaces a set of disparate tools (each with their own installation instructions and configuration issues) with a unified set.
> In fact, your startup should really start off as command line accessible...
I would argue that startups should always start at the API level and work upwards. At least that's what we did with AWS.