[GH-ISSUE #58] Wrong URL for eu-central-1 Developer Q API #38

Closed
opened 2026-02-27 07:17:37 +03:00 by kerem · 1 comment
Owner

Originally created by @saaj on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/jwadow/kiro-gateway/issues/58

I was trying the gateway (with Developer Q) and to make it work in eu-central-1 I needed to patch kiro/config.py, to make KIRO_API_HOST_TEMPLATE = "https://q.{region}.amazonaws.com" (i.e. to make it the same as KIRO_Q_HOST_TEMPLATE), because there's no such host:

$ host codewhisperer.eu-central-1.amazonaws.com
Host codewhisperer.eu-central-1.amazonaws.com not found: 3(NXDOMAIN)

Also with all debugging turned on, the hostname is not logged, so I had to patch the logging to output what's actually not resolving. This AWS firewall whitelist page may be relevant.

Originally created by @saaj on GitHub (Jan 27, 2026). Original GitHub issue: https://github.com/jwadow/kiro-gateway/issues/58 I was trying the gateway (with Developer Q) and to make it work in `eu-central-1` I needed to patch `kiro/config.py`, to make `KIRO_API_HOST_TEMPLATE = "https://q.{region}.amazonaws.com"` (i.e. to make it the same as `KIRO_Q_HOST_TEMPLATE`), because there's no such host: ``` $ host codewhisperer.eu-central-1.amazonaws.com Host codewhisperer.eu-central-1.amazonaws.com not found: 3(NXDOMAIN) ``` Also with all debugging turned on, the hostname is not logged, so I had to patch the logging to output what's actually not resolving. This [AWS firewall whitelist page][1] may be relevant. [1]: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/firewall.html
kerem 2026-02-27 07:17:37 +03:00
  • closed this issue
  • added the
    bug
    fixed
    labels
Author
Owner

@jwadow commented on GitHub (Jan 30, 2026):

Hey, thanks for the detailed report and the fix!

The issue was that codewhisperer.{region}.amazonaws.com only exists for us-east-1. According to AWS docs, the correct endpoint for all regions (including us-east-1) is q.{region}.amazonaws.com.

Fixed by:

  • Changed KIRO_API_HOST_TEMPLATE to use q.{region}.amazonaws.com
  • Added logging for API hosts and URLs to help diagnose similar DNS issues in the future

The gateway now works in all AWS regions (us-east-1, eu-central-1, etc)

Also added you to CONTRIBUTORS.md for finding and fixing this critical issue. Thanks for making the gateway better!

<!-- gh-comment-id:3821604690 --> @jwadow commented on GitHub (Jan 30, 2026): Hey, thanks for the detailed report and the fix! The issue was that `codewhisperer.{region}.amazonaws.com` only exists for us-east-1. According to AWS docs, the correct endpoint for all regions (including us-east-1) is `q.{region}.amazonaws.com`. Fixed by: - Changed `KIRO_API_HOST_TEMPLATE` to use `q.{region}.amazonaws.com` - Added logging for API hosts and URLs to help diagnose similar DNS issues in the future The gateway now works in all AWS regions (us-east-1, eu-central-1, etc) Also added you to CONTRIBUTORS.md for finding and fixing this critical issue. Thanks for making the gateway better!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/kiro-gateway-jwadow#38
No description provided.