3 ms·

You're confusing `awscliv2`[1], a third-party Python wrapper around AWS CLI v2[2], with instance connect. From its package page: - This is not an official AWS

by js2 3y ago

You're confusing `awscliv2`[1], a third-party Python wrapper around AWS CLI v2[2], with instance connect. From its package page: - This is not an official AWS CLI v2 application - By default this app uses amazon/aws-cli Docker image The only official macOS distribution of AWS CLI v2 is via a macOS installer package: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html https://docs.aws.amazon.com/cli/latest/userguide/getting-sta... It's also available in Homebrew[3] but the packaging is maintained by a third-party, not Amazon. [1] https://pypi.org/project/awscliv2/ https://pypi.org/project/awscliv2/ [2] https://awscli.amazonaws.com/v2/documentation/api/latest/index.html https://awscli.amazonaws.com/v2/documentation/api/latest/ind... [3] https://formulae.brew.sh/formula/awscli https://formulae.brew.sh/formula/awscli

radarsat1 3y ago
Oh I see. I installed awscliv2 after discovering that awscli did not have the ec2-instance-connect command, so I could not follow the documentation and went searching to see if there was an updated package and discovered that one. So I guess you are not supposed to install it using pip anymore. Good to know. Update: and now I've read through the github issue, oh my I've missed quite some drama.
- js2 3y ago
  I agree it's confusing and I think Amazon's reasons for dropping PyPI support are pretty lame: https://github.com/aws/aws-cli/issues/4947#issuecomment-586046886 https://github.com/aws/aws-cli/issues/4947#issuecomment-5860... They also have't provided a reason for why they don't distribute via Homebrew: https://github.com/aws/aws-cli/issues/727 https://github.com/aws/aws-cli/issues/727