Updated aws cli & sam cli install details in README

Author: binarymist

README.md

@@ -54,79 +54,33 @@ lambda functions of <a href="https://purpleteam-labs.com/" title="purpleteam">pu
 
 Clone this repository.
 
-# Install the aws cli
+# Install aws cli
 
-It appears that v2 is somewhat different to install, details [here](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html).
-
-## Legacy v1 install of aws cli below
-
-Read:
-
-* https://docs.aws.amazon.com/cli/latest/userguide/installing.html
-* https://docs.aws.amazon.com/cli/latest/userguide/awscli-install-linux.html#awscli-install-linux-path
-
-[Don't install pip the suggested way](https://stackoverflow.com/questions/49881448/importerror-cannot-import-name-main-after-upgrading-to-pip-10-0-0-for-python#answer-49989474)
-
-`python -V`  
-`python3 -V`  
-`apt-get update`  
-`apt-get install python-pip`  
-`apt install python-pip python3-pip`
-
-[`apt-get install python-setuptools python3-setuptools`](https://stackoverflow.com/questions/14426491/python-3-importerror-no-module-named-setuptools#answer-14426553)
-
-The following command can also be run regularly to update awscli  
-`pip install awscli --upgrade --user`  
-If the above command produced `error: invalid command 'bdist_wheel'` then run `pip install wheel`
-
-Needed to then [update my path](https://docs.aws.amazon.com/cli/latest/userguide/install-linux.html#install-linux-pip) so that `~/.local/bin` would be included.
-
-If you get the following error when runing `sam` commands:  
-```
-/home/you/.local/lib/python2.7/site-packages/requests/__init__.py:83: RequestsDependencyWarning: Old version of cryptography ([1, 2, 3]) may cause slowdown.
-  warnings.warn(warning, RequestsDependencyWarning)
-```
-Then run: `pip install --upgrade cryptography`
-
-If you get OpenSSL errors like the following:  
-```
-...
-  File "/home/you/.local/lib/python2.7/site-packages/urllib3/contrib/pyopenssl.py", line 46, in <module>
-    import OpenSSL.SSL
-  File "/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in <module>
-    from OpenSSL import rand, crypto, SSL
-  File "/usr/lib/python2.7/dist-packages/OpenSSL/SSL.py", line 118, in <module>
-    SSL_ST_INIT = _lib.SSL_ST_INIT
-AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
-```
-Then run: `pip install --upgrade pyOpenSSL`
+If you are running on a Linux based system with apt, you can install `awscli` via the standard repository. This may be a little old, but it may be OK, and of course it's very quick and easy.
 
+Or with a handful of commands you can install the latest, details [here](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html).
 
 # Install aws-sam-cli
 
 The [install details](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html) for Linux can be found [here](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install-linux.html).  
 You will need to install brew first. Once you have done that `which brew` will show you were it is installed.  
+Contrary to the install instructions, it was installed to: `/home/linuxbrew/.linuxbrew/Homebrew/bin/brew`  
 For us we use zsh, so adding homebrew to our path was just adding the following line to our ~/.zshrc file:  
 ```shell
-export PATH=/home/linuxbrew/.linuxbrew/Homebrew/bin:$PATH
+export PATH=/home/linuxbrew/.linuxbrew/Homebrew/bin/brew:$PATH
 ```  
 Then just reload with the following command:  
 ```shell
 source ~/.zshrc
 ```  
-Your terminal should know where brew now is. Carry on with the aws-sam-cli install.
-
-## Legacy Python install of aws-sam-cli below
-
-`pip install --user --upgrade aws-sam-cli`
-
-This kept failing with an error [`regex_3/_regex.c:46:20: fatal error: Python.h: No such file or directory`](https://github.com/awslabs/aws-sam-cli/issues/922#issuecomment-452361161)
-
-So I did as [jfuss suggested](https://github.com/awslabs/aws-sam-cli/issues/922#issuecomment-452363441):  
-`sudo apt-get install python-dev python3-dev`  
-Then tried `pip install --user --upgrade aws-sam-cli` again, and could now see `sam` listed in `~/.local/bin/`
+Your terminal should know where brew now is. Carry on with the aws-sam-cli install.  
+For us we had to run the install twice  
+```shell
+brew tap aws/tap
+brew install aws-sam-cli
+```
 
-# [Validating SAM templates](https://github.com/awslabs/aws-sam-cli/blob/develop/docs/usage.md#validate-sam-templates) (probably still needs doing)
+# Configuring aws cli
 
 In order to validate SAM templates, [you'll need](https://github.com/awslabs/aws-sam-cli/issues/394) an AWS user with CLI access and policy `AWSQuickSightListIAM` added to the group of the CLI user, then, usually the easiest way to do this is to run [`aws configure`](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) which will create two files ([`~/.aws/credentials`](https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-shared.html) & `~/.aws/config`) if they don't already exist. The `aws_access_key_id` & `aws_secret_access_key` will be created in the `credentials` file if they don't exist, and the `output` & [`region`](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-region.html) will be created in the `config` file if they don't exist. If you don't set the region you'll end up with [errors](https://github.com/awslabs/aws-sam-cli/issues/442)  
 Next it's a good idea to make sure these files are `chmod 600` (by default mine was). I then `chmod 700` on `~/.aws/`, just like the `~/.ssh/` directory is.