aws-cli tools broken in EC2 build

When I run aws --version in a standard SLES 11.3 AWS build with a public IP, I get the following trace:

Traceback (most recent call last):
File “/usr/bin/aws”, line 23, in
File “/usr/bin/aws”, line 19, in main
return awscli.clidriver.main()
File “/usr/lib64/python2.6/site-packages/awscli/”, line 45, in main
driver = create_clidriver()
File “/usr/lib64/python2.6/site-packages/awscli/”, line 54, in create_clidriver
File “/usr/lib64/python2.6/site-packages/awscli/”, line 44, in load_plugins
modules = _import_plugins(plugin_mapping)
File “/usr/lib64/python2.6/site-packages/awscli/”, line 61, in _import_plugins
module = import(path, fromlist=[module])
File “/usr/lib64/python2.6/site-packages/awscli/”, line 24, in
from awscli.customizations.ec2addcount import ec2_add_count
File “/usr/lib64/python2.6/site-packages/awscli/customizations/”, line 16, in
from botocore.parameters import StringParameter
ImportError: No module named parameters

The aws-cli package is installed but does not seem to be a part of any repositories. Is there an easy way to update the tools and/or get it working?

David W.

There is a separate amazon-ec2 subforum here;

You might get more specific help there, I do note they have a github
site and instructions on how to update in the readme;

Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.48-52.27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!