`aws configure` uses USERPROFILE instead of HOME

[rcdailey]

Describe the bug

When I have the HOME environment variable explicitly set on my Windows 10 system, running aws configure from a Powershell terminal results in the .aws directory and its files being created at %USERPROFILE%/.aws instead of %HOME%/.aws.

Expected Behavior

If the HOME environment variable is set, the .aws directory should be placed at %HOME%/.aws instead of %USERPROFILE%/.aws, according to the docs.

Current Behavior

The aws configure command will spit out files at %USERPROFILE%/.aws but the .NET library correctly looks in %HOME%/.aws which doesn't exist because the tool did not place the files in the right location.

Reproduction Steps

1. In Windows Environment Variables, add a new user environment variable named HOME and set it to some path like C:\linux_home.
2. Restart machine.
3. Execute aws configure and follow the prompts. Insert a value for each question.
4. Observe that files are created in %USERPROFILE%/.aws which is incorrect.

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

<PackageReference Include="AWSSDK.Core" Version="3.7.8.10" />
<PackageReference Include="AWSSDK.EC2" Version="3.7.61" />
<PackageReference Include="AWSSDK.Extensions.NETCore.Setup" Version="3.7.2" />
<PackageReference Include="AWSSDK.SecretsManager" Version="3.7.2.18" />

Targeted .NET Platform

net6.0

Operating System and version

Windows 10

[ashishdhingra]

@rcdailey Thanks for reporting the issue. The issue related to aws configure should be opened in https://github.com/aws/aws-cli repository.

[tim-finnigan]

Hi @rcdailey thanks for reaching out. In the documentation that you linked to, it does mention how Windows uses %USERPROFILE%. And in the .NET developer guide it describes how the SDK looks for your credentials there: https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/creds-assign.html

So this is the expected behavior. Since this isn’t a bug, I’m going to convert the issue into a Discussion per our guidance process. Please let us know if you have any follow up questions.