I am having issues connecting to S3 using AWS CLI, while upgrading I see the error:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
boto3 1.21.28 requires botocore<1.25.0,>=1.24.28, but you have botocore 1.29.11 which is incompatible.
boto3 1.21.28 requires s3transfer<0.6.0,>=0.5.0, but you have s3transfer 0.6.0 which is incompatible.
How can it be resolved? Do I revert back to the previous version of AWS CLI?
Related
I'm using visual studio code with the AWS cli version 2.9.13, I've got an SSO profile configured which I use to authenticate to the AWS service using device code authentication - I can then use this profile to connect to our AWS code commit repository however when trying to invoke any of the AWS PowerShell cmdlets I'm getting the below error returned;
Assembly AWSSDK.SSOOIDC could not be found or loaded. This assembly must be available at runtime to use Amazon.Runtime.Internal.SSOServiceClientHelpers, AWSSDK.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=885c28607f98e604.
This error is returned each time I use the profile parameter as shown below
-ProfileName MySSOProfile
What i've done so far;
Re installed the AWS modules i'm trying to use and installed the
latest version
Updated all packages on my WSL to the latest versions
Installed the AWS Toolkit extension for visual studio, now on version 1.60.0
Installed AWSSDK.Core --version 3.7.103.13
What do I need to do to resolve this error and so that I can use my authenticated AWS profile to invoke the AWS cmdlets?
Using SSO credentials from either the .NET SDK or AWS Tools for PowerShell requires a dependency on the SDK's own SSO and SSOOIDC mdoules.
Install-Module AWS.Tools.Installer
Install-AWSToolsModule S3, SSO, SSOOIDC
# Since we're not invoking a cmdlet from these modules directly,
# we must import them explicitly
Import-Module AWS.Tools.SSO
Import-Module AWS.Tools.SSOOIDC
# AWS Tools for PowerShell doesn't support the SSO login flow yet, so login with the CLI
aws sso login --profile MySSOProfile
# Now we can invoke cmdlets using the SSO profile
Get-S3Bucket -ProfileName MySSOProfile
See also Update AWS CLI credentials from AWS IAM Identity Center by using PowerShell
I am facing issues with boto3(1.9.42) readily comes with AWS which fails when I run certain commands. But same issue is not faced when I run the script locally because boto3 installed locally is 1.9.118 version where as aws comes with 1.9.42.
client_api = boto3.client(service_name='apigatewaymanagementapi', endpoint_url=endpoint_url)
[ERROR] UnknownServiceError: Unknown service: 'apigatewaymanagementapi
I know there is no direct way to replace boto3 in aws. Is there any way I can deploy the local boto3 to aws and use the module from aws lambda functions.
I am following an AWS lambda tutorial https://docs.aws.amazon.com/lambda/latest/dg/vpc-rds-create-rds-mysql.html and the first step is to create an RDS instance via the CLI but I am getting the following error...
Invalid endpoint: https://rds.us-east-2.amazonaws.com
I've tried specifying a couple other parameters such as --availability-zone, -vpc-security-group-ids, etc but it still is saying the endpoint doesn't exist?
Make sure you have the latest version of the AWS CLI tool installed. It sounds like you have an older version before us-east-2 was added. You can check the version you have installed by running aws --version.
when I do this
"/users/akshay/bin/aws --version"
I get
"aws-cli/1.15.57 Python/2.7.10 Darwin/17.6.0 botocore/1.10.56"
why should I always use the path
"/users/akshay/bin/aws"
to refer to the aws cli? And why can't I just do
aws --version?
I am working in the US-East-1 (N.Virginia) and have even configured the Default Region Name to us-east-1 using the command aws configure.
But I am not able to access Batch using CLI. Batch is not even listed as one of the Available Services in aws help.
Any ideas how to enable Batch in AWS Cli? I have administrative access in IAM console so permissions don't seem to be the issue.
The batch service is relatively new, so its commands only exist in fairly new versions of the aws CLI.
Commands for batch in the latest cli documentation: http://docs.aws.amazon.com/cli/latest/reference/batch/index.html?highlight=batch
If you are running Windows, simply download the updated installer. https://aws.amazon.com/cli/
If you are using OSX or Linux use pip. pip install --upgrade awscli