You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you run the aws sts get-caller-identity command after trying to configure programmatic access locally, it is possible to receive an error which states that the file could not be reached.
It means you haven't properly configured the credentials yet.
This leaves you with an option of configuring it via the command line by running aws configure.
Run the command: aws configure
Also, some people may experience an error when trying to configure credentials by running the command aws configure..
The most possible error that could occur when trying to run aws configure is:
When you run the
aws sts get-caller-identity
command after trying to configure programmatic access locally, it is possible to receive an error which states that the file could not be reached.It means you haven't properly configured the credentials yet.
This leaves you with an option of configuring it via the command line by running
aws configure
.aws configure
Also, some people may experience an error when trying to configure credentials by running the command
aws configure
..The most possible error that could occur when trying to run
aws configure
is:When this happens, make sure you delete the
credentials
folder you created manually, and just re-run theaws configure
command again.I will make a pull request to the docs later on.
The text was updated successfully, but these errors were encountered: