The aws CLI documentation shows that we can create and search suppression details using sesv2 but when I try to use the CLI command in my mac its returning error that"Invalid choice". My awscli version is 1.16.209. The endpoint is working in the boto3 but not in the awscli
aws-cli/1.16.209 Python/3.7.2 Darwin/17.7.0 botocore/1.12.172
https://docs.aws.amazon.com/cli/latest/reference/sesv2/index.html#cli-aws-sesv2
is the sesv2 option working for anyone? or Am i using the wrong awscli version?
I came across same issue today. You might be using aws version 1. This is what I suggest.
Upgrade/install aws version 2 (https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html)
Run the ses2 commands now: aws2 sesv2 list-suppressed-destinations --reason BOUNCE
Related
This questions maybe already asked but that is not solve my issue.
I'm trying to deploy my gactions script in google cloud function. So for that I have installed the gactions CLI in Ubuntu 20.04 machine, but I'm having some problems.
The mentioned gactions CLI comments not working in terminal, it's shows [ERROR] unknown command "test" for "gactions" error message.
Eg: gactions test --action_package action.json --project PROJECT_ID
Am using gactions version 3.2.0. Please suggest me how to use those comments in terminal.
I have tried with sudo gactions test --action_package action.json --project PROJECT_ID that also not working.
As the error [ERROR] unknown command "test" for "gactions" describes that the test command is not validating by the gactions CLI.
Might be due to below reasons, can you you have a check on this :
As per this official doc , you are trying to execute the text command
but make sure the action package name given by you is correct.
Can you try any other arguments mentioned in the gactions supported
arguments doc and have a try whether those are validating or not.
Enable the Actions API in the Google Cloud console by following the
instructions in Enable and disable APIs. This allows gactions to
interact with your project.
Make sure you have installed the gactions CLI correctly by running
the command 'gactions version' to check the version number. If the
version number matches the version you installed, then the CLI is
probably installed correctly. If not reinstall the CLI using this
gactions overview
So I have ran the following commands to initialize my amplify project:
amplify configure
amplify init
Then i run amplify add api.
when I select "REST" api, it says "There was an error adding the API resource" Running amplify status confirms that nothing was added. However, when I try to add the "GraphQL" api, it gives me the same error message, but running amplify status indicates that it was actually added successfully.
i want to add REST api to my amplify app. Not sure what the issue is. I have tried updating amplify cli and reinitializing my project multiple times. thanks in advance.
I am seeing a similar error in the step:
Try opening with system-default editor instead?
The error is:
There are 2 options that helped me
On this step select No
Install xdg-utils: sudo yum -y install xdg-utils (I am using EC2 linux 2 instance)
Try these options and let's see if it helps you.
When checking the AWS PATH with which aws when changing the AWS CLI from 1 to 2
/Users/username/.pyenv/shims/aws
I used to install via pyenv, but I want to remove it and install it according to system 2, but even if I try it according to the official doc, it is not changed to system 2.
https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2-mac.html
curl "https://awscli.amazonaws.com/AWSCLIV2.pkg" -o "AWSCLIV2.pkg"
sudo installer -pkg AWSCLIV2.pkg -target /
It did not change to the 2 system even if I typed this command.
I've also tried uninstalling the AWS CLI, but it doesn't work.
Does anyone know of any way to do this?
thank you
I removed my old aws cli from ~/.pyenv/versions/x.x.x/bin/aws, where x.x.x is the current Python version.
Get the current version:
$ pyenv versions
* 3.7.4
Remove aws cli from current pyenv bin:
$ rm -rf ~/.pyenv/versions/3.7.4/bin/aws*
Try again which aws:
$ which aws
/usr/local/bin/aws
I had the same issue.
This is because pyenv linked the shim to very Python version that command has been installed originally with; that's by the way ok to avoid version conflicts. pip3 and awscli v3 uninstall don't take care of that.
What you have to do is to:
First, uninstall the old awscli as noted in the AWS documentation (probably you used pip3). Note: remember to edit your bash_profile or zshrc as you may have a $HOME/.local/bin PATH in your config: you want to remove that too
The aws shim will remain in place until you get rid of that Python version (pyenv uninstall 3.7.x) BUT YOU PROBABLY DON'T WANT THAT
Just remove the shim manually rm /Users/username/.pyenv/shims/aws
Install the AWS CLI v2 using the recommended installed and verify everything works correctly
I had the same issue in my Windows system because of I was having both AWS CLI and AWS CLI v2 installed but PATH environment variable was corrupted because of installing AWS CLI 2 multiple times.
I removed AWS CLI (means version 1) from that PATH or Path or path variable and I pointed to my AWS CLI v2 folder like C:\Program Files\Amazon\AWSCLIV2\aws.exe. Then all my AWS CLI v2 and kubernate 0.xx.x all set by itself. When I check with aws --version, I get aws 2 version always now.
So, install AWS CLI 2 and also check your path system environment variable. I think no need of work around Python version. Please refer to AWS documentation at https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration-instructions.html#cliv2-migration-instructions-side-by-side
I am trying view logs of my running application on Bluemix using : "cf logs my-cool-app" command (CF version 6.11) .
If fails with :
FAILED
Loggregator endpoint missing from config file
Anyone seen this issue?
The problem appears to stem from the use of the 6.11 codebase for CF CLI and the current version of CloudFoundry that Bluemix is running. Good news is that an upcoming upgrade will alleviate the problem. We're investigating potential workarounds.
This is just an issue with the CF CLI version 6.11.
I have seen the option --generate-cli-skeleton in a lot of aws CLI docs, however every time I add it to a aws cmd I get Unknown options: --generate-cli-skeleton.
Can someone tell me or point me to instructions on how to use this option
thanks
Art
This was added in version 1.5.5 (https://github.com/aws/aws-cli/blob/develop/CHANGELOG.rst#155), make sure your are using version 1.5.5 or higher. You can get the version via aws --version.