If you have a question about IPython, (now Jupyter) the programming language written by scientists for scientists with an eye towards presentation, we want you here. If you have tips, Notebooks you want to share, or you want feedback we want you here. We welcome posts about the all versions of the IPython IDE, plus Markdown and LaTex. We discuss the popular libraries Mathplotlab, SciPy, NumPy, & SymPy. If you want to know about features like embedded video or animation check us out. Show
This section covers common errors and troubleshooting steps to follow to resolve your issue. We suggest following the general troubleshooting first. Contents
General troubleshooting to try firstIf you receive an error or encounter an issue with the AWS CLI, we suggest the following general tips to help you troubleshoot. Back to top Check your AWS CLI command formattingIf you receive an error that indicates that a command doesn't exist, or that
it doesn't recognize a parameter (
For more information on how a specific command should be structured, see the AWS CLI version 2 reference guide . Back to top Confirm that you're running a recent version of the AWS CLIIf you receive an error that indicates that a command doesn't exist, or that it doesn't recognize a parameter that the AWS CLI version 2 reference guide says is available, first confirm that your command is correctly formatted. If the formatting is correct, then we recommend that you upgrade to the most recent version of the AWS CLI. Updated versions of the AWS CLI are released almost every business day. New AWS services, features, and parameters are introduced in those new versions of the AWS CLI. The only way to get access to those new services, features, or parameters is to upgrade to a version that was released after that element was first introduced. How you update your version of the AWS CLI depends on how you originally installed it as described in Installing or updating the latest version of the AWS CLI. If you used one of the bundled installers, you might need to remove the existing installation before you download and install the latest version for your operating system. Back to top Use the --debug optionWhen the AWS CLI reports an error that you don't immediately understand, or produces results
that you don't expect, you can get more detail about the error by running the command again with the You can send the output to a text file for later review, or to send to AWS Support when asked for it. When you include the
Here's an example of a command run with and without the
Show moreShow less Back to top Enable and review the AWS CLI command history logsYou can enable the AWS CLI command history logs using the You can this list your history using the When you include the
You can use this information to confirm paramater data and API calls are behaving in the way you expect, and can then deduce at what step in the process your command is failing. Back to top Confirm that your AWS CLI is configuredVarious errors can occur if your Back to top Command not found errorsThis error means that the operating system can't find the AWS CLI command. The installation might be incomplete or requires updating. Possible cause: You're trying to use an AWS CLI feature newer than your installed version, or have incorrect formatting Example error text:
Various errors can occur if your command is formatted incorrectly or you are using an earlier version from before the feature was released. For more information on resolving errors around these two issues, see Check your AWS CLI command formatting and Confirm that you're running a recent version of the AWS CLI. Back to top Possible cause: The terminal needs to be restarted after installationExample error text:
If
the Back to top Possible cause: The AWS CLI did not fully installExample error text:
If the Back to top Possible cause: The AWS CLI does not have permissions (Linux)If the
Back to top Possible cause: The operating systemPATH was not updated during installationExample error text:
You might need to add the Back to top The "aws --version" command returns a different version than you installedYour terminal might be returning a different Possible cause: The terminal needs to be restarted after installing If the Back to top Possible cause: You have multiple versions of the AWS CLIIf you updated the AWS CLI and used a different install method than your
pre-existing installation, it might cause multiple versions to be installed. For example, if on Linux or macOS you used To resolve this, uninstall all versions of the AWS CLI and perform a clean install. After uninstalling all versions, follow instructions appropriate for your operating system to install your desired version of the AWS CLI version 1 or AWS CLI version 2. Back to top The "aws --version" command returns a version after uninstalling the AWS CLIThis often occurs when there is still an AWS CLI installed somewhere on your system. Possible cause: The terminal needs to be restarted after uninstalling If the Back to top Possible cause: You have multiple versions of the AWS CLI on your system, or didn't use the same uninstall method that you used to originally install the AWS CLIThe AWS CLI might not uninstall correctly if you uninstalled the AWS CLI using a different method than you used to install it, or if you installed multiple versions. For example, if you used
Back to top Access denied errorsPossible cause: The AWS CLI program file doesn't have "run" permission On Linux or macOS, make sure that the To add run permission for your user, run the following command, substituting
Back to top Possible cause: Your IAM identity doesn't have permission to perform the operationExample error text:
When you run a AWS CLI command, AWS operations are performed on your behalf, using credentials that associate you with an IAM user or role. The policies attached to that IAM user or role must grant you permission to call the API actions that correspond to the commands that you run with the AWS CLI. Most commands call a single action with a name that matches the command name. However, custom commands like If you are sure that the user or role has the proper permissions assigned by policy, make sure that your AWS CLI command is using the credentials you expect. See the next section about credentials to verify that the credentials the AWS CLI is using are the ones that you expect. For information about assigning permissions to IAM users and roles, see Overview of Access Management: Permissions and Policies in the IAM User Guide. Back to top Invalid credentials and key errorsExample error text:
Possible cause: The AWS CLI is reading incorrect credentials or from an unexpected location The AWS CLI might
be reading credentials from a different location than you expect, or your key pair information is incorrect. You can run The following example shows how to check the credentials used for the default profile.
The following example shows how to check the credentials of a named profile.
To confirm your key pair details, check your Back to top Possible cause: Your computer's clock is out of syncIf you are using valid credentials, your clock might be out of sync. On Linux or macOS, run
If your system clock is not correct within a few minutes, use
On Windows, use the date and time options in the Control Panel to configure your system clock. Back to top Signature does not match errorsExample error text:
When the AWS CLI runs a command, it sends an encrypted request to the AWS servers to perform the appropriate AWS service operations. Your credentials (the access key and secret key) are involved in the encryption and enable AWS to authenticate the person making the request. There are several things that can interfere with the correct operation of this process, as follows. Possible cause: Your clock is out of sync with the AWS servers To help protect against replay attacks , the current time can be used during the encryption/decryption process. If the time of the client and server disagree by more than the allowed amount, the process can fail and the request is rejected. This can also happen when you run a command in a virtual machine whose clock is out of sync with the host machine's clock. One possible cause is when the virtual machine hibernates and takes some time after waking up to sync the clock with the host machine. On Linux or macOS, run
If your system clock is not correct within a few minutes, use
On Windows, use the date and time options in the Control Panel to configure your system clock. Back to top If your AWS secret key includes certain special characters, such as If you process your access keys and secret keys using other tools or scripts, such as tools that build the credentials file on a new instance as part of its creation, those tools and scripts might have their own handling of special characters that causes them to be transformed into something that AWS no longer recognizes. We suggest regenerating the secret key to get one that does not include the special character causing issues. Back to top SSL certificate errorsPossible cause: The AWS CLI doesn't trust your proxy's certificate Example error text:
When you use a AWS CLI command, you receive an To fix this, instruct the AWS CLI where to find your companies Back to top Possible cause: Your configuration isn't pointing to the correct CA root certificate locationExample error text:
This is caused by your Certification Authority (CA) bundle file location being configured incorrectly in the AWS CLI. To fix this, confirm where your companies Back to top Invalid JSON errorsExample error text:
When you use an AWS CLI command, you receive a " Possible cause: You did not enter valid JSON for the AWS CLI to use Confirm you have valid JSON entered for your command. We suggest using a JSON validator for JSON you're having issues formatting. For more advanced JSON usage in the command line, consider using a command line JSON processor, like Back to top Possible cause: Your terminal's quoting rules are preventing valid JSON being sent to the AWS CLIBefore the AWS CLI receives anything from a command, your terminal processes the command using it's own quoting and escaping rules. Due to a terminal's formatting rules, some of your JSON content may be stripped before the command is passed to the AWS CLI. When formulating commands, be sure to use your terminal's quoting rules. To troubleshoot, use the
Modify your command until your until valid JSON is returned. For more in-depth troubleshooting, use the
Use your terminal's quoting rules to fix any issues your JSON input has when being sent to the AWS CLI. For more information on quoting rules, see Using quotation marks with strings in the AWS CLI. If you're having issues with getting valid JSON to the AWS CLI, we recommend to bypass a terminal's quoting rules for JSON data input by using Blobs to pass your JSON data directly to the AWS CLI. For more information on Blobs, see Binary / blob (binary large object) and streaming blob . Back to top Additional resourcesFor additional help with your AWS CLI issues, visit the AWS CLI community on GitHub or the AWS re:Post community. Back to top How do I fix command not found on Mac?It's recommended to try them one by one until the command can be executed successfully.. Fix 1: Check the command's syntax.. Fix 2: Set $PATH as the default macOS path.. Fix 3: Add your directory to PATH.. Fix 4: Reinstall macOS or restore from Time Machine.. How do I fix zsh command not found Mac?Open the . zshrc file with the command nano /. zshrc.. Add the following code to the file: export PATH="$PATH:/opt/homebrew/bin/". Save the file using Control + Enter and X.. To apply changes, type source /. zshrc in the command line.. How do I run Python on Mac Terminal?On a Mac system, it is very straight-forward. All you need to do is open Launchpad and search for Terminal , and in the terminal, type Python and boom, it will give you an output with the Python version.
How do I allow access to Terminal on Mac?On your Mac, choose Apple menu > System Preferences, click Security & Privacy , then click Privacy. Select Files and Folders. Select the checkbox below an app to allow it to access files and folders in that location.
|