fix: add missing Kiro network domains and SECRET_ auth key fallbacks - #50573
Merged
Merged
Conversation
…keys Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
fix: add missing Kiro network domains and SECRET_ fallbacks for auth keys
fix: add missing Kiro network domains and SECRET_ auth key fallbacks
Aug 5, 2026
Copilot created this pull request from a session on behalf of
pelikhan
August 5, 2026 14:21
View session
pelikhan
marked this pull request as ready for review
August 5, 2026 14:38
Contributor
There was a problem hiding this comment.
Pull request overview
Adds reliable authentication and network access for Kiro and Cursor workflow engines.
Changes:
- Allows required Kiro AWS API and telemetry domains.
- Restores API keys from AWF’s
SECRET_-prefixed variables. - Regenerates affected smoke-test workflow lock files.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/shared/kiro.md |
Adds domains and Kiro key fallback. |
.github/workflows/shared/cursor.md |
Adds Cursor key fallback. |
.github/workflows/smoke-kiro.lock.yml |
Regenerates the Kiro workflow. |
.github/workflows/smoke-cursor.lock.yml |
Regenerates the Cursor workflow. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 4/4 changed files
- Comments generated: 0
- Review effort level: Balanced
Contributor
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Kiro CLI auth fails intermittently because two AWS domains are missing from the firewall allow-list, and neither Kiro nor Cursor harness scripts handle the
SECRET_-prefixed env var rename that the AWF entrypoint applies to sensitive tokens.Network allow-list (
shared/kiro.md)q.us-east-1.amazonaws.comandclient-telemetry.us-east-1.amazonaws.com— audit-diff showed 42+ blocked calls per run to these domainsAuth key fallback (
shared/kiro.md,shared/cursor.md)The AWF entrypoint renames
KIRO_API_KEY→SECRET_KIRO_API_KEY(same for Cursor) before the harness runs. Added fallback at harness startup:Without this, when the network deny causes the primary auth path to fail, kiro-cli falls back to interactive device-flow login and errors with
Failed to open URL; cursor-agent errors withAuthentication required.