This release shows which VPC connection a cloud session uses when your organization connects cloud sessions to its Amazon VPC, and adds organization sign-in for MCP servers in V3 sessions and a configurable portal for kiro-cli login. One sign-in through your organization's identity provider now covers every server set to use it, and you or your administrator choose where browser sign-in starts.
Your organization can connect Kiro cloud sessions to private resources in its Amazon VPC. Administrators create the connection in the Kiro console and set it as the profile default in Controls. VPC connections are in preview on Enterprise plans for IAM Identity Center profiles in US East (N. Virginia) (us-east-1). In Kiro CLI 3.5.0, a cloud session connected to a VPC names the connection, VPC ID, and Region on the row under the input and in /session-id. --no-interactive --cloud runs print a [cloud] vpc <name> · <vpc-id> · <region> line on stderr, and --output-format stream-json runs emit a cloudSession record with vpcConnection. Learn more ->
In a V3 session, every MCP server you set to organization sign-in shares one sign-in through your organization's identity provider instead of a separate browser flow per server. Run kiro-cli mcp idp setup with your provider's issuer and client ID, then open /mcp and press Enter to sign in once; those servers stay disconnected until you do. For an HTTP server whose owner issued Kiro a client ID, use the --oauth-client-id <client-id> flag on kiro-cli mcp add, except when your organization's registry manages that server's OAuth. Learn more ->
Set auth.portalUrl and kiro-cli login opens that portal in your browser instead of the default one. Administrators can set the portal for their users through the AuthPortalUrl policy or auth_portal_url in managed-settings.json. If Kiro cannot use that value, it falls back to the default portal. Learn more ->