Skip to content

Conversation

@samsolaimani
Copy link

Summary

Fixes three path resolution errors that prevented the metadata server from starting properly.

Changes

  1. Metadata server path: Changed from '../lib/metadata-server.js' to '../metadata-server.js'
  2. Forever daemon root: Fixed from '../' to '../../../../' to properly resolve to project root
  3. Service files path: Updated from '../service' to '../../../../service'

These paths must resolve correctly from the dist/src/lib/handlers/ directory context after TypeScript compilation.

Testing Instructions

  1. Build the project: npm run build
  2. Start the metadata server: node dist/src/bin/alks.js server start
  3. Verify server is running: curl http://169.254.169.254/latest/meta-data/iam/security-credentials/
    • Should return: alks
  4. Test full credentials endpoint: curl http://169.254.169.254/latest/meta-data/iam/security-credentials/alks
    • Should return JSON with AWS credentials

Note: Testing must use 169.254.169.254 (not 127.0.0.1:45000) as the pf rules redirect traffic.

Related

Fixes three path resolution errors that prevented the metadata server from starting:
1. Corrected metadata-server.js path from '../lib/metadata-server.js' to '../metadata-server.js'
2. Fixed forever daemon root from '../' to '../../../../' to properly resolve to project root
3. Updated service file path from '../service' to '../../../../service'

These changes ensure paths correctly resolve from the dist/src/lib/handlers/ directory context after TypeScript compilation.

Resolves DE565327

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@samsolaimani samsolaimani self-assigned this Jan 26, 2026
@samsolaimani samsolaimani added bug release/patch Indicates an update without breaking changes or new features labels Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug release/patch Indicates an update without breaking changes or new features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants