Package Details: aws-cli-v2-bin 2.7.12-1

Git Clone URL: (read-only, click to copy)
Package Base: aws-cli-v2-bin
Description: Universal Command Line Interface for Amazon Web Services version 2
Upstream URL:
Licenses: Apache
Conflicts: aws-cli, aws-cli-v2
Provides: aws-cli, aws-cli-v2
Submitter: stilvoid
Maintainer: stilvoid
Last Packager: stilvoid
Votes: 40
Popularity: 3.25
First Submitted: 2020-06-24 11:42 (UTC)
Last Updated: 2022-06-30 04:56 (UTC)

Dependencies (2)

Required by (19)

Sources (2)

Latest Comments

Sleipnir commented on 2022-03-11 17:47 (UTC)

Why hasn't this become the default in the official community packages to replace the current AWS CLI v1? Is there a way to request it be moved to community?

ribugent commented on 2022-02-25 07:31 (UTC)

I was reviewing the PKGBUILD and I've noticed that the i686 architecture is not listed on the releases, and also if it was the case, the right release won't be downloaded.

Also, there's an aarch64(arm64) build, and I think it would be nice for these users to allow install it

diff --git a/PKGBUILD b/PKGBUILD
index 3de815a..0cf3f66 100644
@@ -3,15 +3,17 @@ pkgname=aws-cli-v2-bin
 pkgdesc='Universal Command Line Interface for Amazon Web Services version 2'
-arch=('i686' 'x86_64')
+arch=('aarch64' 'x86_64')
 provides=('aws-cli' 'aws-cli-v2')
 conflicts=('aws-cli' 'aws-cli-v2')

 package() {
   $srcdir/aws/install -i "$pkgdir/usr/share/aws-cli" -b "$pkgdir/usr/bin" >/dev/null

Hope this helps

hendry commented on 2021-10-21 03:04 (UTC)

I was fiddling with export aws_cli_auto_prompt=on and I couldn't appear to get the prompt mode working:

aws --version aws-cli/2.2.47 Python/3.8.8 Linux/5.14.12-arch1-1 exe/x86_64.arch prompt/off

Does it need to be rebuilt with it to be explicitly enabled?

barbuk commented on 2021-07-12 04:54 (UTC)

For the last version: 2.2.18

diff --git a/PKGBUILD b/PKGBUILD
index 94f3cd4..e0c309a 100644
@@ -1,6 +1,6 @@
 # Maintainer: Steve Engledow <>
 pkgdesc='Universal Command Line Interface for Amazon Web Services version 2'
 arch=('i686' 'x86_64')
@@ -11,7 +11,7 @@ conflicts=('aws-cli' 'aws-cli-v2')

stilvoid commented on 2020-12-16 14:47 (UTC)

I changed the PKGBUILD to use specific version zips and sha256sums so there's no need to import GPG keys any more.

Mettacrawer commented on 2020-12-16 14:45 (UTC) (edited on 2020-12-16 14:46 (UTC) by Mettacrawer)

To activate bash completion I had to run

$ complete -C /usr/bin/aws_completer aws

Please consider putting a script under /etc/bash_completion.d/ to do that.

Mettacrawer commented on 2020-12-16 14:41 (UTC)

Keyservers sometimes have capacity issues. Please try running pacman-key a few times to see if the server responds eventually.

samhh commented on 2020-11-19 12:10 (UTC)

I had the same error using pacman-key, however gpg --recv-keys <key> worked fine and allowed installation to succeed.

stilvoid commented on 2020-11-04 22:04 (UTC)

Key import is working for me. I just removed and successfully reimported the key. Can you import other keys ok?

badpixelbr commented on 2020-11-03 19:52 (UTC)

sudo pacman-key -r A6310ACC4672475C                                                                                                                             
gpg: keyserver receive failed: General error
==> ERROR: Remote key not fetched correctly from keyserver.

acidrain42 commented on 2020-09-18 13:44 (UTC) (edited on 2020-09-18 13:45 (UTC) by acidrain42)

@stilvoid Having this in the PKGBUILD will override the version at the moment of building the package, creating a disconnect between the AUR version and our local version.

pkgver() {
    ./aws/dist/aws --version | cut -d ' ' -f 1 | cut -d '/' -f 2

It then causes messages like this:

 -> aws-cli-v2-bin: local (2.0.50-1) is newer than AUR (2.0.44-1)

The pkgver() function is good for *-git packages but shouldn't be used for packages with specific versions like this one.

pujianto commented on 2020-09-03 03:22 (UTC) (edited on 2020-09-03 04:19 (UTC) by pujianto)

:: PGP keys need importing:
 -> FB5DB77FD5C118B80511ADA8A6310ACC4672475C, required by: aws-cli-v2-bin
==> Import? [Y/n] y
:: Importing keys with gpg...
gpg: keyserver receive failed: General error
problem importing keys

solved by importing key from

stilvoid commented on 2020-09-01 11:03 (UTC)

Updated the PKGBUILD now that AWS has published their key :)

You'll need to import the key: pacman-key -r A6310ACC4672475C

TaurohtaR commented on 2020-08-25 06:46 (UTC)

@stilvoid appears that each time I install this package my local version is always 1 version ahead of AUR

aws-cli-v2-bin: local (2.0.42-1) is newer than AUR (2.0.41-1)

stilvoid commented on 2020-08-17 14:32 (UTC)

Thanks rtur, I know what's in this PKGBUILD isn't very palatable :(

Please see this github issue and add your +1

tl;dr: the AWS CLI team haven't published their key to a keyserver which makes importing the key a more painful experience.

I'm open to other suggestions for how to approach this if you have any.

rtur commented on 2020-08-12 06:35 (UTC)

Is it a good idea to bundle the public key into the package? Kinda defeats the whole point of it. Why not let users import the public key themselves as is done usually?

Mexx77 commented on 2020-07-30 13:15 (UTC)

works again. thanks stilvoid

stilvoid commented on 2020-07-30 13:04 (UTC)

Wow, upstream seems to release a new version every couple of days at this point!

Mexx77 commented on 2020-07-30 12:59 (UTC) (edited on 2020-07-30 13:00 (UTC) by Mexx77)

i also get

==> Validating source files with sha256sums... ... FAILED
==> ERROR: One or more files did not pass the validity check!
error downloading sources: aws-cli-v2-bin

rew1red commented on 2020-07-29 18:05 (UTC)

It looks like 2.0.35 is the current version, and this accounts for the checksum change.

➜ /usr/share/aws-cli/v2/2.0.35/bin/aws --version
aws-cli/2.0.35 Python/3.7.3 Linux/5.7.10-arch1-1 botocore/2.0.0dev39

stilvoid commented on 2020-07-27 09:29 (UTC)

I updated this last week and it seems correct to me this morning. Perhaps you need to clean build?

TaurohtaR commented on 2020-07-26 07:05 (UTC)

@stilvoid, pls update checksum

==> Validating source files with sha256sums... ... FAILED
==> ERROR: One or more files did not pass the validity check!
error downloading sources: aws-cli-v2-bin

stilvoid commented on 2020-07-10 14:03 (UTC)

Thanks for reporting. Another new version of the CLI was release. Updated to 2.0.30.

scr1m3 commented on 2020-07-10 13:38 (UTC)

I changed the sha256 as 7ee475f22c1b35cc9e53affbf96a9ffce91706e154a9441d0d39cbf8366b718e

in order for the build to go through

Cbhihe commented on 2020-06-26 16:55 (UTC)

@kylelaker: (Re: your comment of 2020.03.20 at 01.35 at I see the incompatibility is between python-botocore-v2.git and the community package python-botocore 1.16.24. Does not change anything in the end and is still an issue for the boto3.x project. Any workaround ?

Cbhihe commented on 2020-06-26 16:39 (UTC)

Thank you. This was all a weird coincidence in time... ;-)

stilvoid commented on 2020-06-26 12:16 (UTC)

A new version of the CLI was released this morning, moments after I updated! I've updated the PKGBUILD to 2.0.26 now

Cbhihe commented on 2020-06-26 11:50 (UTC)

The last commit from 20 min ago, did not fix the md5sums issue. I get the exact same error as before during the validity check.

Cbhihe commented on 2020-06-26 08:14 (UTC) (edited on 2020-06-26 11:52 (UTC) by Cbhihe)

Hello @stilvoid;

After the latest source files fix, installs fail. You need to correct the md5sums for

  • "ERROR: One or more files did not pass the validity check!"

~/aws-cli-v2-bin (master)> makepkg -sric
==> Making package: aws-cli-v2-bin 2.0.25-5 (Fri 26 Jun 2020 10:10:25)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 31.5M 100 31.5M 0 0 10.0M 0 0:00:03 0:00:03 --:--:-- 10.0M
==> Validating source files with md5sums... ... FAILED
==> ERROR: One or more files did not pass the validity check!

stilvoid commented on 2020-06-25 23:29 (UTC)

Whoops yes, good catch. Fixed now :)

montesano commented on 2020-06-25 18:53 (UTC)

Hi, I had an issue where the aws_completer script is being improperly linked.

$ ls -l /usr/bin/aws_completer
lrwxrwxrwx 1 root root 106 Jun 25 10:32 /usr/bin/aws_completer -> /home/me/.cache/yay/aws-cli-v2-bin/pkg/aws-cli-v2-bin/usr/share/aws-cli/v2/current/bin/aws_completer

I fixed it by deleting the quotes around the glob on the for loop line ($pkgdir/$BIN_DIR/*). With quotes, the loop only runs once and $i will be /usr/share/.../aws /usr/share/.../aws_completer which seems to work fine for the aws binary, but not the completer

I'm not sure of the best way to submit a patch, but lmk if you want me to submit something somehow

stilvoid commented on 2020-06-24 11:43 (UTC)

Apologies for the delay, folks!

  • Created new package aws-cli-v2-bin
  • Updated to v2.0.25
  • Added md5sum
  • Submitted request to merge this package's history with the new one.

jhalfmoon commented on 2020-06-24 07:10 (UTC)

Hi, please consider maintaining this package more often, or hand it over to someone else to maintain. This tool is way to high profile for the current package to remain in it's current state of non-maintenance. Thanks.

mercutio commented on 2020-05-30 10:58 (UTC)

This is a PKGBUILD that works for version 2.0.17:

I agree with kylelaker that the package should probably end in -bin.

Cbhihe commented on 2020-05-18 12:10 (UTC)

sym-link current -> /usr/share/aws-cli/v2/2.0.0 located at /usr/share/aws-cli/v2 is still broken. Checksum still unavailable from AWS.

-> unusable.

kylelaker commented on 2020-03-20 01:35 (UTC) (edited on 2020-03-20 01:53 (UTC) by kylelaker)

This package has a few issues:

  • it installs and modifies files outside of $pkgdir
  • it is not built from source but does not end in -bin
  • it is currently out of date and creates an invalid symlink

Please consider adopting the changes in this PKGBUILD

Note: python-botocore-v2-git is not compatible with boto3 so something may need to be done to work around that issue.

n-zhang commented on 2020-02-28 00:08 (UTC)

AWS cli is now on v2.0.1. Symlink broken as it still points to v2.0.0.

stilvoid commented on 2020-02-11 13:40 (UTC)

Updated the package now that AWS CLI v2 is out of preview. I've added PGP sig in comments for now as the AWS CLI team have not yet published their public key to any keyservers. I'm tracking this github issue:

Ciaran commented on 2020-01-15 10:20 (UTC)

1) As AWS don't provide useful versions or hashes, I propose using adding the .sig file and using GPG to validate. 2) Run their installation script in a fakeroot, create the links in a temporary directory, then remove that directory and create the links in a sensible path.

I've sent suggested changes via email.

kriation commented on 2019-12-21 16:13 (UTC)

Broken symlink after installation with no changes to the PKGBUILD

[11:09 @ ~]$ file /usr/bin/aws2 /usr/bin/aws2: broken symbolic link to /tmp/makepkg/aws-cli-v2/pkg/aws-cli-v2/usr/share/aws-cli/v2/current/bin/aws2