Skip to main content

Configuring a firewall, proxy server, or data perimeter for Kiro

If your network uses a firewall, proxy server, or data perimeter, you need to allowlist specific URLs so Kiro can reach its backend services. This page lists every domain Kiro contacts, grouped by function.

Network traffic overview

Kiro makes two types of outbound connections:

  • Application traffic — Requests from the Kiro process (chat, completions, telemetry, and updates in IDE/CLI). In the IDE and CLI, this traffic respects your proxy settings. In Kiro Web, it flows through backend services.
  • Browser traffic — Sign-in opens your default browser. This traffic uses your OS network stack and bypasses any proxy settings configured in the IDE or CLI.

Your firewall must allow both at the network level.

Core URLs

The following URLs are required by all Kiro products (IDE, CLI, and Web):

URLPurpose
app.kiro.devSign-in portal
eu-central-1.app.kiro.devCloud sessions for Kiro profiles in Europe (Frankfurt)
assets.app.kiro.devApplication assets

Surface-specific URLs

Every Kiro IDE installation also needs the following URLs. These cover chat and code assistance, telemetry, and auto-updates.

URLPurpose
prod.us-east-1.auth.desktop.kiro.devToken exchange, refresh, and logout
prod.us-east-1.telemetry.desktop.kiro.devTelemetry (US East), Kiro 1.4.61 and earlier only
prod.eu-central-1.telemetry.desktop.kiro.devTelemetry (Europe), Kiro 1.4.61 and earlier only
prod.download.desktop.kiro.devAuto-updates, Powers registry, and icons
q.us-east-1.amazonaws.comKiro service (US East)
q.eu-central-1.amazonaws.comKiro service (Europe)
runtime.us-east-1.kiro.devKiro service (US East)
runtime.eu-central-1.kiro.devKiro service (Europe)
management.us-east-1.kiro.devConfiguration, access management (US East)
management.eu-central-1.kiro.devConfiguration, access management (Europe)
telemetry.us-east-1.kiro.devTelemetry (US East)
telemetry.eu-central-1.kiro.devTelemetry (Europe)

If your network policy allows wildcard rules, you can allowlist *.kiro.dev and *.app.kiro.dev instead of the individual kiro.dev domains above. Note that some firewalls only match a single subdomain level, so *.kiro.dev would cover app.kiro.dev but not assets.app.kiro.dev. If your firewall behaves this way, also add *.app.kiro.dev or list multi-level subdomains explicitly. See Wildcard rules for a complete summary.

Social sign-in

If you sign in with Google or GitHub, allowlist the Cognito endpoint below. GitHub sign-in also loads an AWS WAF CAPTCHA from *.awswaf.com. If your firewall or proxy blocks this domain, GitHub sign-in fails.

URLPurpose
cognito-identity.us-east-1.amazonaws.comFederated identity for social sign-in
*.awswaf.comCAPTCHA for GitHub sign-in

Some firewalls and proxies match a wildcard at only one subdomain level. If yours does, also allowlist *.captcha.awswaf.com and *.token.awswaf.com.

IAM Identity Center

If your organization uses AWS IAM Identity Center for authentication, allowlist these additional endpoints.

Replace idc-directory-id-or-alias with your IAM Identity Center instance's directory ID or alias, and sso-region with the AWS Region where your instance is enabled. For more information, see What is IAM Identity Center? in the IAM Identity Center User Guide.

URLPurpose
<region>.signin.awsAWS sign-in
<sso-region>.signin.aws.amazon.comAWS sign-in (alternate)
<idc-directory-id-or-alias>.awsapps.comIAM Identity Center portal
portal.sso.<sso-region>.amazonaws.comSSO portal
assets.sso-portal.<sso-region>.amazonaws.comSSO portal assets
oidc.<sso-region>.amazonaws.comOIDC token exchange

External identity providers

If your organization uses an external identity provider (IdP) with IAM Identity Center, the sign-in flow redirects through your IdP's domain. You need to allowlist that domain too.

Identity providerDomain to allowlist
Microsoft Entra IDlogin.microsoftonline.com
Okta<your-org>.okta.com

Check with your identity team for the exact domain if you are unsure which IdP is configured.

AWS GovCloud (US)

If you use Kiro in AWS GovCloud (US), allowlist these endpoints for each Region your organization uses:

URLPurpose
runtime.us-gov-east-1.kiro.devKiro service, AWS GovCloud (US-East)
runtime.us-gov-west-1.kiro.devKiro service, AWS GovCloud (US-West)
management.us-gov-east-1.kiro.devConfiguration and access management, AWS GovCloud (US-East)
management.us-gov-west-1.kiro.devConfiguration and access management, AWS GovCloud (US-West)
telemetry.us-gov-east-1.kiro.devTelemetry, AWS GovCloud (US-East)
telemetry.us-gov-west-1.kiro.devTelemetry, AWS GovCloud (US-West)

Subscription management

If you sign in with Google, GitHub, or AWS Builder ID, Kiro uses Stripe for subscription billing. Allowlist these domains to access the billing portal and upgrade plans.

URLPurpose
billing.stripe.comBilling portal for paid plans
checkout.stripe.comCheckout for plan upgrades

Enterprise customers using IAM Identity Center don't need these domains.

Optional URLs

You only need these if you use the corresponding Kiro feature. Skip any that don't apply to your environment.

URLFeaturePurpose
open-vsx.orgExtensionsSearch and metadata
openvsx.eclipsecontent.orgExtensionsIcons and VSIX downloads
github.comPowers / MCPRepository cloning
raw.githubusercontent.comPowers / MCPConfig files and readme images

Proxy configuration

Kiro respects standard proxy environment variables for all IDE traffic:

  • HTTP_PROXY
  • HTTPS_PROXY
  • NO_PROXY

You can also configure proxy settings in Settings > Proxy inside Kiro.

Troubleshooting connection issues

If some users can connect to Kiro but others cannot, see Network connectivity issues in the troubleshooting guide.

If your network performs TLS inspection and Kiro IDE requests fail with read ECONNRESET, see TLS inspection compatibility.

Data perimeters

If you use data perimeters on AWS to restrict access to trusted identities and resources, make sure your policies allow Kiro's service principals to reach the endpoints listed on this page. For VPC-level controls, see VPC endpoints (AWS PrivateLink).

Wildcard rules

If your network policy allows wildcard rules, you can simplify the allowlist:

WildcardCovers
*.kiro.devAll single-level Kiro subdomains
*.app.kiro.devApplication and CDN assets
*.kiro.aws.devTelemetry endpoints
*.amazonaws.comAll AWS service endpoints (Kiro service, RUM, OIDC, SSO, Cognito)
*.awswaf.comAWS WAF CAPTCHA for GitHub sign-in
*.captcha.awswaf.comNested CAPTCHA hosts for GitHub sign-in; add if your firewall matches only one wildcard level
*.token.awswaf.comNested CAPTCHA hosts for GitHub sign-in; add if your firewall matches only one wildcard level
*.shortbread.aws.devCookie consent
*.signin.awsIAM Identity Center sign-in
Page updated: November 18, 2026