-
Notifications
You must be signed in to change notification settings - Fork 26
Open
Description
npm start fails unless there is a smallwins profile in .aws/config with some value:
This works, literally, with placeholder keys.
[smallwins]
aws_access_key_id = YOUR_AWS_ACCESS_KEY_ID
aws_secret_access_key = YOUR_AWS_SECRET_ACCESS_KEY
I have tried it with both globally installed Architect@latest and leaving it with the local Architect@5.9.37 after removing it globally. It always requires an aws config profile to be present. Taking the @aws profile out of the .arc file, will bypass this issue as well.
If I have Architect@latest installed globally and remove @architect/architect from the devDependencies in package.json, npm start will error with cannot find module 'aws-sdk', even if aws-sdk is installed globally.
Metadata
Metadata
Assignees
Labels
No labels