Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENOENT: no such file or directory, open 'Z:\.aws\config' #13268

Closed
2 tasks done
KingUgochukwu opened this issue Sep 26, 2023 · 3 comments
Closed
2 tasks done

ENOENT: no such file or directory, open 'Z:\.aws\config' #13268

KingUgochukwu opened this issue Sep 26, 2023 · 3 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-init Issues related to initializing a new Amplify project

Comments

@KingUgochukwu
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v14.17.3

Amplify CLI Version

12.4.0

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

amplify init returns the following error

C:\Users\v.anyanwu\Bridger\Developer\DNRC\dnrc_helper> amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project dnrchelper
The following configuration will be applied:

Project information
| Name: dnrchelper
| Environment: dev
| Default editor: Visual Studio Code
| App type: flutter
| Configuration file location: ./lib/
? Initialize the project with the above configuration? Yes
? Select the authentication method you want to use: AWS profile
For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default
🛑 ENOENT: no such file or directory, open 'Z:.aws\config'

Expected behavior

amplify should be initialized in directory

Reproduction steps

  1. Run amplify init

Project Identifier

Learn more at https://docs.amplify.aws/cli/reference/diagnose/

  • Creating Zip
    No Amplify backend project files detected within this folder.
    × Creating Zip

Session Identifier: 8652a3ab-924b-405f-9335-8dec24dad3ce

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@KingUgochukwu KingUgochukwu added the pending-triage Issue is pending triage label Sep 26, 2023
@ykethan ykethan added the platform-init Issues related to initializing a new Amplify project label Sep 26, 2023
@ykethan
Copy link
Member

ykethan commented Sep 26, 2023

Hey @KingUgochukwu, thank you for reaching out. Could you check if the config file is present inside .aws folder? We use the folder to fetch credentials for amplify IAM user to initialize amplify project.
the .aws folder on windows should be located on C:\Users\<userid>\. aws\.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Sep 26, 2023
@ykethan
Copy link
Member

ykethan commented Dec 13, 2023

closing the issue due to inactivity. please feel free in reaching out to us, we would be happy in diving deeper.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2023
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-init Issues related to initializing a new Amplify project
Projects
None yet
Development

No branches or pull requests

2 participants