Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Category SDK
MCP toolkit
Certify
Resources
Skip to main content
The commands shown in this guide use alexa-ai and alexa-ai-user as AWS profile names. These refer to the profiles you configured during the onboarding steps:
  • alexa-ai-user is the base credential profile (IAM User keys)
  • alexa-ai is 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

If alexa-ai new or alexa-ai test commands fail with a Git clone error, follow these steps:
  1. 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.
  2. Verify role assumption works
    If this fails → check that your IAM user has the sts:AssumeRole policy attached.
  3. Clear cached credentials macOS:
    Press Enter twice after the protocol line. Ubuntu/Linux (libsecret):
    Ubuntu/Linux (store — plaintext file):
    Ubuntu/Linux (cache — in-memory):
  4. Verify git credential helper is configured.
    Expected: !aws codecommit credential-helper --profile alexa-ai $@
  5. Test git access manually.
Once the above succeeds, retry the alexa-ai new or alexa-ai test command.

npm install fails with 401 Unauthorized

Symptom:
Steps:
  1. Re-authenticate (CodeArtifact token expires every 12 hours):
  2. If the issue persists, delete the @alexa-ai entries from ~/.npmrc: macOS:
    Ubuntu/Linux:
  3. Re-run the login command from step 1 to regenerate fresh entries.
  4. 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:
Fix: Verify default profile credentials:
If this fails, re-run 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 set ALEXA_ADDON_UNDER_TEST in the CDK stack. This enables basic auth where Alexa sent requests are signed using Private Key.
Last modified on July 10, 2026