Bobcares

.aws Directory Not Found | Troubleshooting tips

by | Sep 14, 2022

Let’s take a closer look at the “.aws directory not found” issue in this article. Bobcares, as a part of our AWS Support Services offers solutions to every AWS query that comes our way.

“.aws directory not found.” Why?

The shared AWS config and credentials files are plaintext files that are stored by default in the “home” folder on the computer. On Linux and macOS, this is usually displayed as ~/.aws and the default location of files is ~/.aws/config ~/.aws/credentials. It is %USERPROFILE%\.aws on Windows and the default location of files is %USERPROFILE%\.aws\config %USERPROFILE%\.aws\credentials.

.aws directory not found

At the start of the path, a ~/ or ~  followed by the file system’s default path separator resolves by checking, in order,

  • The HOME environment variable.
  • The USERPROFILE environment variable.
  • The HOMEDRIVE environment variable links with HOMEPATH environment variable.
  • An SDK or tool-specific home path resolution function or variable.

If a user’s home directory is at the beginning of the path, it resolves to the user name’s home directory whenever possible.

Changing the file’s default location:

In order to change the location or name of these files from the default to a custom value, use the following environment variables.

  • config file environment variable: AWS_CONFIG_FILE
  • credentials file environment variable: AWS_SHARED_CREDENTIALS_FILE

On Linux or macOS, we can specify an alternate location by running the following export commands.

$ export AWS_CONFIG_FILE=/some/file/path/on/the/system/config-file-name
$ export AWS_SHARED_CREDENTIALS_FILE=/some/other/file/path/on/the/system/credentials-file-name

On Windows, we can specify an alternate location by running the following setx commands.

C:\> setx AWS_CONFIG_FILE c:\some\file\path\on\the\system\config-file-name
C:\> setx AWS_SHARED_CREDENTIALS_FILE c:\some\other\file\path\on\the\system\credentials-file-name

Folders beginning with . are hidden folders. Users can create them from the command prompt in Windows or Linux by typing mkdir. If we install aws-cli and then run the aws configure command, it result in the creation of this folder in the home folder automatically. When we run the above command, we must supply the default AWS region, AWS access, and secret key on the command prompt. Once we provide that, this creates the following two files in the.aws folder: config and credentials.

The AWS access and secret key will be present in the credentials file. AWS uses this as an authorization mechanism. It is extremely useful when directly accessing AWS resources via command line or creating AWS clients computationally.

To fix “.aws directory not found.” issue:

The .aws folder is in the adminstrator account (user), so keep that in mind while working, because if we don’t have admin power, then login through that and then check for C:UsersAdministrator.aws.

[Looking for a solution to another query? We are just a click away.]

Conclusion

In this article, we provides a simple troubleshooting method from our Support team to the issue, “.aws directory not found.”

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF