Troubleshooting the Category SDK

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

fatal: unable to access 'https://git-codecommit.us-west-2.amazonaws.com/v1/repos/...': The requested URL returned error: 403

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.

    aws sts get-caller-identity --profile alexa-ai-user
   

   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

    aws sts get-caller-identity --profile alexa-ai
   

   If this fails → check that your IAM user has the sts:AssumeRole policy attached.

3. Clear cached credentials

   macOS:

    git credential-osxkeychain erase
    host=git-codecommit.us-west-2.amazonaws.com
    protocol=https
   

   Press Enter twice after the protocol line.

   Ubuntu/Linux (libsecret):

    printf "protocol=https\nhost=git-codecommit.us-west-2.amazonaws.com\n" | git-credential-libsecret erase
   

   Ubuntu/Linux (store — plaintext file):

    sed -i '/git-codecommit.us-west-2.amazonaws.com/d' ~/.git-credentials
   

   Ubuntu/Linux (cache — in-memory):

    git credential-cache exit
   

4. Verify git credential helper is configured.

    git config --global --get "credential.https://git-codecommit---us-west-2.amazonaws.com.rproxy.govskope.ca.helper"
   

   Expected: !aws codecommit credential-helper --profile alexa-ai $@

5. Test git access manually.

    git ls-remote https://git-codecommit.us-west-2.amazonaws.com/v1/repos/category-restaurant-reservation-template-typescript
   

Once the above succeeds, retry the alexa-ai new or alexa-ai test command.

npm install fails with 401 Unauthorized

Symptom:

npm error 401 Unauthorized - GET https://alexa-ai-372468808636.d.codeartifact.us-west-2.amazonaws.com/...

Steps:

1. Re-authenticate (CodeArtifact token expires every 12 hours):

    aws codeartifact login \
      --tool npm \
      --domain alexa-ai \
      --repository npm-packages \
      --domain-owner 372468808636 \
      --region us-west-2 \
      --namespace @alexa-ai \
      --profile alexa-ai
   

2. If the issue persists, delete the @alexa-ai entries from ~/.npmrc:

   macOS:

    sed -i '' '/@alexa-ai/d' ~/.npmrc
   

   Ubuntu/Linux:

    sed -i '/@alexa-ai/d' ~/.npmrc
   

3. Re-run the login command from step 1 to regenerate fresh entries.

4. Verify the registry is configured correctly:

    npm config get @alexa-ai:registry
   

   Expected: https://alexa-ai-372468808636.d.codeartifact.us-west-2.amazonaws.com/npm/npm-packages/

CDK deploy fails with credential errors

Symptom:

Unable to resolve AWS account to use

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 updated: Jul 10, 2026