I'm trying to upgrade SAM CLI, version 1.18.2 to 1.22.0 on Ubuntu 20.04. I used brew command:
~brew upgrade aws-sam-cli#1.22.0
but didn't work. Showed the next message:
Error: No available formula or cask with the name "aws-sam-cli#1.22".
Also I'm trying to find a downloadable to install a certain version.
Thanks for your help!
https://github.com/aws/aws-sam-cli/issues/1767
For anyone in the future, use pip.
pip3 install --user 'aws-sam-cli==1.12.0'
Related
Im using windows and im trying to use git-remote-codecommit.
steps for HTTPS Connections to AWS CodeCommit with git-remote-codecommit.
https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-git-remote-codecommit.html
While fetching , this error shows:
git clone codecommit://MyRepositoryName
git: 'remote-codecommit' is not a git command. See 'git --help'
please help..
The other solutions did not work for me. I tried following https://docs.aws.amazon.com/codecommit/latest/userguide/troubleshooting-grc.html#:~:text=a%20CodeCommit%20repository-,I%20see%20an%20error%3A%20git%3A%20%27remote-codecommit%27%20is%20not%20a%20git%20command,-Problem%3A%20When%20you but it did not work as well.
What ended up working as doing a brew install git-remote-codecommit :)
$ which git-remote-codecommit
/opt/homebrew/bin/git-remote-codecommit
I am using a M1 Big Sur if that matters.
I had a similar issue. It turns out that somehow the git-remote-codecommit extension was somehow installed but broken.
I fixed it by first
uninstalling: pip3 uninstall git-remote-codecommit
reinstalling: pip3 install git-remote-codecommit
The install will check to see if Python3 is in your $PATH if not you'll need to add it.
This fixed the problem for me.
Need to run this command in terminal to solve this problem pip3 install git-remote-codecommit or pip install git-remote-codecommit
I was also facing this issue but it work after Force install git-remote-codecommit
pip install git-remote-codecommit --force
The same solution is given here as well.
https://www.miraclewebsoft.com/remote-codecommit-is-not-a-git-command-see-git-help/
i try to uninstall git-remote-codecommit and find the path that it's installed
C:\Users\user>pip3 uninstall git-remote-codecommit
Found existing installation: git-remote-codecommit 1.16
Uninstalling git-remote-codecommit-1.16:
Would remove:
c:\users\user\appdata\roaming\python\python39\scripts\git-remote-codecommit-script.py
c:\users\user\appdata\roaming\python\python39\scripts\git-remote-codecommit.exe
c:\users\user\appdata\roaming\python\python39\site-packages\git_remote_codecommit-1.16-py3.9.egg-info
c:\users\user\appdata\roaming\python\python39\site-packages\git_remote_codecommit\*
when i add this path to environment variable then it works.
c:\users\user\appdata\roaming\python\python39\scripts\
I faced the same problem when I installed the git-remote-codecommit using pip with --user flag which installed the package in the home directory.
pip install git-remote-codecommit --user
I fixed the problem by adding Python's Script path to the PATH environment variable.
C:\Users\{HOME_DIR}\AppData\Roaming\Python\Python37\Scripts
In my case I set-up the remote url
$ git remote set-url origin https://git-codecommit.*******/v1/repos/My-Project
I added a commit
and I push to master
git push origin master
and it works
I have installed the AWS CLI around 6 moths back and upgraded using the following command today.
pip install --upgrade awscli
The current version on my Ubuntu 18.04 machine is:
aws-cli/1.14.44 Python/3.6.5 Linux/4.15.0-23-generic botocore/1.8.48
When I try aws eks command, I am getting the following error:
Invalid choice: 'eks', maybe you meant:
* es
Is my aws cli is upgraded properly or should I install something else for EKS service?
I had the same issue on El Capitan 10.11.6 and the only one worked solution was this:
sudo pip install awscli --ignore-installed six
Version 6 comes with distutils in El Capitan
Reference: https://github.com/aws/aws-cli#installation
Solutions mentioned did not resolve my issue - this link helped me out in figuring the issue.
aws --version
displayed a version which was not the latest. EKS was introduced with version 1.15.32 - which means my version did not know EKS at all. Uninstalling and reinstalling did not work either, path was referring to some older version previously installed somewhere else. The solution was following installation instructions here followed by updating the path variable
the issue cannot be resolved until the
aws --version command shows you any version less than 1.15.32.
The other solutions may be additional fixes needed afterwards, yet they will not work with an earlier version either.
Please check with the AWS region you configured for the AWS CLI you installed.
AWS EKS is available only on US East (N. Virginia) and US West (Oregon).
Do check it properly and configure the same for AWS CLI.
I faced the same issue because my current aws cli version was old (as shown below)
$aws --version
aws-cli/1.14.44 Python/3.6.8 Linux/4.15.0-58-generic botocore/1.8.4
Upgrading the awscli version helped to resolve the issue
$pip3 install --upgrade --user awscli
$aws --version
aws-cli/1.16.252 Python/3.6.8 Linux/4.15.0-58-generic botocore/1.12.242
Here is the link to upgrade awscli
https://docs.aws.amazon.com/cli/latest/userguide/install-linux-al2017.html
I was trying to connect to the cluster from a diff aws profile. So ideally we should use the same IAM profile for running kubectl from local so that the heptio-authenticator-aws will be happy.
This happens when we install aws-cli using apt packages as below.
sudo apt-get install awscli
because by default it will install 1.14 aws-cli version. Therefore my recommendation is to use pip3 to install aws-cli to your machine. It always installs the latest aws-cli version.
pip3 install --upgrade --user awscli
All this not worked for you then
pip uninstall awscli
sudo rm -rf /usr/local/aws
pip3 install awscli --upgrade --user
aws --version
aws-cli/1.18.39 Python/3.6.9 Linux/4.15.0-1065-aws botocore/1.15.39
if this is older version(aws-cli/1.18.39) then it won't work for you
Airflow installation with command is failing
sudo pip3 install apache-airflow[gcp_api]
Everything was working fine yesterday. Today I see the following error:
Could not find a version that satisfies the requirement apache-beam[gcp]==2.3.0 (from google-cloud-dataflow->apache-airflow[gcp_api]) (from versions: 0.6.0, 2.0.0, 2.1.0, 2.1.1, 2.2.0)
No matching distribution found for apache-beam[gcp]==2.3.0 (from google-cloud-dataflow->apache-airflow[gcp_api])
Can someone help me on this?
Thanks in advance
I faced the same problem :(
Why?
most likely it happened because in the new version(2.3.0) of apache-beam they actually added the restriction for python3
https://pypi.python.org/pypi/apache-beam/2.3.0
Requires Python: >=2.7,<3.0
the previous packages didn't have this restriction, that is why it was working before(if you didn't use dataflow from gcp).
probably you have the last version of https://pypi.python.org/pypi/google-cloud-dataflow/2.3.0 which has updated apache-beam package
How to fix?
uninstall google-cloud-dataflow
pip3 uninstall google-cloud-dataflow
and install version 2.2.0 which has the old version of apache beam
pip install google-cloud-dataflow==2.2.0
Fixed this problem for me, I hope it will help you as well
This has been resolved in the master branch at Apache Airflow Github by Pull Request #3273 .
You can install the latest development branch using the below commands.
pip install git+https://github.com/apache/incubator-airflow
pip install git+https://github.com/apache/incubator-airflow#egg=apache-airflow[gcp_api]
I'm on a Windows based machine using GitBash for my shell. When I run, pip install aws cli, I get the following message:
Could not find a version that satisfies the requirement cli (from versions: ) No matching distribution found for cli
I Googled the error, and many responses indicate that it's can be the result of a package that's not contained in pypi, etc. (Pip install-couldn't find a version that satisfies the requirement).
However, since I'm following the video here: http://course.fast.ai/lessons/aws.html at 4:13, and it worked for the instructor, I'm not sure what I'm missing - can someone help me understand this (including any helpful troubleshooting commands to identify the source of the issue?)
I'm new to AWS and also bash so I apologize if this is a relatively elementary question.
Thanks in advance!
-Ryan
The command should be:
pip install awscli
You need to remove the space between 'aws' and 'cli'.
Try these commands
curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python get-pip.py
then
pip install awscli
I have successfully installed php70 and mysql. But when i am trying to install phpmyadmin by
$ sudo yum-config-manager --enable epel
And Then
$ sudo yum install -y phpMyAdmin
It gives me
--> Finished Dependency Resolution
Error: php70-common conflicts with php-common-5.3.29-1.8.amzn1.x86_64
Error: php56-common conflicts with php-common-5.3.29-1.8.amzn1.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Also after google sometimes i found a solution that try this
sudo yum install php70-mbstring
And i have tried this also, Still facing same error.
Any suggestion...?
I guess that you are following the Amazon tutorial to install phpMyAdmin ?
I had the same problem today and resolved it by uninstall PHP 7.0 with the yum command (the same given by Amazon with 'remove' instead of 'install' :
sudo yum remove httpd24 php70 mysql56-server php70-mysqlnd
and installed PHP 5.6 instead :
sudo yum install httpd24 php56 mysql56-server php56-mysqlnd
I don't know if this is a good solution, but it worked and I could install phpMyAdmin without dependencies problem. I hope it will help :)
In case you want to keep php7, I found a solution with AWS Amazon experts.
Just use :
sudo yum install -y php70-mbstring
I was having the same issue today. I had some success downloading phpmyadmin from phpmyadmin.net, and following their instructions. I did run into a different problem during the setup of phpmyadmin....
So, I punted on resolving this with the Amazon AMI for now, and chose to install the Bitnami LAMP AMI to get me going quicker. It comes with phpmyadmin configured.
NOTE: Bitnami's AMI is running PHP Version 5.6.29, so I would say it's valid to follow the previous post's advice and downgrade, unless your web application specifically needs PHP 7.0.