Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Update install-cliv2-linux.md #30

Closed
wants to merge 2 commits into from
Closed

Update install-cliv2-linux.md #30

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c8453b9
Update install-cliv2-linux.md
skyzyx Mar 27, 2020
9010510
Merge branch 'master' into patch-1
skyzyx Sep 25, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion doc_source/install-cliv2-linux.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,9 @@ Use your operating system's ability to create a symbolic link \(symlink\) or ali
+ We support the AWS CLI version 2 on Linux ARM\.
+ Because AWS doesn't maintain third\-party repositories, we can’t guarantee that they contain the latest version of the AWS CLI\.

**Important**
It is important to note that BusyBox and Alpine Linux, which are popular Linux distributions for Docker containers and continuous integration systems due to their size, use `musl` for their standard C library and do not ship with `glibc` by default\.

## Install the AWS CLI version 2 on Linux<a name="cliv2-linux-install"></a>

Follow these steps from the command line to install the AWS CLI on Linux\.
Expand Down Expand Up @@ -412,4 +415,4 @@ The following example assumes you downloaded the installer package and saved it
Primary key fingerprint: FB5D B77F D5C1 18B8 0511 ADA8 A631 0ACC 4672 475C
```
**Important**
The warning in the output is expected and doesn't indicate a problem\. It occurs because there isn't a chain of trust between your personal PGP key \(if you have one\) and the AWS CLI PGP key\. For more information, see [Web of trust](https://wikipedia.org/wiki/Web_of_trust)\.
The warning in the output is expected and doesn't indicate a problem\. It occurs because there isn't a chain of trust between your personal PGP key \(if you have one\) and the AWS CLI PGP key\. For more information, see [Web of trust](https://wikipedia.org/wiki/Web_of_trust)\.