Downloads of v


Last Update:

07 Jan 2016

Package Maintainer(s):

Software Author(s):

  • Amazon


ec2clitools admin Workwave-Engineering-Services

Amazon EC2 CLI / API Tools

  • 1
  • 2
  • 3 | Updated: 07 Jan 2016



Downloads of v



Software Author(s):

  • Amazon

  • 1
  • 2
  • 3
Amazon EC2 CLI / API Tools

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install Amazon EC2 CLI / API Tools, run the following command from the command line or from PowerShell:


To upgrade Amazon EC2 CLI / API Tools, run the following command from the command line or from PowerShell:


To uninstall Amazon EC2 CLI / API Tools, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade ec2clitools -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade ec2clitools -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure ec2clitools installed
    name: ec2clitools
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'ec2clitools' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: ec2clitools,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller ec2clitools
   Name     = 'ec2clitools'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'ec2clitools':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install ec2clitools version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 07 Jan 2016.


You can use the CLI tools to manage your Amazon EC2 resources (such as instances, security groups, and volumes) and your Amazon VPC resources (such as VPCs, subnets, route tables, and Internet gateways).


$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'ec2clitools'
$packageVersion = ''
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$checksum = '51D6D7DFAFBFEDF74C743DAB6B9B58A4E48232DF'
$checksumtype = 'sha1'

Install-ChocolateyZipPackage $packageName $url $toolsDir -checksum $checksum -checksumType $checksumType

Install-ChocolateyEnvironmentVariable -variableName 'EC2_HOME' -variableValue "C:\ProgramData\chocolatey\lib\ec2clitools\tools\ec2-api-tools-$packageVersion" -variableType 'Machine'

Install-ChocolateyPath "`%EC2_HOME`%\bin" 'Machine'

Write-Warning "You must start a new prompt, or re-read the environment for the tools to be available in your command line environment."

Write-Warning "For completely automatic operation you must set the environment variables AWS_ACCESS_KEY and AWS_SECRET_KEY, for details see:"

$ErrorActionPreference = 'Stop';

$packageName = 'ec2clitools'
$zipName = ''

Uninstall-ChocolateyZipPackage $packageName $zipName


#Using .NET method prevents expansion (and loss) of environment variables (whether the target of the removal or not)
#To avoid bad situations - does not use substring matching or regular expressions
#Removes duplicates of the target removal path, Cleans up double ";", Handles ending "\"

$PathToRemove = '%EC2_HOME%\bin'
foreach ($path in [Environment]::GetEnvironmentVariable("PATH","Machine").split(';'))
  If ($Path)
    If (($path -ine "$PathToRemove") -AND ($path -ine "$PathToRemove\"))
      [string[]]$Newpath += "$path"
$AssembledNewPath = ($newpath -join(';')).trimend(';')


Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Discussion for the Amazon EC2 CLI / API Tools Package

Ground Rules:

  • This discussion is only about Amazon EC2 CLI / API Tools and the Amazon EC2 CLI / API Tools package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Amazon EC2 CLI / API Tools, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus