alexa-ai and alexa-ai-user as AWS profile names. These refer to the profiles you configured during the onboarding steps:
alexa-ai-useris the base credential profile (IAM User keys)alexa-aiis the role assumption profile (AddOn3PDeveloperToolsRead). If you used different profile names during setup, replace accordingly.
alexa-ai new or alexa-ai test Fails with git clone error
Symptom
alexa-ai new or alexa-ai test commands fail with a Git clone error, follow these steps:
-
Verify your IAM user credentials are valid.
If this fails → your Access Key ID or Secret Access Key is invalid or rotated. Generate new keys in your AWS IAM console.
-
Verify role assumption works
If this fails → check that your IAM user has the
sts:AssumeRolepolicy attached. -
Clear cached credentials
macOS:
Press Enter twice after the
protocolline. Ubuntu/Linux (libsecret):Ubuntu/Linux (store — plaintext file):Ubuntu/Linux (cache — in-memory): -
Verify git credential helper is configured.
Expected:
!aws codecommit credential-helper --profile alexa-ai $@ -
Test git access manually.
alexa-ai new or alexa-ai test command.
npm install fails with 401 Unauthorized
Symptom:-
Re-authenticate (CodeArtifact token expires every 12 hours):
-
If the issue persists, delete the
@alexa-aientries from~/.npmrc: macOS:Ubuntu/Linux: - Re-run the login command from step 1 to regenerate fresh entries.
-
Verify the registry is configured correctly:
Expected:
https://alexa-ai-372468808636.d.codeartifact.us-west-2.amazonaws.com/npm/npm-packages/
CDK deploy fails with credential errors
Symptom:aws configure with your Access Key ID and Secret Access Key (see onboarding Step 5).
4xx error thrown by API Gateway
Symptom When testing, you get a 4xx error from API Gateway. Fix: Ensure you haven’t setALEXA_ADDON_UNDER_TEST in the CDK stack. This enables basic auth where Alexa sent requests are signed using Private Key.
